Working draft: some publisher details are still to be filled in and the text is pending legal review.
Privacy policy
Version of 2026-11-02
This document is BeBrief’s, a service published by Hive Horizon. If an agency invited you to BeBrief, it does not replace that agency’s own terms or privacy policy: to learn how the agency uses your data, ask the agency.
BeBrief is a service published by Hive Horizon. Creative agencies use it to collect their clients’ requests, turn them into briefs with the help of an assistant and follow production. This page explains which personal data we process, why, and how to exercise your rights.
Who is responsible for your data
For the content of a workspace (clients, projects, briefs, messages, files, designs, invited people), the agency that uses BeBrief is the controller. Hive Horizon processes it on the agency’s behalf, as a processor, under the data processing agreement. If you are an agency’s client, send your requests to that agency first.
For agency accounts (sign-up, sign-in, billing, service security), Hive Horizon is the controller.
Hive Horizon, which also runs a creative studio, never uses workspace content or the identity of agencies’ clients for its own account. Its undertakings are set out in the terms of service, under “Confidentiality and no conflict of interest”.
Contact: [privacy@votre-domaine], Hive Horizon, 61 rue de Lyon, 75012 Paris, France.
Data we process
- Identity and contact: name, email address, role in the agency.
- Project content: text and files you add, messages, briefs, designs, comments and approvals. It may contain personal data if you put some in.
- Technical data: sign-in and security logs, including IP address, date and time.
- Preferences: notification and display settings.
We use no advertising, no audience measurement and no trackers.
Purposes and legal bases
- Providing the service (accounts, workspaces, briefs, notifications): performance of the contract.
- Analysing requests with the AI assistant: performance of the contract with the agency.
- Securing the service and preventing abuse (logs, rate limits): legitimate interest.
- Keeping proof that the terms were accepted: legal obligation and legitimate interest.
AI assistant
Text, messages, file extracts and images given to the assistant are sent to OpenAI or Anthropic (Claude models) to produce the brief and replies. Text extracts, never images, are sent to TypeSafe for quick checks: a message’s language, what a request asks, whether the conversation has settled a change, whether the brief matches the files. We ask OpenAI not to store them beyond the request; OpenAI may keep them for up to 30 days to detect abuse. None of these providers trains its models on data received through its API.
The assistant suggests; a person decides. No decision with legal effect is made automatically.
Recipients and sub-processors
Your data is available to the agency’s members according to the access the agency gives them, and to our sub-processors within their role:
| Sub-processor | Role | Data | Location | Safeguards |
|---|---|---|---|---|
| Hetzner Online GmbH | Hosting of the server and database | All service data except files | Germany | Hosted in the European Union |
| [fournisseur du stockage des fichiers] | Storage of uploaded files and designs | Uploaded files, designs, logos | [data centre country, in the EU] | Hosted in the European Union |
| OpenAI, L.L.C. | Brief analysis and the assistant’s replies | Text, messages, file extracts and images sent to the assistant | United States | EU–US Data Privacy Framework and standard contractual clauses; API data not used for training |
| Anthropic, PBC | Brief analysis and the assistant’s replies when a Claude model is used | Text, messages, file extracts and images sent to the assistant | United States | [base du transfert vers Anthropic : DPF et/ou clauses contractuelles types]; API data not used for training |
| TypeSafe | Quick checks: a message’s language, what a request to the assistant asks, whether the conversation has settled a change, whether the brief matches the files | Message text, brief fields, text lines from files; never images | [pays d’hébergement de TypeSafe] | European Commission standard contractual clauses; customer data not used for training |
| [fournisseur d’envoi d’emails] | Sign-in links and notification emails | Email address, name, project title | [country] | Data processing agreement (art. 28) |
| Stripe Payments Europe, Ltd. | Payment and invoices for the agency’s subscription | Agency name, owner’s email, payment method (entered at Stripe, never with us) | Ireland (EU), with possible transfers to the United States | EU–US Data Privacy Framework and standard contractual clauses |
The transfer to OpenAI (United States) relies on the EU–US Data Privacy Framework and the European Commission’s standard contractual clauses; the transfer to Anthropic (United States) on [base du transfert vers Anthropic : DPF et/ou clauses contractuelles types]; the transfer to TypeSafe on the standard contractual clauses.
How long we keep data
| Data | Kept for |
|---|---|
| Account, briefs, messages, files and designs | As long as the agency uses the service; deleted when the workspace is closed |
| Projects in the trash | 30 days, then deleted for good |
| IP address in the security log | 6 months |
| Security and activity log | 12 months (proof that the terms were accepted and the history of support access: for the length of the contract) |
| Notifications | 90 days after being read, 12 months at most |
| Unused invitations and sign-ups | 30 days after they close |
| AI usage figures (no content) | 13 months |
| Workspace whose deletion was requested | 30 days’ grace, then deleted for good |
| Backups | Rolling 30 days |
Your rights
You have the right of access, rectification, erasure, restriction, objection and portability, and the right to give instructions about your data after your death.
- Download your data: Account → Download my data.
- Delete your account: Account → Delete my account. Your name is removed from what you wrote, which stays in the agency’s projects as “Former member” or “Former client”.
- For anything else, write to the agency concerned or to [privacy@votre-domaine]. We answer within one month.
You can lodge a complaint with your data protection authority; in France, the CNIL (www.cnil.fr).
Cookies
We set a single, strictly necessary cookie: your sign-in session (bebrief.session_token), valid for a few days at most. The browser also keeps a few display preferences (collapsed sidebar, last message read). These are exempt from consent, so no banner is shown.
Security
- Each agency is isolated in the database itself (row-level security, enforced even on the application account).
- The application account has no administrative privilege; it can neither bypass isolation nor change the schema.
- Encryption in transit (HTTPS, HSTS) and strict security headers (CSP, no framing).
- Passwordless sign-in with single-use links valid for 30 minutes; sessions can be revoked at any time.
- Figma access keys are encrypted with AES-256-GCM.
- BeBrief staff see metadata only (project counts, storage used); an agency’s clients appear only as “Client”, with no name, email or domain. Access to an agency’s content needs a time-limited permission granted by one of its owners and shown in its log.
- Audit log of sign-ins, administrative actions and support access.
- Rate limiting, read-only unprivileged containers.
- Encrypted off-server backups, with restore tests.
Changes
We tell you about any significant change by email or in the app before it applies.