AI Agent Sovereignty: Four Answers, Not One

A DSI asking where an AI agent's code and data actually go gets four different answers at Atipol, not one. Repository content stays on your own machines; only a file list and version reference are sent. Project data such as tickets is stored encrypted per organization, under a hardware master key, with every access checked and logged, which is not the same as legal immunity.
What "AI agent data sovereignty" actually means
A DSI or RSSI typing "souveraineté agents IA" or "where does my code go" into Google or ChatGPT is usually trying to answer one practical question before signing with any AI agent platform: what leaves our machines, what gets stored somewhere else, and who can be forced to hand it over. That question has at least four separate answers, not one.
The first answer is about code: does the platform read, copy, or transmit your repository content. The second is about project data: tickets, specifications, and history generated while agents work. The third is about encryption: what algorithm protects that data, and who holds the keys. The fourth is about jurisdiction: which country's laws can reach the infrastructure, regardless of which region the data physically sits in.
This article answers all four for Atipol, based only on what Atipol states at https://atipol.ai/llms-full.txt, checked here against the live page, alongside an official French regulator's note on a separate but related risk: hosting inside the EU does not automatically remove exposure to a non-EU parent company's legal obligations.
What never leaves your machines: repository content
Atipol states plainly, at https://atipol.ai/llms-full.txt, that repository content stays on your machines. A delivery sends the reference of the delivered version and the list of changed files, never their contents. An agent working inside your repository does not transmit file contents or diffs back to Atipol's servers at any point in that delivery step.
What Atipol does receive, and store, is narrower than the repository itself: the scope and the list of delivered files, meaning file paths and line counts, stored encrypted per organization. That is a meaningful distinction for a DSI evaluating exposure: metadata about what changed is stored in Atipol's SaaS, even though the changed content itself is not.
This is the part of the sovereignty question that is usually the most urgent for a team worried about proprietary code leaving its own infrastructure. It does not, however, answer the second question, what happens to the project data generated around that code, which is addressed next.
What Atipol's SaaS does store, and how it is encrypted
Project data, tickets, specification documents, and ticket history, is stored in Atipol's SaaS rather than on a customer's own machines. It is encrypted per organization, under a hardware master key, so one organization's data is never pooled with another's.
Every access to that data is checked against the person's rights and logged: each action is attributed to a person, an agent, and a machine, which gives a DSI a reviewable trail rather than a black box.
How stored project data is protected, as a diagram:
Encrypted per organization means the server opens project content according to a person's rights in order to run the product; it does not mean the vendor could never read it. A DSI comparing vendors should keep that distinction in view rather than read "encrypted" as "unreadable by the vendor".
Access to that stored data is also scoped rather than all-or-nothing. Atipol describes, at https://atipol.ai/llms-full.txt, permissions set tool by tool, where a new tool starts out denied until a person approves it, and lists named roles, including Admin, Workspace owner, Project lead, Contributor, Reader, and Auditor, each with a different reach into a project's stored data. That role structure is a separate control from encryption itself, and a DSI evaluating sovereignty should check both.
Your data is encrypted per organization, under a hardware master key; every access is checked against your rights and logged.
The honest limit: where a key is hosted does not mean immunity from non-EU law
Where data and keys are hosted is a real control. It does not, on its own, remove every legal question a DSI might reasonably ask, because a cloud provider operating the underlying infrastructure may itself be subject to obligations outside EU law, the exact scenario Chapter V of the GDPR, Regulation (EU) 2016/679, on international data transfers, was written to address.
The CNIL made a closely related point in a note dated 19/07/2024: data stored by a provider subject to non-European law, such as a hosting company whose parent company sits in the United States, can be exposed to a risk of having to communicate that data to that country's public authorities, even where the hosting itself happens inside the EU.
The CNIL's own note frames this risk as most often considered limited specifically for non-sensitive data entrusted to a provider from a country recognized as offering an adequate level of protection, such as the United States under the European Commission's adequacy decision, and it reserves its strongest concern for the most sensitive categories of data, such as large health databases. A DSI should read that narrower nuance rather than generalize it to all processing, or treat the risk as either absent or certain.
The operational conclusion for a team evaluating Atipol, or any SaaS platform with a comparable architecture, is to separate two different questions: where is the data physically hosted, and which country's legal obligations can reach the company operating that hosting. Atipol addresses the first question; it does not, and should not, claim to resolve the second on a customer's behalf. Atipol's guide on agentic AI, GDPR, and the AI Act, at https://atipol.ai/agentic-ai-blog/agentic-ai-gdpr-ai-act, covers the compliance side of that second question in more depth.
What's planned, not available today: customer key and self-hosting
Two capabilities that would change this picture are listed by Atipol as planned, not shipped. A customer-held encryption key, kept in the customer's own vault and revocable by the customer rather than by Atipol, is planned for the Enterprise plan. A self-hosted version of the platform, running on infrastructure the customer controls entirely, is listed as a later, Enterprise-oriented capability.
Neither is available on any plan today. A DSI whose sovereignty requirement cannot be satisfied by organization-level encryption with a provider-held key, under the architecture described above, should treat these two items as a timeline question for Atipol directly, not assume either is already live.
Atipol places the customer key, at https://atipol.ai/llms-full.txt, under its Enterprise plan description, alongside an extended audit log, both listed as planned rather than available today. Self-hosting is not tied to that same plan description; it appears separately, under a "coming soon" list, with no date more specific than "later." A DSI with a hard sovereignty deadline should ask Atipol directly for a committed date on either item rather than infer one from that wording.
A hosting location is not a sovereign cloud certification
It is worth being precise about what a hosting location does and does not establish. Hosting data in a given country is not the same thing as a sovereign cloud certification such as SecNumCloud, and Atipol does not claim that certification. For the jurisdiction question, what matters is which company operates the underlying infrastructure, a question worth putting to every vendor.
What stays local, what's stored, and what's planned: one table
The table below separates the sovereignty question into its four parts, using only what Atipol states at https://atipol.ai/llms-full.txt and what the CNIL's note states, rather than treating sovereignty as one single yes-or-no answer.
Reading it top to bottom separates a claim that is fully true today, repository content, from one that is only partly true, project data, stored but encrypted, from one that is not made at all, immunity from non-EU legal reach, from one that is only a roadmap commitment, a customer-held key or self-hosting. Collapsing those four into a single "is Atipol sovereign" question obscures exactly the distinctions a DSI needs before signing.
| Question | Status today | Where it's confirmed |
|---|---|---|
| Repository content (code, diffs) | Stays on your machines; never sent | Atipol, llms-full.txt, 10/11/2026 |
| File paths and line counts of a delivery | Sent and stored, encrypted per organization | Atipol, llms-full.txt, 10/11/2026 |
| Project data (tickets, history) | Stored in Atipol's SaaS, encrypted per organization | Atipol, llms-full.txt, 10/11/2026 |
| Master key | Hardware master key; every access checked and logged | Atipol, security page |
| A vendor that can never read the data | Not claimed; the server opens content according to rights | Atipol, llms-full.txt, 10/11/2026 |
| Immunity from non-EU legal reach on the cloud provider | Not claimed; flagged as a general risk for non-EU-law providers | CNIL, 19/07/2024 |
| Customer-held key / self-hosting | Planned for Enterprise; not available today | Atipol, llms-full.txt, 10/11/2026 |
Common mistakes when assessing AI agent sovereignty
The first mistake is treating "our code stays local" and "our data is sovereign" as the same claim. On Atipol, the first is true for repository content; the second is more limited, since project data is stored by the SaaS and the master key sits on infrastructure operated by a US-headquartered cloud provider, even from a French region.
The second mistake is reading "encrypted per organization" as a promise that the vendor can never read the data. Encryption per organization keeps one customer's data apart from another's and ties every access to a person's rights; it is not the same as a design in which the vendor itself can never open anything, and a DSI should not translate "encrypted" into that stronger claim on a vendor's behalf.
The third mistake is assuming a planned roadmap item, such as a customer-held key or self-hosting, is already available because a competitor offers something similar today. Ask any vendor in this space for a committed date on roadmap items, and re-check that date at renewal rather than at signing only.
A fourth, smaller mistake is stopping the review at encryption and key custody without also checking tool-level permissions and the audit trail, since a sovereignty review that ignores who can act on stored data inside the platform is incomplete even when the encryption answer is accurate.
Atipol sets out how it protects data and logs every access at https://atipol.ai/security, alongside its guide on securing MCP servers connected to agents, at https://atipol.ai/agentic-ai-blog/mcp-security, which covers a closely related exposure a sovereignty review should not skip.
Frequently asked questions
Does my source code ever leave my own machines when I use Atipol?
No, not in content form. Repository content stays on your machines, and a delivery sends only the reference of the delivered version and the list of changed files, never their contents. That list, file paths and line counts, is stored encrypted per organization, but the code itself is not. This split, content never sent versus delivery records stored, is the distinction a sovereignty review needs to keep in view.
How is project data protected in Atipol?
Your data is encrypted per organization, under a hardware master key; every access is checked against your rights and logged. The server opens project content according to a person's rights in order to run the product, so "encrypted" should not be read as "unreadable by the vendor".
Does where the master key is hosted make Atipol immune to US law?
No claim like that is made, and a hosting location does not resolve that question on its own. The CNIL noted on 19/07/2024 that data held by a provider subject to non-European law, such as one with a US parent company, can face a risk of disclosure to that country's authorities, even when hosted inside the EU; it frames this risk as most often limited specifically for non-sensitive data handled by a provider from an adequate country, not as absent.
Sources
- Atipol, llms-full.txt, last updated 10/11/2026
- CNIL, Cloud : les risques d'une certification européenne permettant l'accès des autorités étrangères, 19/07/2024
- Regulation (EU) 2016/679 (GDPR), Official Journal, 04/05/2016
- Atipol, security page, updated 09/11/2026
The public demo shows a fictional organization at work, no account needed. The free plan includes a project, three agents and an agent lead.
