Sub-processors and Operational Providers
The providers below support archive storage, billing, customer email, analytics and operational diagnostics. Account owners and admins are notified by email when this list changes.
| Name | Role | Data categories processed | Region | Privacy URL | Added | Removed |
|---|---|---|---|---|---|---|
| Hetzner | Application hosting and storage | WhatsApp message content (decrypted, plaintext), media, account archive data, application diagnostics and access logs | DE (Cloud application host: Nuremberg; Storage Box: Germany, specific location unverified) | https://www.hetzner.com/legal/privacy-policy | 2026-01-01 | |
| Paddle | Billing | Payment method info, billing address, subscription status | IE / US (merchant of record) | https://www.paddle.com/legal/privacy | 2026-01-01 | |
| Resend | Customer transactional email | Recipient email address, transactional email content | US | https://resend.com/privacy | 2026-01-01 | |
| Sentry | Error/performance monitoring and native operator email alerts | Sanitized diagnostic fields, exception classes, code frame locations, opaque event/trace/correlation IDs, timing; operator account and notification metadata | Event data: Frankfurt, Germany (EU); account, integration and notification metadata may be processed in the US | https://sentry.io/privacy/ | 2026-01-01 | |
| PostHog | Analytics | Page views, feature usage events (cookieless mode, no personal data or IP stored) | EU (confirmed via deploy/nginx.conf reverse-proxy config, eu.i.posthog.com / eu-assets.i.posthog.com, 2026-07-28) | https://posthog.com/privacy | 2026-01-01 | |
| Telegram | Operational on-call cloud messaging | Fixed severity/category/time, exception class, sanitized code frame locations and opaque event IDs; operator account/chat metadata and ACK replies | Actual operator/group storage region unverified; cloud service operates across jurisdictions | https://telegram.org/privacy | 2026-10-01 (disclosed) |
Operational alerts exclude customer message bodies, search terms, request bodies and arbitrary error prose. Fixed diagnostic fields, structural traceback locations and opaque identifiers can remain linkable within Stora. Telegram is the operator's cloud messaging provider; listing it here does not certify a processor contract for customer archive data.
Sentry's Frankfurt event region does not establish EU-only processing of its account, integration and notification metadata. Account-specific Sentry retention, Telegram group region and auto-delete, operator mailbox retention and a fixed age limit for hosting diagnostics are unverified. Native Sentry operator emails use its own delivery infrastructure and the operator's mailbox separately from Resend. Applicable contractual and international-transfer safeguards for operational providers remain subject to review; published provider defaults are not guaranteed account settings.
For questions about our sub-processors or to object to a new addition, contact privacy@storabackup.com.
See also: Data Processing Agreement — section 7 (Sub-processor Flow-Down) for your rights when sub-processors change.