Skip to content
Pillion
Join the waitlist
Explore Pillion

Sovereign source. Private agent context.

Our European storage boundary covers native source history, agent tasks, checkpoints, saved conversations, and review evidence. External models, customer-operated harnesses, and billing have separate processing arrangements.

Source and agent context share the core storage commitment. See the processing boundaries below.

Allowed geography

For Pillion’s core data residency commitment, allowed geography means the EU member states, Iceland, Liechtenstein, Norway, the United Kingdom and Switzerland.

European Union
All 27 member states.
GDPR applies directly.
EEA
Iceland, Liechtenstein, Norway.
GDPR applies through the EEA agreement.
Adequacy
United Kingdom, Switzerland.
Current EU adequacy decisions; reviewed when they are renewed.

Where each class of data rests

Native source history and changesSource and product storesEU regionAt rest
Agent tasks and review evidenceProduct storeEU regionAt rest
Saved conversations and checkpointsProduct and object storesEU regionAt rest
Git LFS objectsBlob prefixEU regionAt rest
Issues, pull requests, commentsPostgresEU regionAt rest
Attachments on conversationsBlob prefixEU regionAt rest
Workflow artefacts and cachesBlob prefixEU regionAt rest
SecretsSealed storeEU regionEnvelope, per-owner key
Backups and replicasObject storageAllowed geography onlyAt rest
Transactional emailEU email providerAllowed geography onlyIn transit

Subprocessors

Core source and agent data uses operators incorporated in allowed geography. Stored data stays within that geography. Paddle handles billing data separately under its own privacy terms.

Compute and network
Scaleway SAS
France · EU region, same as the storage.
Object storage and runners
Scaleway SAS
France · EU object storage and bare metal.
Transactional email
Scaleway SAS · TEM
France · EU account and security mail.
Payments
Paddle · Merchant of Record
Billing data only · independent controller with international processing; separate from core data residency.
Read about Paddle billing data →

Agent and model processing

Your existing harness and chosen model provider control their own processing. Saving their conversations in Pillion does not change those processing locations. Pillion Review uses your provider key, or Pillion’s Nebius account after an organisation owner enables managed review. Core storage residency does not promise EU-only inference. See our subprocessor list. Explore agent workflows and model choice.

Who can read source and agent context

Source access follows repository visibility and permissions. Task evidence requires current repository and task access.
Saved conversations remain private to their creator. Sharing grants current repository collaborators access to selected events, including on public pull requests.
A named on-call engineer, only on a break-glass path that writes to your audit log.
No model training on source, tasks, checkpoints, saved conversations, or other customer content. No third-party analytics inside the authenticated product.
A lawful order from a competent authority in the EU or the UK, which we will tell you about unless legally barred.

Encryption at rest, OIDC SSO controls, and rulesets protect source and collaboration. Source exports use Git-compatible formats. Private conversations and other agent metadata require separate exports with current authorisation. Detail lives on the security page.

Straight answers

Is Pillion a US company with an EU region?

No. Pillion Ltd is registered in England and Wales, a jurisdiction holding a current EU adequacy decision, and the operators of the core source and product-data path are incorporated in allowed geography. An EU region operated by a non-EU parent does not meet the definition we hold ourselves to, because the parent remains subject to extraterritorial disclosure law.

Do backups ever leave the region?

Core source and collaboration backups and replicas stay inside the European geography described on this page: the EU, the EEA, the UK or Switzerland.

Is my code used to train models?

Pillion does not use customer content, including saved agent conversations, to train models. If you enable AI review, code context goes to your chosen provider using your key, or to Nebius through the managed service. The subprocessor list explains that separate processing path.

What if a government asks for data?

We require a lawful order from a competent authority in the EU or the UK, we disclose only what the order compels, and we tell the affected customer unless legally barred. Aggregate counts are published.

Can I keep CI compute entirely under my control?

Yes. Attach your own runners and no job ever executes on our compute. Caches and artefacts those jobs produce are still stored in-region, encrypted at rest.

What certifications do you hold today?

None yet, and we will not imply otherwise. Controls are mapped against ISO 27001 and the audit is planned; until it is done, this page says planned.