Subprocessors

Overview

This page lists subprocessors that may process personal information for EmailGuard based on the current codebase, configuration, and documented deployment options. Actual subprocessors may vary by deployment, enabled modules, customer configuration, and infrastructure choices.

This is example subprocessor documentation for an enterprise SaaS deployment. Update it before production launch and whenever providers, regions, purposes, or data categories change.

Subprocessor commitments

Where we engage subprocessors, we expect them to provide services under agreements that include confidentiality, security, and data protection obligations appropriate to their role. We remain responsible for our obligations to customers under applicable agreements.

Enterprise customers may request notice of material subprocessor changes through their signed agreement or Data Processing Addendum.

Current and likely subprocessors

Provider	Purpose	Data involved	Notes
Stripe	Subscription billing, checkout, customer portal, invoices, payment webhooks	Billing identifiers, customer metadata, plan details, subscription status, invoice/payment metadata	Used when the billing module is enabled. Full payment card data should be handled by Stripe-hosted fields or Stripe surfaces.
Resend	Transactional email	Email address, message metadata, message contents for verification, password reset, invitations, notifications, and support workflows	Used when email delivery is configured.
Sentry	Error monitoring and performance diagnostics	Error events, stack traces, request metadata, device/browser details, release identifiers, user identifiers if configured	Used by frontend, backend, and mobile when DSNs are configured.
Google	OAuth sign-in and Android app distribution	OAuth identifiers, email/profile data during sign-in; app listing and distribution metadata for Google Play	OAuth is used only when enabled. Google Play links are used when mobile distribution is enabled.
GitHub	OAuth sign-in, source hosting, CI/CD, repository automation	OAuth identifiers and profile data during sign-in; repository metadata, CI logs, workflow artifacts	OAuth is used only when enabled. GitHub Actions may process code, logs, test output, and artifacts.
Hosting provider	Frontend, API, worker, and static asset hosting	Request metadata, logs, deployment metadata, application traffic, environment metadata	The template documents Dokploy, Docker-based VPS hosting, and Railway-compatible frontend hosting.
Domain, DNS, CDN, or WAF provider	DNS resolution, TLS, caching, network security, DDoS mitigation	DNS records, request metadata, IP addresses, security events	Add the actual provider used by the deployment.

Deployment-dependent providers

Forks of this template may add providers such as analytics, customer support, CRM, data warehouses, object storage, SMS delivery, search, AI services, CDN/WAF services, or managed infrastructure. Update this page before enabling additional providers in production.

Data location

Provider regions depend on the deployment and selected service plans. Enterprise customers with data residency requirements should confirm the chosen infrastructure regions and provider terms before production use.

Most of our Servers are located in Hetzner US (Ashburn, Virgnia).

Change notices

We may update this list when subprocessors are added, removed, or replaced. For enterprise customers with written notice rights, notice procedures should be handled under the applicable agreement or DPA.

Objections

If a customer has a reasonable data protection objection to a new subprocessor, the customer should contact [email protected] within the notice period stated in the applicable agreement. The parties should work in good faith to address the objection.

Contact

Questions about subprocessors can be sent to [email protected].