Data protection · reviewed on 27 October 2026
Who handles your data, what for and where
AIM CODEX uses these companies to run. Each one handles only the data it needs for its part. Your account data and your documents are stored in the European Union.
Announced change · from 10 November 2026
The AI functions will stop going through OpenRouter (USA) and will run on Mistral AI SAS (France), in its European region, with zero retention. From that day, the text and recordings you send to the AI stay in the European Union. Announced on 27 October 2026. If you object, write to hola@aim-codex.ai before that date (data processing agreement, subprocessors clause).
Railway Railway (USA)
- What for
- Hosting the application and the database.
- What data
- Everything you keep in AIM CODEX: account, documents, seals and activity log.
- Where
- Servers in the Netherlands (European Union).
Resend Resend (USA)
- What for
- Sending the service’s emails: notices, links and reminders.
- What data
- The recipient’s address, the subject and the content of the notice.
- Where
- European region (Ireland).
Migadu Migadu-Mail GmbH (Switzerland)
- What for
- The hola@aim-codex.ai mailbox and fallback sending if Resend fails.
- What data
- The messages you write to us and, only as a fallback, the same data as Resend.
- Where
- Switzerland (a country with a European Union adequacy decision).
OpenRouter OpenRouter, Inc. (USA)
- What for
- Taking to the AI models the text you ask them to draft, review or explain.
- What data
- Only what you send to the AI: the text you ask it to draft, review or explain and, if you use meeting minutes, the recording. No data retention and no use for training models (we require this on every request).
- Where
- United States; the model is run by providers that may be outside the European Union. It stops being used on 10 November 2026, replaced by Mistral AI in the European Union (see “Announced change”).
Paddle Paddle.com Market Limited (United Kingdom)
- What for
- Charging and invoicing the paid plans. Paddle makes the sale as a reseller: it handles that data as controller, not on our behalf.
- What data
- Payment and billing data, which you enter directly with Paddle; we never see it.
- Where
- United Kingdom (a country with a European Union adequacy decision).
Third parties that handle no personal data
- OpenTimestamps calendars. They receive only each document’s SHA-256 fingerprint to anchor it in Bitcoin: neither the document nor any personal data. More
- GoDaddy. Manages the DNS of the aim-codex.ai domain. It does not handle our customers’ data.
- Time-stamping authorities (DigiCert, Sectigo, FreeTSA). They receive only each document’s SHA-256 fingerprint to return an RFC 3161 timestamp: neither the document nor any personal data.