Subprocessors
Version 1.6 · last updated 12 November 2026
This list names the third-party providers Uprelic GmbH engages to provide Strom, Uprelic's decision API, together with what each one does, which data it handles, where, and under which transfer safeguard. It forms part of the Data Processing Agreement (the "DPA"), § 8.
Where your content goes
Requests are processed on servers in the EU, operated for Uprelic by one cloud provider, OVHcloud, in its data centre in Gravelines, France: a server that runs the API and the database, and a GPU server that runs the Strom model (Uprelic's own, fine-tuned from open model weights). The GPU server reaches the internet only to download the model's weights when it starts, and sends request content nowhere but back to our API. TLS ends on our servers and on OVHcloud's gateway in front of the GPU server, so no other provider sees your traffic unencrypted.
Two providers hold the content of your requests, both in the EU: the cloud provider (OVHcloud), which runs the servers, and the backup storage provider (Scaleway), which stores our backups in the Netherlands. The backups are encrypted by Uprelic before they leave our servers, and Scaleway holds no key.
Apart from Cortecs, which is used only if you turn on the optional improvement of document extraction, the other providers never receive request content; they handle account, sign-in and billing data only.
No AI model providers by default. No third-party AI model provider receives your requests, images or responses, unless you turn on the optional improvement of document extraction (Terms, § 9.9). Then Cortecs receives samples of your documents.
No analytics providers. We use no analytics, advertising or tracking services.
Cloud provider
| Item | OVHcloud |
|---|---|
| Name and entity | OVH SAS (France), under its Data Processing Agreement (French law) |
| Website | ovhcloud.com |
| Purpose | Running the servers for the Strom API, database and model and for our website analytics |
| Data involved | All account and request data at rest and in processing, including request content; IP addresses and connection metadata |
| Location | Data centre in Gravelines, France (EU) |
| Transfer safeguard | Not required (EU) |
Backup storage provider
| Item | Scaleway |
|---|---|
| Name and entity | Scaleway SAS (France), under its Data Processing Agreement (French law) |
| Website | scaleway.com |
| Purpose | Object storage for encrypted backups |
| Data involved | Encrypted backups of the whole database (encrypted by Uprelic before upload; Scaleway holds no key) |
| Receives request content | Only in encrypted form, inside the backups |
| Location | Amsterdam, Netherlands (EU) |
| Transfer safeguard | Not required (EU) |
Amazon Web Services (Amazon SES)
| Item | Details |
|---|---|
| Name and entity | Amazon Web Services EMEA SARL |
| Website | aws.amazon.com |
| Purpose | Sending sign-in emails (magic links), the welcome email and notices about the account, such as a low balance |
| Data involved | Email address and the content of these emails |
| Receives request content | No |
| Location | Amazon SES region eu-central-1 (Frankfurt, Germany) |
| Transfer safeguard | EU region; for any access from outside the EEA, the EU Standard Contractual Clauses in the AWS DPA; AWS is also DPF-certified |
Stripe
| Item | Details |
|---|---|
| Name and entity | Stripe Payments Europe, Ltd. (Ireland) |
| Website | stripe.com |
| Purpose | Payments for prepaid top-ups, invoices, tax calculation, customer portal |
| Data involved | Billing details, payment details, tax ID where given, invoices, Stripe customer ID |
| Receives request content | No |
| Location | Contracting entity in Ireland (EU); also the USA and other countries where Stripe operates |
| Transfer safeguard | EU–US Data Privacy Framework and EU Standard Contractual Clauses (Stripe Data Transfers Addendum) |
| Note | Stripe is an independent controller for fraud prevention, risk and regulatory compliance |
Google (only with Google sign-in)
| Item | Details |
|---|---|
| Name and entity | Google Ireland Limited / Google LLC — an independent controller, not our processor |
| Website | google.com |
| Purpose | Sign-in to the console with a Google account |
| Data involved | The data exchanged for sign-in, such as your email address and Google account identifier |
| Receives request content | No |
| Location | Google's global data centres, including the USA |
| Transfer safeguard | EU–US Data Privacy Framework and EU Standard Contractual Clauses (Google Controller-Controller Data Protection Terms) |
Cortecs (only with improvement of document extraction)
| Item | Details |
|---|---|
| Name and entity | Cortecs GmbH (Vienna, Austria) |
| Website | cortecs.ai |
| Purpose | AI inference for the optional improvement of document extraction |
| Data involved | Samples of documents sent to POST /v1/extract, with the account's field names and descriptions and Strom's answers on them |
| Receives request content | Yes, but only from accounts that turned the feature on under Billing |
| Location | EU |
| Transfer safeguard | Not required (EU) |
Not on this list
- Our own components. The API, the database and the Strom model are Uprelic's own systems on the servers operated for us, not services of a third party.
- The IP geolocation database. We look up a visitor's country in a database file from DB-IP that is stored on our servers. No data is sent to DB-IP.
- Our DNS provider. It answers lookups for our domain names and never receives your traffic or data.
- Image hosts you point us to. When you reference an image by URL, we download it from that address on your instruction. The operator of the address is not our subprocessor.
- Other AI model providers, and analytics providers. We use none.
Changes to this list
We announce any new or replacement subprocessor at least 30 days before it takes effect, by email to the address of your account and by publishing the change, with its effective date, on this page. You can object before the change takes effect, as described in § 8 of the DPA. Cortecs is the exception when added: it receives data only from accounts that turn the feature on, and turning it on is your agreement to it (§ 8.9 of the DPA). Every version of this list carries a version number and a date.
Questions
Questions about this list: privacy@uprelic.com.