EU sovereignty

Where is TransformRadar data hosted?

TransformRadar hosts all customer data on Clever Cloud in Paris. The application, the PostgreSQL database, file storage and AI inference all run inside EU jurisdiction on European-owned infrastructure, with no US CLOUD Act exposure. Email is sent through Brevo in France. No provider we use trains any model on your data.

Every provider in the chain, and where it sits

Data residency is only meaningful if it holds for the whole processing chain, not just the database. A European region operated by a US-owned company still sits inside the reach of the CLOUD Act. TransformRadar is built on European-owned providers end to end.

Application and database — Clever Cloud, Paris
The web application, the background workers, and the PostgreSQL database all run on Clever Cloud, a French company operating in French data centres.
File storage — Clever Cloud Cellar
Attachments, exports, and generated documents are stored in Cellar, Clever Cloud’s S3-compatible object storage, in the same jurisdiction as the database.
AI inference — Mistral La Plateforme, Paris
Every AI feature calls Mistral, a French provider. Prompts and completions do not leave the EU, and the provider does not train on the data we send.
Transactional email — Brevo, France
Magic links, invitations, notifications, and digests are delivered through Brevo, a French email provider.

Why the CLOUD Act matters even for an EU region

The US CLOUD Act lets US authorities compel a US-based provider to produce data it controls, wherever in the world that data is physically stored. Choosing the Frankfurt or Paris region of a US hyperscaler reduces latency and satisfies a data-residency checkbox, but it does not remove that exposure, because the legal obligation attaches to the provider rather than to the disk.

For a transformation programme this is not abstract. The programme record contains the business case, the benefits the board was promised, the risks nobody wants in a press release, and the names and assessments of the people running it. That is the material a sovereignty requirement exists to protect.

TransformRadar avoids the exposure by not having a US provider in the chain at all. There is no US subprocessor to compel.

Is TransformRadar GDPR-compliant?

TransformRadar is built to be used in a GDPR-compliant way, and the design decisions that make that possible are structural rather than contractual. All processing happens inside the EU by default, so there is no third-country transfer to justify with standard contractual clauses.

When your organisation uses TransformRadar, your organisation is the controller of the personal data it enters about its own employees, contractors, and programme stakeholders. ThejnValue Best Focus ApS, a Danish company, acts as processor on your instructions, and a data processing agreement is available. Full detail — categories of data, retention, subprocessors, and your rights — is in the privacy policy.

How your data is kept apart from every other customer

EU hosting answers where the data sits. Tenant isolation answers who can reach it. TransformRadar is multi-tenant, and separation is enforced in the database rather than in application code that a future bug could bypass.

Row-level security, forced
Every tenant table has PostgreSQL row-level security enabled and forced, filtered by the active organisation. The runtime database role cannot bypass it.
Fail-closed, not fail-quiet
A query that arrives without an organisation context raises an error rather than silently returning nothing — an isolation failure is loud, not invisible.
A cross-tenant test suite on every change
An automated suite sets up two organisations and attempts to reach one from the other by guessing identifiers, manipulating URLs, and forging headers. It runs on every pull request.
Audited access
Meaningful actions are written to an audit log that records who did them and through which surface — the product UI, the assistant, or an external agent.

What happens to your data when AI features run

AI in TransformRadar reframes your own programme data — it does not consult an outside corpus and it does not invent facts. Every prompt carries the structured input that licenses the claims in the output, and every output is schema-validated before a person sees it.

Each AI artefact is a draft its owner edits and approves. Nothing is circulated automatically. Prompt inputs and outputs are retained for 30 days in a single audited table and then deleted, with only cost metadata kept.

There is one deliberate exception to EU-only egress, and it is opt-in: an organisation may connect its own external AI agent over the Model Context Protocol. That is the customer choosing their own provider, it is off by default, and an organisation administrator has to acknowledge the egress before it can be switched on.

Questions people ask

Where is TransformRadar data hosted?
On Clever Cloud in Paris. The application, the PostgreSQL database, and object storage all run on French infrastructure operated by a French company, inside EU jurisdiction.
Is TransformRadar exposed to the US CLOUD Act?
No. There is no US-owned provider in the processing chain — hosting, storage, email, and AI inference are all European providers, so there is no US entity that could be compelled to produce your data.
Does any AI provider train on our programme data?
No. AI inference runs on Mistral La Plateforme in Paris, and no provider that reserves the right to train on customer data is eligible for use in TransformRadar.
Can we get a data processing agreement?
Yes. Your organisation is the controller of the data it enters and ThejnValue Best Focus ApS acts as processor on your instructions. A data processing agreement is available on request.
Can we export everything if we leave?
Yes. A full export of your organisation’s data is available to organisation administrators, and remains available during the read-only grace period after a subscription ends.