Subprocessors
The companies that process personal data on our behalf, as described in section 7 of our Privacy Policy. Every one of them is bound by a data processing agreement we hold. We update this page before adding anyone new.
Subprocessors
Vendors we choose and engage to run ClarNow. Each one is bound by a data processing agreement we hold directly, and we remain liable to you for their work. This table is Annex III of our Data Processing Agreement; section 7 of the DPA governs how it changes and how you can object.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Google Cloud (Cloud Run, Firebase Hosting) | Application hosting and static site delivery | All service data in transit and at rest | EU |
| MongoDB, Inc. (Atlas) | Primary database | Accounts, forms, form responses | EU |
| Cloudflare, Inc. (R2) | File storage for uploads and form assets | Files uploaded through forms, images | EU |
| Stripe Payments Europe, Ltd. | Subscription billing, and payments collected through the Payment field | Billing name, email, address, tax status, payment metadata | Ireland; group companies in the USA |
| Amazon Web Services EMEA SARL (Amazon SES) | Transactional email (sign-in, receipts, form notifications) | Email address, message content | EU; group companies in the USA |
| PostHog, Inc. | Product analytics and session replay on clarnow.com | Pseudonymous usage events, IP address, device and browser data | EU — hosted at eu.i.posthog.com |
| Google Ireland Ltd. (Google Sign-In, Google Drive) | Optional sign-in, and optional upload of form files to your Drive | Email, name, profile picture; files you route to Drive | EU; group companies in the USA |
| Google Ireland Ltd. (Google Analytics) | Traffic and audience analytics on clarnow.com | Pseudonymous usage events, IP address, device and browser data | EU; group companies in the USA |
Providers you can connect yourself
These are not subprocessors, and they are not part of Annex III. They are bring-your-own-key: your organisation connects one with an API key you supply, and we neither pick a provider nor hold a key of our own. If nobody in your workspace connects one, none of them ever receives your data — and only the one you connect ever does.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Anthropic PBC | AI-assisted features, only if your organisation connects it | Whatever data that feature sends it | USA |
| OpenAI, L.L.C. | AI-assisted features, only if your organisation connects it | Whatever data that feature sends it | USA |
| Google LLC (Gemini API) | AI-assisted features, only if your organisation connects it | Whatever data that feature sends it | USA |
| Groq, Inc. | AI-assisted features, only if your organisation connects it | Whatever data that feature sends it | USA |
Because the account is your own, your agreement with that provider — not a data processing agreement of ours — governs how they handle the data there, including whether they train on it. That varies by provider and API tier, so check the one you connect. You can reverse the choice at any time by disconnecting the provider.
We email every account holder before a new subprocessor starts processing your data — you don't need to subscribe to anything to hear about a change.
Tracking a form owner can add to their own form
These are also not subprocessors. Unlike the integrations above, a provider here runs directly in a respondent's browser — a form owner can choose to load it on a specific form they publish, using their own pixel or container ID. We never enable one ourselves, and a form carries none of them unless its owner turned one on. See section 6 of our Privacy Policy.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Meta Platforms Ireland Ltd. (Facebook Pixel) | Ad tracking on a form, only if the form owner enables it | Browser and device data, and form interactions, sent directly from the respondent’s browser to Meta | USA and other Meta regions |
| Google LLC (Tag Manager) | Loads a tag container on a form, only if the form owner enables it | Whatever the form owner’s own container is configured to collect and send | Depends on what the form owner’s container loads |
Because the form owner configures it with their own account, their agreement with that provider — not a data processing agreement of ours — governs what happens to the data there. If you are a respondent with a question about this, the form owner is who decides it, not us — see section 5 of our Privacy Policy.
Getting a respondent's consent before one of these fires, and having a legal basis to run it at all, is the form owner's responsibility — not ours. We may offer an optional consent banner as a tool, but a form owner can just as well use their own consent management platform, or a consent step inside their own Tag Manager container, or nothing at all — that choice, and answering for it, is theirs.