Subprocessors
The companies that help us run TicketHappy and may handle Customer Data in doing so.
Last updated: November 6, 2026
How we choose them
We share Customer Data only with subprocessors that can protect it, under their written data-protection terms. Before adding one, we review its security attestations, such as a SOC 2 report or an ISO 27001 certificate, in proportion to the data it will handle. We review each one at least once a year.
Customer Data is hosted only on Google Cloud in the United States. It never goes to a vendor for advertising, and we never sell it. See the Privacy Policy for everything else about sharing.
The list
| Subprocessor | What it does for us | Data it handles | Where |
|---|---|---|---|
| Google Cloud Cloud Run, Cloud SQL, Cloud Storage |
Hosting, the database, attachment files and backups | All Customer Data | United States (us-central1) |
| Google Workspace | Sending notification e-mails; receiving tickets sent by e-mail | Names, e-mail addresses and the ticket content that travels by e-mail | United States |
| Stripe | Billing | The billing contact and payment details only; no student data | United States |
| Cloudflare | DNS, security and delivery for tickethappy.app (web traffic passes through Cloudflare’s network); receives Customers’ ticket e-mail at tickethappy.net and passes it straight to TicketHappy | Web requests and ticket e-mails, including Customer Data, in transit. Nothing is stored there apart from Cloudflare’s delivery and security logs (addresses and request details, never message or page content, kept up to 30 days) and cached copies of public files such as our stylesheets and a Customer’s public help-centre logo. | Global network |
| Anthropic, PBC Claude API |
Writes the automatic first reply on a new ticket and the help chat’s answers, for Customers that turn them on, and the staff helpers: suggested replies and draft help articles when staff ask, and suggested help articles and suggested troubleshooting steps on the tickets staff work, unless the Customer turns them off, and, for Customers that turn it on, chooses which team or staff member handles a new ticket | Subject and text of the ticket, or the messages typed into the help chat, and the Customer’s own published help articles; for routing, short descriptions of the Customer’s teams and staff, labelled by number, not name; for the staff helpers, its recent replies and staff notes with names and other personal details removed first; no attachments, no other tickets, nothing from confidential departments; not used to train models; kept only briefly for abuse detection | United States |
| Amazon Web Services, Inc. Amazon Simple Email Service |
Sends ticket e-mail from a Customer’s own address, for Customers that turn it on | The ticket e-mails it sends (recipients’ names and addresses, subject, message and attachments), held only while it delivers them; afterwards its sending records: addresses, delivery results and bounced addresses, not message content | United States |
Changes
We give Customers at least 30 days’ notice before adding a subprocessor that will handle Customer Data, and we update this page when one is added or removed.
Anthropic was added on 17 October 2026, before any Customer had signed up, so Customers agree to it when they sign up. Amazon Web Services was added on 6 November 2026, for sending ticket e-mail from a Customer’s own address, before any Customer had signed up. For any future change we give existing Customers 30 days’ notice, as Section 6 of the Privacy Policy says.