Skip to content

Transfers outside Quebec

Last updated October 27, 2026

When a Quebec business uses BrightDoor, personal information is kept outside Quebec, in the United States. Quebec's private-sector privacy law (s. 17) asks for an assessment before that happens. This is BrightDoor AI LLC's assessment of what we hold. Use it for your own.

What leaves Quebec, and why

  • Messages, requests, and leads people send through a business's site: name, email, phone, the message, and form answers. Why: To bring them to the business and let it answer. How sensitive: Usually low. Forms ask people not to share health, legal, or financial details; law offices' requests lose their details after a set time.
  • The business's clients and contacts, with their consent records. Why: So the business can keep in touch only with people who agreed. How sensitive: Low to moderate: contact details and how someone agreed.
  • The owner's own account: names, emails, licence numbers, billing and tax numbers. Why: To run the account, show the required licence lines, and bill. How sensitive: Low to moderate. Card numbers stay with Stripe; BrightDoor never sees them.
  • Visit counts: pages, referring sites, and kinds of device, by day. Why: To show the owner simple reports. How sensitive: Very low. No cookies, no profile, and no IP address is stored.

Where it goes

Each provider may use the information only to do its job for us.

  • Neon (on Amazon Web Services) (United States, Ohio (aws-us-east-2)). BrightDoor's database and file storage. Information: Everything below: accounts, leads and messages, files, settings, and the audit log. Bound by: Neon Data Processing Addendum.
  • Vercel (United States). Hosts BrightDoor and every site, and routes drafting requests to model providers (AI Gateway). Information: What a page shows or a form sends, while it passes through. Bound by: Vercel Data Processing Addendum.
  • Cloudflare (R2) (United States). Stores Estimation files and map tiles. Information: Plan sets and price lists an owner uploads. No visitor messages. Bound by: Cloudflare Data Processing Addendum.
  • Inngest (United States). Runs background jobs. Information: Job instructions, which can name a record by its id. Bound by: Inngest Data Processing Agreement.
  • Clerk (United States). Sign-in. Information: The owner's team: names, emails, and sign-in details. Bound by: Clerk Data Processing Addendum.
  • Stripe (United States). Billing and partner payouts. Information: The owner's billing details and tax numbers. Never visitor messages. Bound by: Stripe Data Processing Agreement.
  • Resend (United States). Sends email. Information: The email address and the message being sent. Bound by: Resend Data Processing Addendum.
  • Twilio (United States). Texts and calls, when the business uses them. Information: Phone numbers and the text of messages. Bound by: Twilio Data Protection Addendum.
  • OpenAI and Anthropic (through Vercel's AI Gateway) (United States). Draft text the owner approves, and read plan sets. Information: Only the text a draft needs: for a reply, a first name and the short note someone wrote. Never contact details. Bound by: Each provider's API data processing terms, which limit use to doing the work.
  • Google (United States). Only if the owner connects a Google account or Business Profile. Information: Reviews, profile numbers, and the replies and posts the owner approves. Bound by: Google API Services User Data Policy.

How it is protected

  • Contract: BrightDoor's Terms and data processing agreement bind BrightDoor to use the information only to run the service. Each provider is bound by its own data processing terms (listed above) to the same.
  • Encryption: every connection is encrypted, and the database and file storage encrypt what they keep.
  • Separation: each business's information is kept apart from every other account's.
  • Access: only a few people at BrightDoor can open an account, only to help when asked, and each time is written to the audit log.
  • Less data: forms ask only for what a reply needs, and tracking tools stay off until a visitor says yes.
  • Deletion: the business can delete any record at once; a closed account is deleted after 30 days, and backups roll off within 30 days after that.
  • Incidents: BrightDoor keeps a register of confidentiality incidents and tells the business without delay, so it can tell the Commission d'accès à l'information and the people concerned.

The law in the United States

  • The United States has no single federal privacy law like Quebec's. Privacy is covered by sector laws and by state laws, such as California's.
  • The US Federal Trade Commission can act against a company that breaks its own privacy promises.
  • US courts, police, and national security agencies can ask for information held there, under US law (for example, a warrant, or the Foreign Intelligence Surveillance Act). BrightDoor would ask for a proper legal order, give only what it requires, and tell the business unless the law forbids it.

Conclusion

Given how little sensitive information the sites collect, what it is used for, and the protections above, BrightDoor's assessment is that the information is adequately protected in the United States. A business that collects more sensitive information than this (health details, ID numbers, finances) should not do it through its site, and should redo this assessment for that information.

The written agreement the law asks for is our data processing agreement, which is part of our Terms.

How to use it

  • Read it, and change anything that's different for your business (for example, if you connect Google or text your clients).
  • Print it or save it as a PDF, sign and date it, and keep it with your privacy records.
  • Look at it again once a year, or when BrightDoor emails you about a new provider.

Privacy officer: [name], privacy@brightdoor.ai.