Your data, kept honest.
Relay is built in Brisbane and operates under Australian privacy law. This policy explains exactly what we collect, why we collect it, and what we do with it. We don't sell your data. We don't use call content to train external models. Read on for the detail.
Last updated 13 November 2026
1. Who we are
Relay is operated by Relay Systems Pty Ltd, an Australian proprietary company registered in Queensland. Our registered address is in Brisbane, Australia. Throughout this policy, “Relay,” “we,” and “us” mean Relay Systems Pty Ltd.
We comply with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). If you're in the EU/UK, your data is also handled in line with the GDPR's lawful-basis requirements (legitimate interest for sales and marketing; consent for product use).
2. What we collect
Demo bookings & enquiries. When you book or request a demo on our website, we collect your name, work email address, the time you picked and your time zone, and, where you give them, your office or company name, a phone number, your office address (asked only when the meeting needs one) and when suits you. When you submit your email address in a “Book a demo” field we keep it from that point, so we can follow up about your demo even if you don't finish booking. We also record the part of the site you submitted from (e.g. “hero”), the campaign tags on the link that brought you to us, your IP address, and your browser user-agent string. This is the minimum needed to arrange your demo and follow up on your request.
Sign-up & checkout. When you start a subscription, we ask which CRM and phone system you use so we can confirm Relay supports your stack before taking payment. We collect your billing details to process the subscription — card data is handled directly by our payment processor, Stripe; we store only a Stripe customer reference and your subscription status, never your full card number.
Product usage (when you become a customer). Relay is an iPhone app and a work number, your Relay line, whose calls pass through Relay’s servers. When your line records a call, the caller hears a recording notice first; on a call you place, the notice plays when you press Record. Calls in Private mode, outside your recording hours, or with numbers you have set to never record are not recorded. A recording is stored encrypted, and nothing is transcribed or sent to an AI service until you ask Relay to work on that call: to write it up, run a skill on it, ask about it, or sync it to your CRM. It is then transcribed (in a batch, not live) and the audio is deleted as soon as the transcript is stored. A recording nobody asks about is deleted after 30 days, or on the window your organisation sets. A voicemail left on your Relay line is a message somebody left for you, so it is transcribed when it arrives, and its audio is kept for you to play back until your organisation’s retention window or until you delete the call. When you ask Relay to work on a call, we process the transcript for AI extraction, generate structured fields and summaries, and run the post-call workflows you configured; a street address heard on a call may be checked against public map data to correct a misheard street or suburb. We also store your integration credentials (encrypted at rest), your team members' identities, and audit logs of who did what.
Texts on your line. Texts sent and received on your Relay number are stored so you can read and reply to them in the app. When you ask Relay to work on a call or a text thread, recent texts with that person are read as context for that work, and only then.
Your number. When Relay issues you a number, Australian law requires your name and service address to be lodged in the Integrated Public Number Database through our carrier. If you port your own number to Relay, the identity details the port requires (such as a date of birth or account number) are stored encrypted and deleted once the port completes.
Telemetry. We keep basic server logs (timings, error rates, request metadata) to keep the service fast, reliable, and secure. The console holds your session in your browser's local storage rather than a cookie; the iPhone app keeps it in the device keychain. The app also sends short call-connection diagnostics (timings and error names, never audio, numbers or names) so we can find faults.
Advertising (opt-in). On our marketing pages only, if you accept cookies in our banner, we load the Meta (Facebook) advertising pixel and the LinkedIn Insight Tag to measure our ads and reach people who've visited us. The Meta pixel records which pages you viewed and whether you requested a demo or created an account, and shares that with Meta. It never runs in the Relay app, never runs if you decline, and we don't sell your data. Our website also uses Plausible, a cookieless analytics service, on every page. Full detail — and how to opt out — is in our Cookie Policy.
3. Why we collect it
Form data is used solely to triage your request and contact you about a demo and onboarding. Product data is used to deliver the service: transcribing calls, extracting structured fields, and firing the post-call workflows you've configured. Telemetry is used to keep the service fast and reliable.
We will not use any of this data to train external AI models, to sell to third parties, or to target you with unrelated marketing.
4. Who we share it with (and why)
Sub-processors. We share only what's necessary with these vendors, each contractually bound to handle your data lawfully:
- Supabase (database hosting, Sydney ap-southeast-2 region). Stores all your customer data encrypted at rest.
- Anthropic (Claude API, United States). Receives call transcripts, the texts you ask Relay to work with, and the details Relay needs to write a call up or carry out an action you asked for. Anthropic’s commercial terms bar it from training models on data sent through their API, and it deletes prompts and outputs within 30 days; only content flagged by its safety systems as a policy breach can be held longer.
- AssemblyAI (speech-to-text, United States). Receives call audio for transcription and returns the transcript to us. Each side of a call may be sent on its own, so the transcript can say who said what. Audio is deleted at AssemblyAI within 48 hours and transcripts within a day, and we have opted out of their model-improvement program.
- Crazytel (telecommunications carrier, Australia). Carries your Relay number, its calls and its texts. As the carrier it holds call records and text messages for the periods Australian telecommunications law requires.
- Vultr (server hosting, Sydney). Runs Relay's call switch, which carries call audio while a call is in progress and stores none of it.
- Apple (push notifications). Delivers the notifications the app shows you, which may name the person a call was with.
- Deepgram (speech-to-text, standby). Used only if we switch transcription back from AssemblyAI. When used, it receives call audio for transcription; audio is processed and discarded — our requests are excluded from Deepgram's model-improvement program — and transcripts are returned to us.
- Stripe (payments). Processes subscription billing. We don't store full card numbers — Stripe handles card data directly.
- Resend (transactional email). Receives the email addresses needed to send you account-related notifications.
- Calendly (demo scheduling, United States). When you book a demo on our website, receives your name, email address, time zone and the time you picked, plus your office or company name, phone number or office address if the booking includes them. It puts the booking in our calendar and emails you the invite and any reminders.
- Cloudflare (DNS). Directs traffic for our domain.
- Fly.io / Vercel (backend hosting in Sydney, and website hosting). Receive standard server logs.
- Meta (advertising measurement) and Plausible (website analytics), as described under Advertising above.
CRM and integration providers. When you connect a CRM (HubSpot, Salesforce, Pipedrive, Zoho), email (Gmail, Outlook), calendar, or one of the other tools we integrate with (Slack, DocuSign, Notion), we share the data needed for the integrations you've enabled, and only as part of an action you approved. Those providers' privacy policies govern what they do with that data on their side.
Legal obligation. We'll disclose data if we're served with a valid legal order. We'll let you know unless the order forbids it.
We will never sell your data.
5. Google user data (Gmail & Calendar)
When you connect a Google account to Relay, we request a deliberately narrow set of permissions (OAuth scopes). This section describes exactly what we access, why, and what we do with it. It governs our use of all data obtained through Google APIs.
What we access.
- Gmail — send (
gmail.send). We send follow-up emails from your own mailbox, only as a post-call workflow action you have configured and approved in Relay. This permission lets us send only: we do not read, search, list, download, or modify your existing email, and we cannot read or change any Gmail settings. - Calendar — events (
calendar.events). We create and manage calendar events that you schedule as a post-call action (for example, booking a follow-up meeting). - Calendar — read (
calendar.readonly). We list your calendars so you can choose which one to write to, and read your calendar when you ask Relay to book or check a time. We do not store the contents of your existing calendar events. - Google Drive — file (
drive.file). When you pick a document from Google Drive in Relay, we access only the files you choose. - Account identity (
openid,userinfo.email,userinfo.profile). We read the connected account's email address and display name so you can tell connected Google accounts apart when more than one is linked.
What we store and for how long. We store your Google OAuth tokens encrypted at rest, the connected account's email address, and a record of the actions Relay performed on your behalf (such as a reference to a draft or event we created). We do not copy or retain the contents of your mailbox or calendar. You can disconnect a Google account at any time in Settings → Integrations, which revokes our access and deletes the stored tokens.
What we never do. We do not sell Google user data, we do not transfer it to third parties except as needed to provide the features you enabled, we do not use it for advertising, and we do not use it to train any AI model — including our own or any external model.
Limited Use disclosure. Relay's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6. Where your data lives
Primary data is stored in Supabase's Sydney (ap-southeast-2) region, and Relay's own servers and call switch run in Sydney. Some sub-processors (Anthropic, AssemblyAI, Deepgram if used, Resend, Stripe, Calendly, Meta and Apple) process data in the United States during the request lifecycle.
7. How long we keep it
Demo-request form submissions are kept until you become a customer or for 24 months, whichever is shorter. After that we delete the row.
A call recording is kept, encrypted, only until you ask Relay to work on the call: its audio is deleted as soon as the transcript is stored, and a recording nobody asks about is deleted after 30 days, or on the window your organisation sets. The one exception is a voicemail left on your Relay line: its audio is kept so you can listen to it, and is deleted on your organisation’s retention window or when you delete the call. Transcripts, AI summaries, and notes are retained so your team can search and revisit past conversations; your organisation’s administrator can instead set an automatic deletion window (3, 30, or 90 days) in Settings, and an automated retention worker then purges transcripts, summaries, notes, verbatim quotes, and contact details past that window, keeping only a non-identifying skeleton (call outcome, labels, confidence, duration, and sync and audit logs) plus the structured values written into your CRM, which remains the system of record for your customer data. Texts on your Relay line are kept with your other records. Your account and any remaining exportable data are kept while your subscription is active and for 30 days after cancellation, then deleted. Backups of our database are kept for seven days. Call records (who called whom, when, and for how long, never the content) are kept for the two years Australian telecommunications law requires of a carriage service provider.
What you ask Relay in the app — a question about your calls or an instruction — is kept for 30 days so you can read it and its answer again. After that, the words of the request, Relay’s answer, and its working are deleted (sooner if your organisation has set a shorter window). A request that is still waiting on you is kept until you deal with it. A record that the request was made, without its words, is kept for billing.
8. Your rights
Under Australian and EU/UK privacy law you can: access the personal data we hold about you, correct it, delete it, restrict its processing, object to it, and (for demo-request data) withdraw consent at any time.
To exercise any of these rights, email privacy@userelay.com.au. We'll respond within 30 days.
9. Security
Integration credentials and OAuth tokens are encrypted at rest with AES-256-GCM using an application key held separately from the database; account passwords are hashed with scrypt; the rest of your data is encrypted at rest by our database host and backed up daily. Data in transit uses TLS 1.2+. Every query is scoped to your organisation, with row-level security enabled on the database as a second layer, and every privileged action is audit-logged.
For more on how we handle data day-to-day, see our Security page.
10. Changes to this policy
We'll post any updates here and bump the “last updated” date. Material changes that affect how your data is used will be emailed to active customers at least 30 days before they take effect.
11. Contact
Privacy concerns: privacy@userelay.com.au
General contact: see our Contact page.
If you're unhappy with how we've handled your data, you have the right to complain to the Office of the Australian Information Commissioner (oaic.gov.au).