Draft pending legal review · Borrador pendiente de revisión legalThis text has not been reviewed by a lawyer yet and may change. It is not legal advice. We publish it to be transparent about how neuri.bazar works; the final version will replace this one.

Privacy Notice

Last updated: October 14, 2026 · Version 0.2 (draft)

See also: Terms of Service

1. Controller and processor

This notice covers users in the United States and in Mexico. For Mexico it is issued under the Federal Law on the Protection of Personal Data Held by Private Parties (LFPDPPP), published in the Official Gazette (DOF) on March 20, 2025 and in force since March 21, 2025.

2. Data we process

WhoseWhat
Store owners and staffName, email, role, store membership, whether they signed in with Google or an email link, last sign-in, sessions (stored as hashes), manager PIN (hashed) and an audit log of the changes they make.
Store vendorsName, WhatsApp and/or email, chosen channel and messaging consent, booth, commission, rent, balance and ledger, items with photos and prices, statements, bank account for payouts (routing and account number, or CLABE), signed agreement (text, name, drawn signature, date, IP and browser at signing) and, if they save one, their card for rent (stored by Stripe; we only see the last 4 digits, plus the authorization text and date).
Store customersOnly if they provide it: name, WhatsApp or email for a receipt or layaway, and what they bought or put on layaway.
Booth applicantsName, email, WhatsApp, what they sell and the booth size they want.
Technical dataIP address for rate limiting (deleted the next day), server error log without emails or numbers (30 days) and a log of messages sent (recipient, template, status).
neuri.tech visitorsAnonymous, cookieless visits and clicks (see section 8).

Sensitive data: we do not ask for or process sensitive data (ethnic origin, health, beliefs, sexual orientation, etc.). Financial data: we do process vendors' balances, payouts, bank account and card-charge authorization; they are entered by the store or by the vendor in My Booth.

3. Why we use it

Purposes needed to provide the service

Optional purposes (you can say no)

We do not sell personal data, use it for advertising, or use it to train AI models.

5. Who we share it with (subprocessors)

We use these providers to deliver the service. They process data only for that purpose, under contract. Most are in the United States, so data from Mexico is transferred internationally to the US.

ProviderPurposeLocation
RailwayServers that run the applicationUS
NeonDatabase (Postgres)US
StripePlan billing for stores (Billing) and the store's charges to vendors in its own account (Connect); card dataUS
ResendEmail delivery (sign-in links, notices, statements)US
Meta PlatformsWhatsApp Business (consented notices) and publishing to the store's Facebook/InstagramUS
GoogleSign in with Google (name and email)US
SentryTechnical error reports, without personal dataUS
PostHogAnonymous, cookieless analytics for neuri.tech (not the app)US
Cloudflare R2 or Backblaze B2; GitHubStoring the encrypted daily backup; GitHub Actions runs the backup jobUS

If the owner connects an AI assistant (Claude, ChatGPT or another), the data that assistant reads goes to that provider at the store's choice and under its terms. Beyond this, we only disclose data when a competent authority lawfully requires it.

6. How long we keep it

7. Your rights

You can ask to access, correct or delete your data, or object to its use (the "ARCO" rights under Mexican law), and you can withdraw consent or limit use (for example, stop WhatsApp messages or marketing emails).

Mexican authority: since March 21, 2025, the former INAI's powers over personal data held by private parties belong to the Secretaría Anticorrupción y Buen Gobierno (Ministry of Anti-Corruption and Good Governance). If you believe your request was not handled properly, you may go to it.

8. Cookies and analytics

9. Security

Each store is isolated in the database (row-level security), money history cannot be edited, access is role-based, sessions can be ended instantly, connections are encrypted (HTTPS), social media tokens are stored encrypted, vendors' bank accounts are encrypted at the application level (AES-256, with a key kept outside the database) and shown masked (last 4 digits): the full number is only decrypted to build the bank payout file and when the store asks to see it to correct it, and it is not included in the data export and the daily backup is encrypted. If a breach significantly affects your rights, we will tell you without undue delay.

10. US and Arizona

11. Changes to this notice

We will post any change on this page with its date and, if it is material, email store owners. If a change requires new consent, we will ask for it.

12. References

Draft for legal review. Not legal advice.