subprocessors
Last updated: 23 September 2026
Under article 28 of the GDPR, ozeye discloses the third parties (“subprocessors”) that process personal data on behalf of our customers. This page lists each one, what it does, where it is established, what it receives, and what we can document about how long it keeps request content.
We notify customers of additions or replacements at least 30 days in advance by email and by updating this page. Business customers with a DPA can object as described in the DPA. Questions: privacy@ozeye.ai.
AI inference providers
A request is sent only to the provider that serves it (and, if that provider fails, to
another provider of the same model as a fallback). You can exclude providers in your
dashboard settings or with PUT /v1/account/provider-blocks; excluded
providers never receive your requests.
| Subprocessor | Location | Data processed | Retention of request content |
|---|---|---|---|
| Mistral AI Data Processing Addendum | Paris, France | Prompt and completion content of requests it serves | Zero data retention activated by Mistral for ozeye’s account (April 2026). It covers Mistral’s stateless API endpoints, such as chat completions, embeddings and OCR: input and output are not stored or logged longer than needed to produce the response. |
| Scaleway (Generative APIs) Contracts and Data Processing Agreement | Paris, France | Prompt and completion content of requests it serves | According to Scaleway’s published terms and data processing agreement (linked). |
| OVHcloud (AI Endpoints) Contracts and Data Processing Agreement | Gravelines, France | Prompt and completion content of requests it serves | OVHcloud states that AI Endpoints does not keep request content, only the data needed for billing (published terms, linked). |
| Inceptron AB Privacy Policy | Lund, Sweden | Prompt and completion content of requests it serves | According to Inceptron’s published terms (linked). |
| TensorX Ltd. Data Processing Agreement | Dublin, Ireland | Prompt and completion content of requests it serves | According to TensorX’s published terms and data processing agreement (linked). |
other subprocessors
| Subprocessor | Purpose | Location | Data processed |
|---|---|---|---|
| Hetzner Online GmbH Data Processing Agreement | Server hosting: a virtual server running ozeye, its PostgreSQL database, the login system and the Monero payment software | Germany | Everything ozeye stores: account data, hashed API keys, usage and audit metadata, payment and invoice records, saved notebooks and presets, and the local copy of the encrypted backups. |
| Offsite backup storage | Offsite copy of the database backups | EU | Database dumps encrypted with GPG (AES-256) before upload; the provider cannot read them. Kept 30 days. |
| Linkup SAS Privacy Policy | Hosted web search (only when you enable it) | Paris, France | Search query text. ozeye has a signed zero-data-retention agreement with Linkup: queries are processed in memory in the EU, not stored and not used for training. ozeye itself keeps only billing metadata, never the query or the results. |
| Scaleway (Transactional Email) Data Processing Agreement | Email delivery: verification and recovery codes, the welcome email, product-update emails you opted into | Paris, France | Recipient email address and the email content. Individual emails are sent on demand; no contact lists are uploaded. Delivery events (bounces, complaints) come back to us so we stop mailing those addresses. |
| Mollie B.V. Data Processing Agreement | Card, iDEAL and Bancontact payments | Amsterdam, Netherlands | Payment amount and description from us; the payment details you enter on Mollie’s checkout. We receive the payment status, method and the country of your payment instrument. ozeye never sees card or bank account numbers. |
Each entry links to that company’s published terms, which apply to ozeye as to every customer. Where a row describes a specific arrangement (Mistral’s zero data retention for our account, the Linkup agreement), details are available on request to privacy@ozeye.ai.
EU data residency
Every subprocessor listed above is established in the European Union and processes the data in the EU. We do not transfer personal data to countries outside the EU/EEA, and we will not add a subprocessor outside the EU/EEA without prior notice.
Some features you choose to use make requests to services that are not our subprocessors: the page fetch tool requests the web page you asked for, MCP servers you add receive the requests you send them, the icon of an MCP server is looked up at Google’s favicon service by domain name, and browser notebooks download their runtime and Python packages from cdn.jsdelivr.net, wasm.marimo.app and PyPI. See the privacy policy for details.
what ozeye itself retains
ozeye never writes prompts or outputs to its database, logs or backups. Our records contain metadata only: time, model, provider, token counts and cost. Retention periods are in the privacy policy.
provider prompt caches
Several providers keep a prompt cache: the model’s internal state for the beginning of a prompt is held for a short time in the serving infrastructure, so a request that repeats the same beginning is faster and cheaper. This is what the “cached input” price on our pricing and model pages reflects. The cached state is derived from your content, stays inside the provider, never reaches ozeye, and is not shared between accounts, but it means something derived from a request can outlive that request for a while inside the provider. If this matters for your use case, exclude the providers concerned in your settings, or contact privacy@ozeye.ai for the specifics of the providers you use.
self-managed components (not subprocessors)
These run on ozeye’s own server at Hetzner. No other company operates them or has access to their data:
- PostgreSQL 17 - the database, self-hosted on our Hetzner server
- Ory Kratos - login and session management (Apache 2.0)
- Bitcart - Monero payment processing (open source)
- Bifrost - Go library inside ozeye that sends requests to providers (Apache 2.0, no external service)
change history
- 23 September 2026 - Retention of request content stated per provider as documented; added offsite backup storage; corrected the hosting description (self-hosted database on a Hetzner server); listed Bitcart as a self-managed component
- September 2026 - Published links to each subprocessor’s data processing terms
- August 2026 - Added Linkup as search subprocessor; removed Qwant, Mojeek and Wikimedia
- August 2026 - Added TensorX as AI inference subprocessor
- May 2026 - Added Inceptron as AI inference subprocessor
- April 2026 - Initial subprocessor list published
contact
For questions about subprocessors, copies of their data processing terms, or to object to a specific subprocessor, contact privacy@ozeye.ai.