Legal

Subprocessors

Every company that touches data in the course of running SupportAndGo, what it does, which country it operates in, and what it can see. Our data sovereignty page tells you to ask a vendor this question, so here is our answer rather than an invitation to ask. Last updated 1 November 2026.

Who else handles your information

SupportAndGo runs on services provided by other companies. This page lists every one of them, what it does, which country it operates in, and what it can see. We keep it current: if a provider is added or removed, this page changes in the same release.

What it doesProviderCountryWhat it can see
Hosting, database, file storage and queues Google Cloud and Firebase Australia (Sydney) All support content: tickets, messages, attachments and the audit log
AI processing Google Cloud Vertex AI Australia (Sydney) Message content, to classify it and draft a reply for a person to approve
Sign-in identities Google (Firebase Authentication) United States Agent name, email address and sign-in method. No ticket content
Account, billing and outbound email MyAndGo (Fintech Development Pty Ltd) Australia (Sydney) Agent name and email address, and the text of replies sent to your customers
Email delivery SendGrid, and Amazon SES United States, and Australia (Sydney) Email in transit: recipient addresses, subject, body and attachments
Inbound email SendGrid United States Email in transit: sender address, subject, body and attachments
Payments Stripe United States Payment and card details. No ticket content
Website bot protection Cloudflare (Turnstile) United States Form submission metadata from this website. No ticket content and no customer data
App and browser notifications Expo, and Google and Apple push services United States Nothing from a message. Notifications are content-free by design: no subject, no message text, no customer name or address
Website analytics Google Analytics 4 United States Page paths and standard web analytics for this website. No ticket content

Not on this list, and why

Telephony is not enabled. Voicemail would be received by Twilio in the United States if a desk used a phone number, and no desk does; the code that would accept it refuses every request while the credential is absent, which it is. It goes on this list the day a desk gets a number.

Location lookup uses a database file on our own servers rather than a service, so nothing about a visitor is sent anywhere to perform it.

We do not use any AI service outside Australia. All AI processing, including personal-information detection and general classification, runs on Google Cloud in Sydney, Australia. If that service is unavailable, the AI step stops rather than sending anything offshore.