RINDOGATAN LLC · Version 1.8 · 26 October 2026 · PrivacyCloud edition of 5 November 2026
These are the sub-processors of the free pilot on PrivacyCloud and of the paid subscriptions, the EU Subscription and the USD Subscription (Annex III of the data processing agreement, which covers all of them). The certifications shown with each one are that sub-processor's; we make their reports or certificates available on request (clause 14 of the DPA). Before adding or replacing one we give at least thirty (30) days' notice, by e-mail to each account's administrative address and on this page (clause 8 of the DPA). Within that period you may object on reasonable data protection grounds.
| Role | Provider | Products | Data location | Safeguard if accessed from the US | Certifications |
|---|---|---|---|---|---|
| Hosting platform (application and server functions) | Vercel | privacy program, AI governance program, vendor catalog | Frankfurt, EU (fra1 region), all three | DPF and SCCs | SOC 2 Type II, ISO 27001 |
| Database provider | Neon, LLC (part of the Databricks group; the data processing addendum of Databricks, Inc. applies) | privacy program, AI governance program, vendor catalog | Frankfurt, EU (eu-central-1), all three | DPF and SCCs | SOC 2 Type II, ISO 27001, ISO 27701 |
| E-mail provider: sign-in links and notices and, with the rights-request module, rights-request notices to requesters (name, e-mail, reference, staff message text). It keeps copies of the e-mails and their delivery logs for up to thirty (30) days | Resend | all three | United States | DPF and SCCs | SOC 2 Type II |
| E-mail service of our support and privacy addresses: receives the messages you and your users send us (support requests, rights requests, notices under this agreement) and our replies | Google LLC (Google Workspace) | all three | United States and other countries | DPF and SCCs | SOC 2 Type II, ISO 27001, ISO 27701, ISO 42001 |
| Payment processor (Subscription billing) | Stripe (RINDOGATAN LLC's account) | billing | United States and other countries | DPF and SCCs | PCI DSS Level 1, SOC 2 Type II |
| AI provider: produces the drafts your users ask for from the details of the record being drafted, with an open-weight model it runs on its own infrastructure (only when AI features are switched on by the administrator and your organisation has not added its own API inference key). It does not keep the requests or the results by default; with the setting we use (zero data retention), it does not keep them for reliability or abuse monitoring either | Groq, Inc. (GroqCloud) | privacy program, AI governance program | United States | SCCs, as the provider's documents state | SOC 2 Type II |
DPF: EU-US Data Privacy Framework. SCCs: European Commission standard contractual clauses. Certifications: the main certifications each sub-processor holds, as it publishes them; they are the sub-processor's, not Rindogatan's (clause 14). The payment processor handles the Customer's billing data partly as an independent controller; it is listed for transparency.
AI provider: the AI provider runs an open-weight model on its own infrastructure; it does not pass requests to other model providers. Its own sub-processors are listed on its published sub-processor page (https://trust.groq.com/subprocessors); that page is how you can follow changes among them (clause 8 of the DPA and clause 8 of the US Privacy Addendum). If your administrator adds your organisation's own API inference key, the AI features use your provider instead, under your own agreement with it, and that provider is not our sub-processor. AI features running on the AI engine we provide must not be used on records that contain the data listed in clause 4 of the DPA (special categories, criminal data and other sensitive data).
Vendor catalog: to build and keep up to date the catalog of public information about vendors, our own catalogue work sends vendors' public documents (such as privacy policies and data processing agreements) to Anthropic and, when that feature is switched on, to an AI gateway (OpenRouter, Inc.). No data from your account or your vendor portfolio is sent with them, so they take part in our own catalogue work and not as sub-processors of your data; they are mentioned here for transparency.
Sign in with Google (all three Services, only if the user chooses it): for the sign-in data Google LLC acts as an independent controller under its Controller-Controller Data Protection Terms; for that data it is not a sub-processor, and it is mentioned here for transparency. Google Workspace, in the table above, is a separate service in which Google acts as our sub-processor.