This page lists the third parties (sub-processors) that process customer data on Hamlet’s behalf when you use our platform.
We maintain this list under version control and update it when sub-processors are added, replaced, or removed. To subscribe to change notifications, email security@hamletco.space with the subject line “Sub-processor notifications” and the email address you’d like notified.
For full context on how Hamlet handles personal information, see our Privacy Policy and Security & Data Practices page.
Change notification commitment
Hamlet provides 30 days’ prior written notice before adding or replacing a sub-processor that handles customer data. Notifications are delivered by email to the customer’s designated security contact (and, where applicable, the subscribers list above).
Right to object. Customers may object to a proposed sub-processor change in writing within the 30-day notice period. If Hamlet and the customer cannot resolve the objection through reasonable discussion, the customer may terminate the affected service without penalty for the affected scope.
Emergency replacement. Where a sub-processor must be replaced urgently for security or continuity reasons, Hamlet will provide notice as soon as practicable, with an explanation of the urgency and the rationale.
Current sub-processors
Sub-processor | Purpose | Region | Data flowing |
|---|---|---|---|
Google Cloud | Primary hosting, data storage, file storage, asynchronous workloads | australia-southeast1 (Sydney) | All customer data at rest. Encrypted backups in GCP asia multi-region by default; AU-only available on request. |
WorldPay (IntegraPay) | Card payment capture and processing (primary AU gateway) | Australia | Cardholder data captured by gateway-hosted forms. Hamlet receives tokens only. |
Stripe | Alternative card payment gateway (platform default for non-WorldPay customers) | United States | As above. Hamlet receives tokens only. |
Xero | Accounting integration (invoice and contact sync) | Australia / New Zealand | Invoice line items, customer contact records, payment confirmations. |
SendGrid (Twilio SendGrid) | Transactional email delivery | United States | Recipient email address. Message body for system notifications. |
Twilio | SMS delivery (where enabled) | United States / Australia | Recipient phone number. Message body. |
PostHog | Product analytics on member portal and admin dashboard | United States (default); EU region configurable | User identification, role, tenant identifier, event data. No payment data. No booking content. No message content. |
Google Tag Manager / Google Analytics | Marketing analytics on member portal (per-tenant opt-in) | United States | Visitor-level interaction events. |
Meta (Facebook) Pixel | Marketing analytics on member portal (per-tenant opt-in) | United States | Visitor-level interaction events. No payment data. No booking content. |
Slack | Internal error and integration-failure notifications | United States | Server-side error metadata. No customer personal information in alert payloads. |
OpenAI / Anthropic | Administrator AI assistant (opt-in feature) | United States | Prompts and responses initiated by administrator users. |
Expo / EAS | Mobile application build and over-the-air update delivery | United States | Mobile application bundle metadata. No customer data. |
Apple (Sign in with Apple) | Mobile OAuth identity provider | United States | Authentication tokens. No payment data. |
What we don’t use
For transparency, Hamlet does not currently contract with the following common SaaS sub-processors:
- Sentry
- Datadog
- New Relic
- PagerDuty
- Opsgenie
- Mixpanel
- Segment
- Auth0
- Okta
If this changes, the list above will be updated and customers will be notified per the change-notification commitment.
Cross-border disclosure
Primary customer data at rest remains in Australia (Google Cloud australia-southeast1).
As shown above, some sub-processors are located outside Australia (primarily the United States, with some EU/NZ/APAC processing). Before disclosing personal information to an overseas sub-processor, Hamlet takes reasonable steps to ensure the recipient handles that information consistently with the Australian Privacy Principles, as required by APP 8 — including through appropriate contractual arrangements.
For more detail on cross-border disclosure, see Section 9 of our Privacy Policy.
Contact
Questions about sub-processors, change notifications, or objections:
For broader privacy queries:
Document version
Version | Date | Notes |
|---|---|---|
1.0 | 11 May 2026 | Initial public release. |