Home › Legal › Sub-processors
Our own sub-processors
We ask other companies to publish this properly, so here is ours. It is discovered, reviewed and re-checked by exactly the same engine we sell — and it is entry number one in the public register.
Nobody here edits this list in a text editor. Our discovery runs against our own domain on the same schedule as every customer’s, a reviewer approves what it finds, and the dated history below is generated from the same ledger. If we ever let this page go stale, you should stop believing anything else on this site.
01 Who we are
subprocessor.org processes personal data on behalf of our customers when they use the service — principally the contact details of the people on their team who use it, the domains and vendor lists they ask us to analyse, and any contract they upload so we can read its notification clause.
For that processing we act as a processor, and the companies listed below are our sub-processors. For our own marketing site and sales enquiries we act as a controller; that is covered in the privacy notice.
02 The current list
Every entity below, what it does for us, where it processes, and the source we read it from — the same four columns we hold every other company to.
| Entity | Purpose | Country | Data reaching it |
|---|---|---|---|
| Postmark (Wildbit, LLC) |
Transactional email — change alerts, digests, and notices we send on a customer’s behalf | United States | Recipient name and email address, message content |
| Google LLC | Sign-in only. We use Google as an identity provider and hold no Google account data beyond your email address and name | United States | Email address, display name |
| Stripe, Inc. | Subscription billing and invoicing | United States, Ireland | Billing contact, company name, VAT number. We never see card numbers. |
| Internet Archive | Historical page captures, used to reconstruct dated change history for vendors in the register | United States | Public URLs only. No customer data is sent |
| Search provider (discovery) |
Locating a company’s published sub-processor page during discovery | United States | Public domain names only. No customer data is sent |
| Hosting provider | Application servers, database and backups | To be confirmed before publication | All service data at rest, encrypted |
Six companies. Two of them (the archive and the search provider) never receive anything about you or your customers — they only ever see public domain names. Stripe never gives us card numbers. Google only tells us who you are when you sign in.
03 What is deliberately not on this list
The point of the two-column distinction we make on every scan applies to us too. These are real third parties we use, and they are not sub-processors, because no customer data reaches them:
- Google Fonts — served on the marketing site. Covered by the privacy notice, not by a DPA.
- Analytics — we do not run third-party analytics on the application at all.
- Vendors we monitor — we read the public pages of companies in the register. They are the subject of the service, not our sub-processors, and we send them nothing.
If you disagree with any of those classifications, that is a legitimate argument to have — tell us and we will record it either way.
04 How you hear about a change
The same way we insist your vendors should tell you.
- The change is published on this page with the date we made it, immediately.
- Every customer with an active subscription is emailed directly — not asked to check a page.
- Anyone at all can subscribe to this page’s feed without an account, including people who are not customers.
- A 30-day notice period runs from the date of the email, before the new sub-processor begins processing.
Thirty days is the common market position and it is what we can genuinely honour while still being able to replace a failing supplier. It is written into our DPA rather than only stated here, so it is a contractual commitment and not a policy we can quietly change.
05 Objecting to a sub-processor
You may object on reasonable grounds within the notice period. Write to [email protected] setting out the grounds, and one of three things happens:
- We do not proceed with that sub-processor for your data, where that is technically possible.
- We propose an alternative arrangement.
- Neither is workable, in which case you may terminate the affected part of the service and we refund the unused balance. We will not hold you to a contract whose supply chain you object to.
Every objection is recorded in the ledger with its outcome, and the count is published in our transparency figures whether or not it reflects well on us.
06 Change history
Generated from the ledger. Every entry carries the date we recorded it, not the date we got round to writing it down.
| Date | Change | Entity | Record |
|---|---|---|---|
| 17 Aug 2026 | List first published | Six entities | 0f31c8ad9e42 |
Anyone can verify a row against the public ledger endpoint documented in the API reference — no account required.
Your list should look like this too.
Discovered, reviewed by a person, dated, and kept current without anyone editing a page by hand.