| Cloudflare, Inc. | CDN, edge compute, DDoS protection for validant.ai and platform.validant.ai; Email Routing, which forwards replies sent to the Trust Signal address signal@validant.ai to the editor's mailbox | Technical metadata (IP, request headers, response codes), request bodies in transit; forwarded replies in transit | Global network: a request is served by the data centre nearest the visitor | EU SCCs + Swiss revFADP addendum; data processing addendum in place |
| Supabase, Inc. | Database, file storage and server functions of the platform at platform.validant.ai, including our internal marketing tool | Platform account and audit records and content uploaded to the platform; records of the marketing tool, including comments on our LinkedIn posts | Switzerland (Zurich): hosted on Amazon Web Services, region eu-central-2; a download may pass Supabase's global delivery network | Stored in Switzerland; Supabase DPA (part of its terms of service) with EU SCCs and its Swiss addendum for any access from outside Switzerland |
| Okta, Inc. (Auth0) | Sign-in to platform.validant.ai: accounts, login and multi-factor authentication | Email address, name, login identifiers, sign-in and security events | European Union (Auth0 EU region) | Okta's Data Processing Addendum, which incorporates the EU SCCs |
| Google LLC | AI features of the platform on the paid Gemini API: assistant answers, concept explanations, guideline drafts, agent tasks, and the automatic personal-data check of community screenshots before they are published. Website analytics (Google Analytics 4), only with your cookie consent | Text users enter into these features and the context the feature sends with it; community screenshots before publication; for analytics, pseudonymous usage data | United States and other countries where Google has facilities | Google's processor data protection terms; on the paid Gemini API, Google does not use prompts or responses to improve its products |
| OpenAI Ireland Limited | Language and image models for our own research and editorial work: research batches on public sources and illustrations for the Trust Signal newsletter; search vectors of our own knowledge catalogue | Public articles and research material, our own catalogue text; no platform feature sends users' questions or customer content to OpenAI | United States | OpenAI's Data Processing Addendum with EU SCCs; API data is not used for training |
| Stripe Payments Europe, Limited | Card payments for platform plans and credits. Payments are built but not yet switched on (test mode) | Account email of a user who opens checkout; once payments are live, the payment details entered at Stripe | Ireland and United States | Stripe Data Processing Agreement (part of the Stripe Services Agreement) with EU SCCs and the Data Privacy Framework, including the Swiss-US framework |
| Resend, Inc. | Transactional email (account, demo replies, notifications) and the Trust Signal newsletter: each issue and the subscription emails (confirmation, preferences, unsubscribe), sent from signal@validant.ai | Recipient email, message content, delivery metadata | United States; validant.ai mail is sent from its EU region (Ireland) | EU SCCs + Swiss addendum; processor is DPF-certified |
| METANET AG | Swiss mail hosting of the editor's mailboxes: replies to the Trust Signal address are forwarded there, and editorial notices go to the editor. Sends no newsletter mail since 24 October 2026 | Replies from readers (their email address and message); editorial notices without subscriber data | Switzerland (Zurich) | None: Swiss provider, mail server in Switzerland |
| GitHub, Inc. | Source control, CI/CD, issue tracking for validant.ai codebases | Code, build artefacts, issue metadata; no customer content | United States | EU SCCs + Swiss addendum; Microsoft DPF certification applies |
| Anthropic, PBC | Language models (Claude API) for our own research and editorial work: news research, scoring articles for the Trust Signal newsletter, and enrichment in our fairness engine; Claude as a tool in our software development | Public articles and research material, our own code and documents; no platform feature sends customer content to Anthropic | United States | API: Anthropic's Commercial Terms with its Data Processing Addendum; under these terms Anthropic may not train models on our content |