Legal
Sub-processors
The third parties that process personal data on PubTrust's behalf, what each one does, and what it sees.
Current sub-processors
| Sub-processor | Purpose | Data |
|---|---|---|
| Cloudflare | Edge network: delivery of the tag and policy bundles, receipt of beacons, IP truncation, queueing | Beacon data in transit, including the connecting IP address before truncation; Site configuration |
| Railway | Application hosting, Postgres database and Redis | Stored event data (truncated IP addresses by default), account data, audit log |
| Stripe | Subscriptions, payments and usage metering | Billing contacts, plan, one aggregated usage figure per organisation per day; card details are held by Stripe and never reach PubTrust |
| plinth (plinth.tools) | Transactional email: account emails, usage alerts, report digests | Recipient names and email addresses, email content |
Stripe never receives raw events: a daily job sends one aggregated usage figure per organisation. An EU region is available for the Railway-hosted application platform and database.
How will I hear about changes?
We notify customers before adding or replacing a sub-processor, so you can object under the Data Processing Agreement. To be notified, write to privacy@pubtrust.cc.