A page you can hand to your legal team. It says what we do, not what we intend to do — and everything on it can be checked from inside the product.
The boundary is the tenant column, and the filters that carry it.
Your workspace lives in a database shared with other free workspaces. Every read is scoped to your tenant, and that scoping is proven by tests rather than promised — but the separation is code, not a database.
The boundary is a database of your own.
Your workspace gets its own MySQL database, with its own credentials, on our servers. No query of ours can reach another customer's data from yours, because the connection does not open it.
The boundary is a machine of your own.
Your instance runs on its own virtual machine, with its own set of secrets. Docker is not a security boundary — the kernel is shared — so a paying customer gets a machine, not a container next to someone else's.
The boundary is your own infrastructure.
You run Galy yourself, on your machines, with your database and your keys. The instance never calls our control plane to serve a request: it keeps working when we are down, which is the only real proof that it does not depend on us.
Only the free tier shares a database, and its separation is then the tenant column plus the filters that carry it. Every other level puts a database — or a machine — between two customers.
This list is derived from what this instance actually has configured. An integration that is switched off does not appear here; one that is on cannot be left out.
api.anthropic.com
Le coach conversationnel : il lit vos objectifs pour vous répondre.
Le texte de vos échanges avec le coach, et l'arbre de vos objectifs. Aucune pièce jointe, aucun fichier.
Le registre de Galy, hébergé par Green Acres
Savoir quelle instance sert quel client, en mode mutualisé.
Le nom de votre instance et l'adresse à laquelle elle répond. Aucune donnée de projet ne s'y trouve.
Your objectives, your briefs and your specs never leave, except in the one case above where the coach reads them to answer you — and that case can be switched off.
The conversational coach is the only part that sends your content anywhere. An administrator cuts it from inside the product, and the outbound log then shows that nothing more leaves for that destination.
On a dedicated instance it goes further: the project-only build does not even compile the coach. An outbound flow that no code can emit is something you demonstrate, where a disabled one asks to be taken on trust.
Your data is neither sold nor handed over for advertising purposes. No account of ours exists on your instance by default: if support needs one, you create it like any other member, every one of its actions appears in your access log, and you revoke it when you are done.