Sub-processors
Sub-processors
SecureChat processes as little data as possible. This page lists every third-party sub-processor that handles data on our behalf, so you can verify the data-protection commitments yourself. We notify all users via the iOS app and the status page at least 30 days in advance before adding a new sub-processor.
Current sub-processors
| Sub-processor | Purpose | Data processed | Region | Compliance |
|---|---|---|---|---|
| GitHub, Inc. github.com |
Public source-code hosting, issue tracker, public roadmap | Public commits, public issues, public discussions. No message content. | USA (primary), EU mirror available | EU-US Data Privacy Framework certified; SOC 2 Type II |
| Cloudflare, Inc. cloudflare.com |
Authoritative DNS, edge CDN for the static marketing site | DNS query logs (anonymized), HTTP access logs for static pages. No message content. | Global anycast (EU nodes available) | EU-US Data Privacy Framework certified; ISO 27001 / SOC 2 |
| Apple, Inc. apple.com |
TestFlight distribution during the public-beta phase | Installation counts, session counts, crash counts per build. Free-text feedback if you submit it. | USA (Apple operates TestFlight globally) | SOC 2 Type II; Apple Privacy Policy applies |
| Hetzner Online GmbH hetzner.com |
VPS hosting for the public relay at securechat.team |
Sealed message envelopes (24h max retention). TLS metadata. | Germany (FSN1 / NBG data centers) | ISO 27001; GDPR-compliant by jurisdiction |
What is NOT a sub-processor
For clarity, these are not sub-processors because they process no SecureChat data:
- No third-party analytics (no Google Analytics, no Plausible, no Fathom)
- No third-party error tracking (no Sentry, no Bugsnag, no Crashlytics)
- No third-party email marketing (no Mailchimp, no ConvertKit, no Sendgrid)
- No third-party payments (no Stripe, no PayPal — the app is free during beta)
- No social-login SDKs (no Sign in with Apple, no Facebook, no Google)
The relay's admin endpoints are protected by a per-deploy bearer token; no third-party identity provider is involved.
Adding a new sub-processor
If we add a new sub-processor, we will:
- Publish the change on the status page at least 30 days before it takes effect.
- Update this page with the sub-processor name, purpose, data processed, region, and compliance certifications.
- Announce it in the iOS app on next launch.
You can request a copy of the sub-processor's data-processing agreement by emailing privacy@securechat.team.
Source of truth
The full source of this page is in the project repository at sub-processors.html on GitHub. Changes are tracked via git history.