Last updated: October 20, 2026
Subprocessors
These are the companies PennyPost uses to process personal data. The first table lists the sub-processors that handle our customers' users' data, which our Data Processing Addendum calls Customer Personal Data. That table is Annex III of the standard contractual clauses in the DPA.
Sub-processors for your users' data
| Provider | What it does for PennyPost | Personal data it handles | Location |
|---|---|---|---|
| Amazon Web Services, Inc. (Amazon SES) | Sends email, and reports deliveries, bounces and complaints back to us | Recipient email addresses and names, email content, sending domains, delivery reports | United States: US East (N. Virginia) |
| MongoDB, Inc. (MongoDB Atlas) | Our database | Everything PennyPost stores: contacts, page views, key actions, workflow progress, email records | United States: on Amazon Web Services, US East (N. Virginia) |
| Vercel Inc. | Hosts the app, the API and the snippet's endpoint, keeps server logs, and stores images uploaded to the email editor | Every request to PennyPost, with its IP address and what it carries, such as a user's email address and page path from the snippet | See provider |
| Upstash, Inc. | Runs background jobs (QStash) and rate-limit counters (Redis) | Internal IDs of emails and workflow runs. Short-lived counter keys made from IP addresses, email addresses, and app or API key IDs | See provider |
| Anthropic, PBC | Writes AI drafts and suggests an app's key pages | Your website's text and your answers. For key page suggestions, your app's most-opened page paths from the last 30 days with their view counts, with IDs in the paths replaced. No email addresses, names or other data about a single person | See provider |
Providers for your PennyPost account only
These handle data about you as a PennyPost customer, not about your users. The providers above handle your account data too.
| Provider | What it does for PennyPost | Personal data it handles |
|---|---|---|
| Polar (polar.sh) | Checkout, billing and sales tax, as our merchant of record | The name, email address, billing address and payment details you enter at checkout |
| Google LLC | "Continue with Google" sign-in | Your name, email address and Google account ID |
Loaded by your browser
When you're logged in, your browser loads small images straight from these services. PennyPost's servers don't send them anything.
| Service | What it shows | What it receives |
|---|---|---|
| Gravatar (Automattic Inc.) | Contact pictures | A SHA-256 hash of the email address of each contact on screen |
| Google's favicon service | Website icons | Domain names |
Providers you bring
- Resend. If you connect your own Resend account, PennyPost sends your emails through it with your API key. Resend then works for you under your own agreement with Resend, so it's your processor and isn't on our list.
- PostHog. If you connect PostHog with one click, PennyPost runs read-only queries on the one project you picked, for new people, their page views and the two events you chose. With a webhook instead, your PostHog project sends events to PennyPost and PennyPost can't read your PostHog account. Either way PostHog is your processor, and PennyPost doesn't send PostHog any data.
- Segment. If you connect Segment, your Segment workspace sends events to PennyPost. Segment is your processor. PennyPost doesn't send Segment any data and can't read your Segment workspace.
Changes to this list
Before we add or replace a sub-processor that handles your users' data, we'll update this page and email your account's address at least 14 days ahead. You can object by email to hello@usepennypost.com within those 14 days. Section 7 of our Data Processing Addendum explains what happens next.