01Overview
PristineSend uses the third-party subprocessors listed below to provide our Service. When we add or replace a subprocessor, we notify workspace owners by email at least 14 days in advance so you have time to object, as set out in our Data Processing Addendum. To object to a change, contact us at legal@pristinesend.com.
02Current Subprocessors
| Subprocessor | Purpose | Data processed | Data location |
|---|---|---|---|
| Bird (SparkPost) | Email delivery | Recipient email addresses and names, message content, sending metadata | United States |
| Amazon Web Services (incl. Amazon SES) | Cloud infrastructure & email delivery | Email content, recipient addresses, sending metadata | United States |
| Vercel | Application hosting & delivery | Application usage and log data, IP addresses | United States |
| Supabase | Database & file storage | Account data, contacts, campaign data | United States (us-west-2, Oregon) |
| Cloudflare | CDN, DNS & network security | IP addresses, request metadata | Global edge network (no data-localization region configured) |
| Clerk | Authentication & user management | Account-owner credentials and profile data (not recipient data) | United States |
| Inngest | Background job & workflow processing | Job metadata (record identifiers only — no recipient addresses or message content) | United States |
| ZeroBounce | Email list verification | Contact email addresses | United States |
| Anthropic | AI features (deliverability scoring & content-safety scanning) | Email subject, preview text and body content; to check that an email comes from who it says, the sender's name and address and the account's organisation name, verified domains, website and where the email's pictures came from; applicant name and email for signup review | United States |
| TypeSafe | Content-safety scanning (a second AI model, compared against Anthropic's) and signup review | Email subject, preview text and body content; to check that an email comes from who it says, the sender's name and address and the account's organisation name, verified domains, website and where the email's pictures came from; for signup review, the applicant's sending domain, signup page address and text, described use case and expected list size and volume (not their name or email). Not used to train AI models. No zero-retention commitment: kept as long as necessary to provide the service, and usage data derived from it may be kept longer | United States |
| Stripe | Payment processing | Account-owner billing and payment details (collected directly by Stripe) | United States |
| BetterStack | Uptime & status monitoring | System and operational metrics | European Union |