What a sub-processor is, and why this page exists
A sub-processor is any third party we engage that handles personal data as part of delivering our service — the company hosting the servers, the one delivering our email, the advertising platform our software uploads conversions to. They act on our instructions, under contract, and cannot use the data for their own purposes.
Enterprise buyers ask for this list during procurement, data-protection law expects controllers to know it, and platform reviewers look for it. Publishing it up front saves everyone a round of emails.
Claudphic (corporate — claudphic.com)
This website is a brochure. It has no database, no accounts and no customer data — the only personal data involved is server logs and any correspondence you choose to send.
| Sub-processor | Purpose | Data involved | Location |
|---|---|---|---|
| [[HOSTING PROVIDER]] | Website and application hosting, server logs | IP addresses, request logs, application data at rest | [[PROCESSING REGION]] |
| [[EMAIL PROVIDER]] | Business email and correspondence | Name, email address, message contents | [[PROCESSING REGION]] |
| [[DNS / CDN PROVIDER]] | Domain resolution, TLS termination, abuse protection | IP addresses, request metadata | Global edge network |
| Google Fonts (Google LLC) | Web font delivery on claudphic.com | IP address and user-agent, as part of the ordinary font request | Global edge network |
Claudphic Ads (the product)
The product holds real customer data, so its list is the one that matters for a data processing agreement. The authoritative version is maintained alongside the product at claudphicads.com; the entries below are reproduced here for completeness.
| Sub-processor | Purpose | Data involved | Location |
|---|---|---|---|
| Google Ads API (Google LLC) | Uploading offline conversions on a Claudphic Ads customer's instruction | Hashed identifiers and conversion events, sent on the customer's behalf | United States / global |
| Meta Conversions API (Meta Platforms, Inc.) | Uploading offline conversions on a Claudphic Ads customer's instruction | Hashed identifiers and conversion events, sent on the customer's behalf | United States / global |
| [[PAYMENT PROCESSOR]] | Subscription billing for Claudphic Ads | Billing name, email, payment method token, invoice records | India |
Google and Meta appear here because Claudphic Ads uploads conversion outcomes to them on a customer's instruction — that is the entire point of the product. Identifiers are hashed before transmission. Once uploaded, that data sits under Google's and Meta's own terms and retention rules, which is why the data deletion page is explicit that deleting with us does not delete at the platform.
How we choose them
- As few as possible. Every additional vendor is another place data can leak and another contract to hold. The list is short on purpose.
- Contractually bound. Each is engaged under terms that restrict processing to our instructions and require appropriate security.
- No data brokers, ever. We do not buy contact data, enrich records against third-party datasets, or sell data to anyone. That is not a current-policy statement; it is a category of vendor we will not engage.
Changes to this list
Customers get at least thirty days' notice before a new sub-processor begins processing their data, sent to the account's billing contact. That window exists so you can object, ask questions, or terminate if the change is unacceptable to you.
If a change is forced on us faster than that — a provider shutting down, or an urgent security migration — we will tell you as soon as we know and explain why the notice was short.
Requesting a data processing agreement
A signed data processing agreement, including this list as an annex, is available to Claudphic Ads customers on request through the contact page. If your organisation needs its own paper rather than ours, send it over and we will review it.
Sub-processors, summarised
- Claudphic publishes a complete, named list of every third party that processes data on its behalf, rather than describing them generically.
- The corporate website involves only hosting, email, domain infrastructure and web fonts; it holds no customer accounts or database.
- Claudphic Ads additionally uses the Google Ads API and Meta Conversions API to upload conversions on a customer's instruction, with identifiers hashed before transmission, plus a payment processor for billing.
- Customers receive at least thirty days' notice before a new sub-processor begins processing their data.
- Claudphic does not buy, sell, broker or enrich personal data with any third party.
- A signed data processing agreement with this list annexed is available to customers on request.