Legal
Sub-processors
Effective 20 September 2026 · Last updated 20 September 2026
We give customers at least 30 days' notice before a new sub-processor handles Customer Data. Last updated 20 September 2026.
| Sub-processor | Purpose | Data | Location |
|---|---|---|---|
| Google Cloud | Platform hosting and databases | All Customer Data | Australia (AU and NZ customers); United Kingdom (UK customers) |
| Stripe | Payment gateway | Payment and billing data for customers using Stripe | Global; card data held by Stripe, not Hamlet |
| Worldpay | Payment gateway | Payment and billing data for customers using Worldpay | Global; card data held by Worldpay, not Hamlet |
| SendGrid (Twilio) | Transactional email | Names, email addresses, message content | United States |
| Xero | Accounting integration | Invoice, payment and contact data for customers who connect Xero | Global |
| Calendar integration | Booking details for customers who connect Google Calendar | Global | |
| Slack | Shared support channels | Support conversations with customers who opt in | United States |
| Supademo | Guides and training content | Usage of guides; no Customer Data | United States |
| PostHog | Error and performance monitoring | Technical logs which may include identifiers | United States |
| Atlassian (Jira) | Support tickets | Contact details and ticket content | Global; data residency set per Atlassian site |
This page lists the sub-processors that handle Customer Data within the Hamlet platform. Providers that handle personal information for Hamlet's own business, rather than Customer Data, are listed in the Privacy Policy.
Sub-processors are engaged under clause 22.3 of the Terms of Service, and personal data transfers are governed by the Data Processing Addendum.