Everyone who touches your data
A short list, because the product is small on purpose. Each entry says what the company does for us and what it can actually see.
Last updated 27 August 2026
Draft. These documents describe how pinguHQ actually works today, and they have not yet been reviewed by a lawyer. If something here matters to a decision you are making, ask us before you rely on it: hello@pinguhq.com.
In short
- 7 companies, each named below with what it can see.
- Where your alerts go — Slack, Telegram, a webhook — is your choice, so those are not subprocessors and are not on this list.
- We update this page before a new one starts, and will email you first if you ask us to.
The list
Each of these is bound by contract to use customer data only to provide its service to us. Where one of them processes personal data outside the UK or the EEA, that transfer relies on the standard contractual clauses or an equivalent mechanism in that provider’s own terms.
Hosts and serves the dashboard, status pages and this website
What it can see
IP address and user agent in request logs; anything in a URL you visit
Postgres database and authentication
What it can see
Your name, email address and avatar; everything you create in the product; status page subscriber email addresses
Stores check history — the response times and status codes behind your graphs
What it can see
The addresses you asked us to check and the result of each check. No account data
Sends email: alerts, status page updates and sign-in links
What it can see
Recipient email address and the contents of the message
Merchant of record — takes payment and handles tax
What it can see
Billing name, email, country and card details. Card details are entered on their checkout and never reach us
Issues certificates and routes traffic for status pages on your own domain
What it can see
The domain name you connect, and visitor IP addresses for requests to it
TO CONFIRM — server host
One Linux server running Redis and the check, incident and notification workers
What it can see
Monitor configuration and queued alerts, in transit. Nothing durable is stored there
Deliberately not on this list
Slack, Telegram and your webhook endpoints. When you connect one, we deliver alerts to a destination you chose, in a system we neither selected nor control. They are recipients you picked rather than processors we engaged, and padding this list with them would blur a distinction that matters when you are working out who is responsible for what.
Google, when you sign in with it. Google is your identity provider, not our processor: data flows from them to us, not the other way round. We receive your name, email address and profile picture, and nothing else.
Analytics and advertising vendors. There are none. The marketing site loads no analytics script and sets no cookies at all.
When this list changes
We update this page before a new subprocessor starts handling customer data, not after. The date at the top of the page moves when it does.
Email hello@pinguhq.com and we will add you to the list of people told by email before a change takes effect. If you object to a new one on reasonable data protection grounds, tell us: if we cannot resolve it, you can cancel and we will refund the unused part of your period.
Data processing agreement
If you need a signed DPA, including the standard contractual clauses, ask at hello@pinguhq.com and we will send one over.
There is no click-through DPA on this site yet, and that is deliberate rather than an oversight. A data processing agreement is a contract, not marketing copy; publishing one that no lawyer has read would be worse than asking you to email us for it.