Sub-processors
Last updated: 21 October 2026
These are the companies that process personal data on SubSaver's behalf. Each one is bound by a data processing agreement, may only use the data to provide its service to us, and is covered by the transfer safeguards described in our privacy policy.
Service providers (processors)
| Provider | What for | Personal data | Location |
|---|---|---|---|
| Vercel | Application hosting (servers in Frankfurt, EU) | All account data stored by SubSaver (encrypted in transit and at rest; inbox access tokens and app passwords additionally encrypted by SubSaver) | Frankfurt, EU; company based in the USA |
| Neon | Database (Frankfurt, EU) | All account data stored by SubSaver (encrypted in transit and at rest; inbox access tokens and app passwords additionally encrypted by SubSaver) | Frankfurt, EU; company based in the USA |
| Vercel Speed Insights | Measuring page speed (Core Web Vitals), without cookies | Page address, browser, operating system, device type, connection speed, approximate country | USA |
| Google Analytics (Google Ireland Limited) | Counting visits and seeing which pages help people sign up. Website only, and only if you accept analytics cookies. | Pages viewed, how you arrived (referrer), browser, device type, approximate location, a random visitor ID in a cookie. IP addresses aren't stored. Never anything from your SubSaver account or emails. | Ireland; may be processed in the USA (Google LLC, EU-U.S. Data Privacy Framework) |
| Resend | Sending reminders, summaries and account emails | Email address, email subject and content (for example a reminder's service, price and date) | USA |
| Stripe | Payments, invoices and the billing portal. Paid plans only. | Email address, name and billing address you give Stripe, payment details (entered at Stripe, never seen by SubSaver), plan and payment history | Ireland (Stripe Payments Europe) and the USA |
Services you choose to use with SubSaver
These companies aren't our processors: they run services you use with SubSaver and handle data under their own privacy policies. They're listed so you know where data goes.
| Company | What for | Data involved | When |
|---|---|---|---|
| Sign in with Google; Gmail read-only access (Gmail API); Firebase Cloud Messaging for Android app notifications; push for Chrome | Sign-in request and tokens; requests for your billing emails; Android notifications' title and text with the device token; Chrome notifications end-to-end encrypted, with the browser's push address | Only if you sign in with Google, connect Gmail or turn on push | |
| Microsoft | Sign in with Microsoft; Outlook read-only access (Microsoft Graph); push for Edge on Windows | Sign-in request and tokens; requests for your billing emails; Edge notifications end-to-end encrypted, with the browser's push address | Only if you sign in with Microsoft, connect Outlook or turn on push |
| Yahoo | Yahoo Mail read-only access (IMAP with an app password you create) | Requests for your billing emails | Only if you connect Yahoo Mail |
| Apple | Apple Push Notification service for the iPhone app and Safari; iCloud Mail read-only access (IMAP with an app-specific password you create) | iPhone notifications' title and text with the device token; Safari notifications end-to-end encrypted, with the browser's push address; requests for your billing emails if you connect iCloud Mail | Only if you turn on push or connect iCloud Mail |
| Mozilla | Push for Firefox | End-to-end encrypted notifications (Mozilla can't read them), with the browser's push address | Only if you turn on push in Firefox |
Changes
We update this page before a new processor starts handling personal data. If a change matters to you, we'll also email you in advance. Questions: support@subsaver.help.