Privacy policy
Last updated: 2 November 2026
<br/> is in private beta: this text will be completed before the service opens commercially.
This page explains what data <br/> collects, what it is used for, where it is processed and how to exercise your rights. It applies to the br.garah.me website, the server and the Visual Studio Code extension.
Data controller
The data controller is Dominique Bria, publisher of <br/>.
During the beta, contact us with the “Send feedback” command in the extension.
The data we process
- Your account: email address, display name, language, creation date.
- Your teams and projects: name, members, roles (team lead or collaborator), invitations.
- Your project content: chat messages, attachments, project memory (decisions, tasks, notes), orders given to the cook, their steps, their summary and the names of the files changed.
- Your working preferences: the backup copy of your local memory (the ~/.bria/memoire.md file), kept on the server only to restore it on a new machine.
- Project vault secrets: encrypted on the server (AES-256-GCM). Their values are never sent to the AI.
- Your machines: a machine identifier, the operating system and editor used, and sign-in sessions, of which only a fingerprint is kept.
- AI usage: for each call, the provider, the model, the number of tokens processed, the duration and the credits used. The content of the exchanges is not copied into this log.
- The feedback you send from the extension, and your email address if you request a beta invitation.
The website uses no advertising, no audience measurement tool and no tracking cookie.
What this data is used for
- Running the service: accounts, team chat, project memory, the work of the server and the cook (basis: performing the service you use).
- Signing you in with a code sent by email, and writing to you about your account or the beta.
- Measuring credit usage, applying plan quotas and preventing abuse (basis: our legitimate interest in keeping the service safe and sustainable).
- Improving <br/> based on the feedback you send us.
Artificial intelligence
To answer and carry out orders, the project's messages, its memory and, for the cook, the content of the files it reads are sent to AI providers: Google (Gemini), Mistral AI, Groq and Z.ai. Vault secrets are excluded: the AI only sees their names.
During the beta, <br/> uses these providers' free tiers. On these tiers, some of them may keep and use the content sent to improve their services; this is notably the case for Google's free Gemini API. So please do not share sensitive information in the chat during the beta.
What happens on your machine
The cook works on the machine of the member who agrees to lend it, inside the project folder, according to the chosen permission mode. Files stay on that machine; only the excerpts needed for the order are sent to the AI, as described above.
The website only stores, in your browser, your choice of light or dark mode.
Where your data is processed
- Server and database: in Europe (Microsoft Azure and Neon, Frankfurt).
- Attachments: Backblaze, in the United States.
- Website: Vercel, global network.
- Emails: Resend, sent from Ireland.
- AI: Google and Groq (United States), Mistral AI (France), Z.ai (outside the European Union).
Some of these providers are located outside the European Union. We choose providers that contractually commit to protecting the data they process on our behalf.
Retention
- Sign-in codes: 10 minutes.
- Your account and project content: as long as the account exists. A project's messages remain visible to its team after a member leaves.
- Machine sessions: until sign-out or until the machine is revoked.
- Beta invitation requests: until the end of the beta.
- The AI usage log: as long as needed to track costs and billing.
Your rights
You can access your data, have it corrected, request a copy, object to processing or ask for its deletion.
You can delete your account yourself from the extension (Settings, “Delete my account”).
For any other request, use the “Send feedback” command in the extension. We reply within one month.
You may also lodge a complaint with the data protection authority of your country.
Security
Exchanges are encrypted (HTTPS), vault secrets are encrypted at rest, sign-in tokens are only kept as fingerprints, and access to the internal dashboard is restricted by account and by section.
Changes
This policy may change, in particular when the service opens commercially. The update date appears at the top of the page; in the event of a significant change, we will let you know in the extension or by email.