ChurnSafe

Sub-processors

Last updated: March 2026

ChurnSafe uses the following sub-processors to deliver its services. We will update this page and notify customers before engaging any new sub-processors.

Current Sub-processors

Sub-processorPurposeLocation
CloudflareInfrastructure, CDN, edge computing, D1 database, Workers compute, R2 storage, KV storeGlobal (edge network)
StripePayment processing, subscription managementUnited States
ResendTransactional and intervention email deliveryUnited States
SentryError monitoring and performance tracking (PII scrubbed before transmission)United States
OpenAILLM processing for intervention email generation (when configured)United States

Data Processing Details

Cloudflare

Cloudflare provides the core infrastructure for ChurnSafe. All application data, including event data, risk scores, and user information, is stored in Cloudflare D1 (SQLite database) and processed by Cloudflare Workers. Data is encrypted in transit and at rest.

Stripe

Stripe processes all payment transactions. ChurnSafe stores Stripe customer and subscription IDs but does not store credit card numbers or sensitive payment details directly.

Resend

Resend delivers transactional emails (account verification, password reset) and intervention emails generated by the churn prevention system. Email content is transmitted securely and not retained by Resend beyond delivery.

Sentry

Sentry receives error reports for monitoring and debugging. All personally identifiable information (PII) is scrubbed before transmission using a beforeSend filter that removes email addresses, names, user IDs, and Stripe customer IDs.

OpenAI

When configured by the account administrator, OpenAI’s API is used to generate personalized intervention emails. The data sent includes anonymized behavioral context and the founder’s voice profile. No raw PII is sent to OpenAI.

Changes to Sub-processors

We will provide at least 30 days’ notice before engaging a new sub-processor. Notifications will be sent to the email address associated with your ChurnSafe account.

If you object to a new sub-processor, you may terminate your account within 30 days of notification.

Contact

For questions about our sub-processors, contact us at dpa@churnsafe.co.