1. About this list
To run Chernion we use a small number of service providers that process personal data on our behalf or receive it to perform a service. This page lists them. It is referenced by the Privacy Policy and by the Data Processing Agreement and is part of that agreement.
2. How we notify changes
When we intend to add or change a sub processor that processes Customer Personal Data under the Data Processing Agreement, we will update this page, and business customers may object on reasonable data protection grounds as set out in that agreement. We encourage you to check this page for the current list.
3. Current sub processors
| Provider | Service | Data involved | Where |
|---|---|---|---|
| OpenAI | Model inference for the GPT and Codex families | The content of requests routed to those models | United States, under a lawful transfer mechanism |
| Anthropic | Model inference for the Claude, Opus, and Fable families | The content of requests routed to those models | United States, under a lawful transfer mechanism |
| Model inference for the Gemini family | The content of requests routed to those models | United States and other regions, under a lawful transfer mechanism | |
| Mollie | Card and wallet payments and value added tax invoicing | Billing details and payment amounts | European Union (Netherlands) |
| PayerURL | Crypto hosted checkout | Billing details and payment amounts for crypto top ups | Outside the European Economic Area, under a lawful transfer mechanism |
4. Used only in certain cases
| Provider | Service | Data involved | When |
|---|---|---|---|
| Social sign in | Your Google account email, name, and identifier | Only if you choose to sign in with Google | |
| GitHub | Social sign in | Your GitHub account email, name, and identifier | Only if you choose to sign in with GitHub |
Self custodial crypto deposits settle on public blockchain networks. Those networks are public infrastructure rather than processors acting on our behalf, and a transaction recorded on them is public by design.
5. Infrastructure providers to be confirmed
We also rely on a cloud hosting and infrastructure provider that runs the service, and a transactional email provider that delivers verification, sign in, and invoice emails. The exact named vendors are to be confirmed and will be listed here by name. They process technical and account data needed to run the service and to send these messages.
6. Objecting to a sub processor
Business customers who have entered the Data Processing Agreement may object to a new sub processor on reasonable data protection grounds, as set out in that agreement. Write to [email protected].
7. Contact
Questions about this list can be sent to [email protected].