Privacy policy

1. Who the controller is

Bridges Agents, CNPJ (Brazilian company registration number) 60.453.617/0001-94, is the controller of the personal data processed on BridgesAgents, under the Brazilian General Data Protection Law (Law 13,709/2018, “LGPD”). Data protection officer (DPO): [DPO name, to be completed], [DPO email, to be completed].

When we serve people in the European Economic Area or the United Kingdom, we also apply the General Data Protection Regulation (GDPR/UK GDPR); EU representative: [EU representative, if applicable]. For California residents, we follow the CCPA/CPRA. For orders, the store is an independent controller of the consumer data it receives to fulfill the order.

2. Data we process

• People who use the dashboard (merchants and their team): name, email, password (stored only as a hash, never in plain text), role and stores accessed, date these documents were accepted.
• Company and stores: legal name, CNPJ, addresses, location, opening hours and delivery areas. This is company data; it may include personal data when the merchant is a sole proprietor.
• Location sent by agents: when an agent queries offers, it may send the consumer's CEP (Brazilian ZIP code) or coordinates. We use this only to work out which stores serve that area and how far they are; we do not identify the consumer.
• Access logs: IP address, date and time of access and of API usage, used for security and usage limits.
• Consumers who confirm orders: name, mobile number, email (optional; required for digital products), address (for delivery and at-home services) and the requested date (services and bookings). They go to the order's store, which needs them to fulfill it.
• Consent to share: the AI assistant you use (its operator) collects your consent for the order data to come to BridgesAgents and be shared with partners, under its contract with BridgesAgents. We record which assistant the order came from and, if you stop sharing, the date.
• Support tickets: name, email and what you write in the conversation with the team.
• Fraud prevention signals: what happens to each order (placed, cancelled, paid, refused, refunded), the amount, the payment method and the area (start of the postal code). The buyer's email, name, phone, document and address are stored only as a code (keyed hash), never the data itself.
• Notices from the store's checkout: when the store uses an external checkout (such as AppMax or Mercado Pago), it tells us the order's payment status and, if it sends them, the buyer's email, name, document and phone, used only for the signals above.

3. What we use it for and on what legal basis

• Creating and maintaining the account, authenticating and providing the service: performance of a contract (art. 7, V).
• Sending invitation, email confirmation, password reset and operational notice emails: performance of a contract.
• Preventing fraud and abuse, enforcing usage limits and protecting the platform: legitimate interest (art. 7, IX).
• Calculating each order's risk level for the store (signals from the store itself and, if it takes part in the network, from other network stores) and showing aggregated numbers by area: fraud prevention and credit protection, under legitimate interest (art. 7, IX and X). The store sees only the level and the reasons, never data given at another store; the area never decides on its own. You may ask for this assessment to be reviewed (art. 20).
• Sharing your name, email and phone with BridgesAgents partners, for offers and fraud prevention: based on the consent (art. 7, I) collected by the operator of the AI assistant you used, who is responsible for it under its contract with BridgesAgents. You can stop at any time at My data.
• Showing contracted partners the orders by area (products, amounts, payment, refusals and reasons), without the buyer's name or contact: legitimate interest (art. 7, IX), for market research, offers and fraud prevention.
• Keeping access logs for the legally required period: compliance with a legal obligation (Brazilian Internet Civil Framework, Marco Civil da Internet, art. 15).

4. Who we share it with

• Microsoft Azure: hosting of the application and database, in the Canada Central region (international transfer, under Microsoft's contractual safeguards).
• Resend: sending transactional emails (receives the recipient's name and email). International transfers may occur, with the safeguards provided for in the LGPD.
• BrasilAPI: CEP lookup to obtain the city and approximate coordinates (receives only the CEP).
• OpenStreetMap (Nominatim): postal code lookup for other countries to obtain approximate coordinates (receives only the postal code and country).
• Woovi: invoice collection via Pix (receives the billed company's data).
• Bling and Nuvemshop: only when the merchant connects their account, to import the catalog.
• Stores: receive the consumer data of each order confirmed with them.
• Other stores in the signal network: receive only the risk level and reasons (e.g. "chargeback at another store"), without name, contact, address or the originating store, and totals for areas with minimum volume and at least 3 companies.
• Contracted partners (agent developers, advertising and fraud prevention companies and other stores): see the network stores' orders by area, with the fields their contract allows. Name, email and phone only from orders with the buyer's consent. Every query is logged, and the partner is responsible for how it uses the data, under the contract and the LGPD.
• The store's checkout: the order link takes you to the checkout chosen by the store; payment is made directly with the store and that checkout, which has its own policy. BridgesAgents never receives or passes on the order's money.
• The public, agents and integrations: receive the catalog and store data (not the data of the people who use the dashboard).
• Authorities, when there is a legal obligation or a court order.

We only share your contact based on the consent collected by the assistant you used, and you can stop at My data.

5. How long we keep it

• Account data: while the account exists and, afterwards, for the period needed to meet legal obligations.
• Access logs: 6 months, as required by the Marco Civil da Internet.
• Invitation, confirmation and password reset links: expire within 7 days and can be used only once.
• CEP and postal code lookup cache: up to 90 days.
• Orders and support tickets: while needed to serve you and for the legal periods (tax and consumer protection).
• Fraud prevention signals: 12 months, then deleted automatically.

6. Your rights

You may request confirmation of processing, access, correction, anonymization, portability, deletion, information about sharing and review of automated decisions (LGPD, art. 18), by emailing [DPO email, to be completed]. We respond within the legal deadline. You may also file a complaint with the ANPD (Brazilian Data Protection Authority).

If you bought through an AI assistant, you can request a copy or the deletion of your order data at My data, confirming through the email used on the orders.

At My data you can also stop sharing your contact with partners. It applies from then on; what a partner already received follows its contract and the LGPD, and you can ask that partner directly to delete it.

Under the GDPR, you may also request restriction of processing, object to processing based on legitimate interest, and complain to your country's data protection authority. Under the CCPA/CPRA, you may know, correct and delete your data; we do not sell or share personal data for cross-context behavioral advertising.

7. Security

Encrypted connections (HTTPS), passwords hashed with bcrypt, API keys and access links stored only as hashes, sessions that expire and can be ended, role-based access control and a limit on login attempts. No measure is infallible; in the event of a relevant incident, we will notify those affected and the ANPD as required by law.

8. Cookies

We use only strictly necessary cookies: the session cookie, to keep you signed in (not accessible to page scripts), and the language cookie. We do not use advertising or tracking cookies, so we do not ask for cookie consent.

9. Changes to this policy

We may update this policy; the version and date are shown at the top of the page, and relevant changes are announced in the dashboard or by email.