Data processing agreement
This agreement is part of the terms of service. It applies when your projects contain personal data, under Article 28 of the GDPR. Last updated [to fill: date].
1. Roles
You, the customer, are the controller of the personal data in your projects ("customer data"). [to fill: company name] ("Galerne") processes it as your processor, only on your documented instructions. Your instructions are these terms, your settings, and what you, your members and your agents do in the service.
2. What we process
- Subject matter: hosting, serving, versioning and searching the content of your projects.
- Duration: as long as you use the service, then until deletion under section 9.
- Nature: storage, backup, retrieval through the API and MCP server, delivery through the CDN, indexing for search, and deletion.
- Data subjects: people named in your content, your site visitors when they request media, and members of your projects.
- Categories of data: whatever you put in your content, such as names, photos, contact details and text; member names and emails; request logs.
Do not store special categories of data (health, beliefs, biometrics and similar) in Galerne unless you have agreed it with us in writing.
3. No training, no other use
We do not use customer data to train, fine-tune or evaluate any machine learning model, and we do not let our subprocessors do so. We do not sell customer data or use it for our own purposes.
4. Models and the agent data flow
Galerne runs no language model. The data flows when you use agents are these:
- When an agent or MCP client you connected calls a Galerne tool, Galerne returns the requested customer data to that client, under the role and rules you gave the agent. This is processing on your instruction.
- The MCP client may then send that data to a model provider (for example Anthropic, OpenAI, Mistral, or a model you run). You choose the client and the provider. That onward transfer is outside our processing: you act as controller for it, under your own agreement with the provider, and you check its location and safeguards.
- Each project lists the agents and OAuth clients with access, when they were last used, and lets you revoke them at once.
- Semantic search, on Business and above, sends published text to an embedding model run by Scaleway in Paris, which returns vectors. The vectors are stored in your project database. Scaleway is listed as a subprocessor for this.
5. Confidentiality and security
People at Galerne who can access customer data are bound by confidentiality and access it only to run, support or secure the service. Our measures include:
- One database per project, apart from other projects.
- Encryption in transit (TLS) on every public endpoint. [to fill: encryption at rest of database volumes, backups and media storage]
- Tokens stored as hashes; scoped, revocable tokens; short-lived OAuth access tokens with rotating refresh tokens.
- Role-based access per project, agent rules (branches, types, writing on main, promotion) and per-agent rate limits.
- History of every change with its author, person or agent, and an audit log on Business and above.
- Backups of every database, kept [to fill: retention], with restore tested [to fill: frequency].
6. Subprocessors
You authorise the subprocessors on the subprocessors page. We tell you at least 30 days before adding or replacing one, by email to account owners. You can object for a reasonable reason; if we cannot address it, you can end the affected plan and get a refund of prepaid fees for the remaining period. Each subprocessor is bound by data protection terms at least as protective as these.
7. Location and transfers
We store and process customer data in the European Union. We do not transfer it outside the EU. Transfers made by your agents or MCP clients are covered by section 4.
8. Assistance, breaches and audits
- We help you answer requests from data subjects. Most can be handled directly in the studio or through the API, which can read, change, export and delete any document.
- We notify you of a personal data breach affecting customer data without undue delay, and within [to fill: 48] hours of becoming aware of it, with what we know and what we are doing.
- We help with impact assessments and consultations with authorities where they concern our service.
- We make available the information needed to show compliance with this agreement, and allow audits by you or an auditor you choose, with 30 days' notice, at most once a year unless a breach or an authority requires more.
9. End of processing
You can export all customer data at any time in the documented export format. After a project is deleted or the agreement ends, we delete its customer data within [to fill: number] days, and from backups when they expire, unless the law requires us to keep it.