Braise privacy policy
2026-09-01
This policy describes data processing on the Braise website (the “Site”). When available, it also describes processing in the Braise desktop application for macOS, Windows and Linux, published by THE BLUE HOUSE (SASU).
1. Data controller
- THE BLUE HOUSE (SASU) — 7, rue d’Arsonval, 75015 Paris, France
- SIREN: 947 923 637 — RCS Paris
- Contact: hello@braise.dev
- Data Protection Officer: Cyril Guilleminot
2. Data processed via the Site
- Navigation and security: minimal technical data from your browser and network (e.g. IP as logged by the host, user-agent, URL, referrer, timestamp) in hosting logs.
- Waitlist form: email, role (need compute / provide compute / both), optional hardware and runtime notes, country, free-text notes, language preference, and whether you are open to an interview.
- Contact: if you email us, we process your address and message content to reply.
We do not currently load advertising pixels or cookie-based retargeting on the Site.
3. Data processed via the future desktop application (when released)
- Community inference Off: Braise creates no community route or product telemetry. Any configured local backend is consumer-owned and outside the Braise inference service.
- Account and credits (when you opt in): email or account identifiers, credit balance metadata, purchase confirmation metadata from the payment provider, node capability advertisements, and settlement receipts (not community prompt bodies on the edge path).
- Community jobs: the selected community provider can read the prompt it executes; the control plane is designed to receive routing and settlement metadata, not community prompt bodies on the peer path.
- Payments: card and billing data are handled by Stripe (or the payment provider then in use); we do not store full card numbers on our servers.
Exact product telemetry, if any, will be optional or minimized and described before activation.
4. Purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Site security and maintenance | Legitimate interest (Art. 6-1-f GDPR) |
| Waitlist, early access, interviews | Legitimate interest / pre-contractual (Art. 6-1-f / 6-1-b) |
| Email support | Legitimate interest or pre-contractual |
| Account, credits, community matching (app) | Contract performance (Art. 6-1-b) |
| Payments and accounting | Legal obligation / contract |
5. Recipients / subprocessors
- Hosting / forms: Netlify, Inc. (United States): Site hosting and Netlify Forms for waitlist submissions.
- Payments (future paid product): Stripe, Inc. / Stripe Payments Europe, Ltd.
- Email: only if you contact us or we email waitlist members about Braise.
No sale of personal data.
6. International transfers
Netlify is a US company; technical and form data may be transferred to the United States under safeguards such as standard contractual clauses used by the provider. Stripe may involve international transfers when payments go live.
7. Retention
- Hosting logs: short period needed for security.
- Waitlist: until you ask to be removed, or until the waitlist is closed and a reasonable period for launch communications has passed.
- Emails: time to handle the request, then legal retention if required.
- Account / ledger (app): for the life of the account and legal accounting periods.
8. Your rights
You have rights of access, rectification, erasure, restriction, objection, and portability where applicable, and the right to lodge a complaint with a supervisory authority (in France: CNIL).
Contact: hello@braise.dev
9. Security
We apply reasonable technical and organizational measures (TLS, access controls, least privilege, dependency updates). No method of transmission is perfectly secure.
10. Minors
The Site is not directed at children under 15.
11. Changes
We may update this policy; the “updated” date above will change. Material changes to the product will be reflected before paid or community features go live.
12. Product privacy principles (non-contractual summary)
- When Community inference is Off, Braise sends no prompt to a community provider; any local backend is outside the Braise inference service.
- Public community providers can read jobs they execute.
- Compute Credits are the closed-beta reward instrument and are not money.