Legal

Where your data is stored, and what to tell your clients

A guide for accounting, tax and legal practices on where Cradle stores and processes client information, how long it's kept, and how to meet your disclosure obligations under the TASA Code, APES 110, the Privacy Acts and the lawyers' conduct rules.

If you're a registered tax practitioner, an accountant, or a lawyer, your professional rules say you can't hand client information to a third party without telling the client, and usually without their permission. A cloud phone system that records calls, transcribes them and files notes into your practice software is a third party holding client information. This page gives you what you need to disclose it properly: where each kind of data is held, where it's processed, how long we keep it, and wording you can drop into an engagement letter or privacy policy.

The short version: Cradle processes your data in the United States. Call recordings, transcripts, AI notes and message attachments for Australian and New Zealand firms are stored in Sydney, and for UK and European firms in London. They're still produced in the United States first. If a client asks "does my information leave Australia (or New Zealand)?", the honest answer is yes, and the country to name is the United States.

Where each kind of data lives

A useful way to think about it is an envelope. What's written on the outside (who called whom, when, for how long, the contact's name and number) is addressing information: it has to be handled properly, but it's not the confidential part. What's inside the envelope (the recording, the transcript, the AI summary and notes, the message text and any attachments) is the client conversation itself. That's where the stronger protections, the regional storage and the retention controls apply, and it's what your clients and regulators care about when they ask where their information goes.

Your organisation's Home Region is set by the country of your business address in Cradle: Sydney (Google Cloud australia-southeast1) for Australia and New Zealand, London (europe-west2) for the United Kingdom, the European Union, Iceland, Liechtenstein, Norway, Switzerland and the Crown Dependencies, and the United States for everywhere else. If no country is recorded for your organisation, it's Sydney until one is.

Data Stored at rest Processed (created or handled)
Inside the envelope
Call recordings and voicemail audio Your Home Region. Each recording is copied there when the call ends and our telephony provider's copy (Twilio, in a subaccount that belongs only to your organisation) is then deleted. Recordings made before 13 October 2026 were moved there and deleted from Twilio by 16 October 2026. The admin portal shows where your recordings are stored. Every recording is deleted for good when its retention period ends. United States, after the call ends. We aim to carry and mix the live audio of a call in Twilio's region closest to you (Sydney for Australia and New Zealand), so for most customers it doesn't pass through the United States during the call. A call can fail over to another region if there's a fault or we detect a faster path.
Transcripts Your Home Region United States (AssemblyAI)
AI summaries, call titles and CRM notes Your Home Region United States, and other Google Cloud regions where a request is routed for capacity (Google Vertex AI). The summary is generated from the call audio; notes and titles from the transcript.
Message attachments (SMS, MMS, WhatsApp, team messaging) Your Home Region United States (Twilio). WhatsApp messages also pass through Meta's global network.
Message text (SMS, WhatsApp, team messaging) United States (Google Cloud) United States
Outside the envelope
Call records (numbers, times, durations, outcomes), contacts, users, settings, presence history, live call state United States (Google Cloud) United States
Voice-menu recordings and greetings you upload United States (Google Cloud) United States
Voicemail notification emails (audio and transcript) Your own mailbox Sent from the United States (SendGrid)
Notes, summaries and recording links filed to your CRM or practice system Your CRM or practice system, under its own terms and locations

Our compute runs in Google Cloud's Iowa region (us-central1). Full detail for every supplier is on the sub-processor register, which is the document reviewers check a data-location claim against, so the two always agree.

What we don't claim. We don't say your data "stays in Australia", "never leaves New Zealand" or is "Australian-resident". Storing transcripts and recordings in Sydney is real and useful, but the transcript was created in the United States, the recording was processed there after the call, and your call records are there too. If a client or regulator needs data that never leaves the country (for example, My Health Records Act data, or government PROTECTED work), Cradle isn't the right tool for that work today, and we'd rather tell you than have you find out.

How long we keep it

Data Default retention Can you change it? How it's deleted
Call recordings and voicemail audio 365 days for organisations created on or after 8 October 2026. Organisations created before then keep the period they already had (usually 28 or 365 days); ask us if you're not sure what yours is. Yes, by emailing help@cradle.io from an admin account. We apply the change within 28 business days. Weekly automatic sweep deletes the audio wherever it's held; the call record stays without the recording. Admins can also delete the recordings of any call at once.
Transcripts, AI summaries, notes and titles 365 days for organisations created on or after 8 October 2026. For organisations created before then, kept until you ask us to set a period, because for many firms the transcript and summary are the record once the audio is gone. Deleting a recording doesn't delete its transcript. Yes, on request as above. Weekly automatic sweep once a period applies. Admins can delete a call's transcription and summary together at any time.
Message attachments (text, WhatsApp and team messaging) 365 days for organisations created on or after 8 October 2026. For organisations created before then, kept until the message or conversation is deleted, or until you ask us to set a period. One period covers all three kinds of attachment. Yes, on request as above. Weekly automatic sweep once a period applies, which also deletes any copy our telephony provider holds. Deleting a message or conversation removes its attachments at once.
Message text (SMS, WhatsApp, team messaging) Life of your account Admins can delete an SMS or WhatsApp message or a whole conversation at any time; in team messaging, the person who sent a message can delete it. See Deleting messages and conversations. Deleted text is replaced with a "Message deleted" marker.
Call records, contacts, users and settings Life of your account Contacts you delete are purged after 30 days. Contacts and users are deleted or returned when your account closes. Call records (numbers, times, durations, charges) are anonymised so they no longer identify anyone, and kept for billing and audit.
Presence history (each person's status, such as available, busy, away or offline, and when it changed) 28 days No Deleted automatically after 28 days, and when your account closes. With Microsoft Teams presence sync on, a status can reflect the person's Teams or calendar status.
Access logs for the Cradle API and command-line tools (which user or key was used, when, from which IP address and what was requested) 12 months No Deleted automatically after 12 months, including after your account closes. We keep them only to detect and investigate security incidents and misuse.
Everything, when you leave Exported or deleted at your election within one month of termination; deleted within 30 days after that; backups within 90 days. The one-month export window doesn't extend by itself; we can agree one extension at your cost, and deletion follows at the end of it. Clause 18.7 of the Terms of Use. We confirm deletion in writing on request.

Three things to know about retention:

  • Deletion stops at Cradle. Notes, summaries and transcripts we've filed into your practice system or CRM (FYI, XPM, Karbon, HubSpot) stay there under that system's retention; we don't delete from your systems. We never copy audio into them, only a link back to Cradle, so once a recording is deleted here the link stops playing but the written record in your system remains.
  • Deleted means gone. We hold one copy of each recording, transcript, AI note and attachment, and no archive or backup of them. Once the weekly sweep has run, or someone in your organisation deletes an item, it's removed from Cradle and we don't restore it, no matter how quickly you ask. Our deletion process then takes a short time to finish: the sweep runs within 7 days of a retention period ending, and our storage provider takes up to 7 more days to destroy a removed item. The Terms call this the deletion window, it's never more than 14 days, and after it nobody can get the item back. Set retention to match your own record-keeping obligations (for example, the ATO's five-year rule for tax records, or the Law Society's file-retention guidance), and export anything you need before it expires.
  • You can pause deletion for a legal matter, but it takes more than sending an email. If you're facing litigation, a regulatory inquiry or a professional-conduct matter, an admin can email legal@cradle.io asking us to suspend automatic deletion of specified calls, messages or a date range until it's resolved. The hold isn't in place until we've written back to confirm we received the request and have acted on it, so chase us if you haven't heard within one business day, and don't assume anything is held until you have that confirmation. We put the hold in place by extending your organisation's retention period, which you'll see change in the admin portal. Two things to plan for: we charge for the extra storage the hold causes, per recorded minute, at the rate in your Proposal or at a rate we'll quote when we confirm the hold (storage is quoted per organisation, so ask), and the hold doesn't stop your own people using the delete controls, so you'll need to manage that internally, for example by restricting who can delete while the matter is open. Clause 10.14 of the Terms of Use sets out the detail.

Our suppliers' own copies are limited to a processing window of at most 24 hours: Twilio's copy of a message attachment is deleted within the Processing Window once ours is stored (and so is its copy of each recording); AssemblyAI deletes call audio after transcribing it, and we delete the transcript from AssemblyAI as soon as our copy is stored; Google holds its working copies of AI requests and outputs for no more than 24 hours. An AI supplier may also keep a copy for a limited period solely for abuse and safety monitoring, where its terms require it; that copy is restricted to its safety review, isn't used for training, and the period is on the sub-processor register. Twilio keeps call and message logs (numbers, times, message text) under its own retention schedule.

What the rules say, and what to do

The obligations below all come down to the same three steps: tell the client where their information goes, get their permission (an engagement letter with a positive acceptance is the normal way), and keep evidence that you checked the provider out. This page and the documents linked at the end are the evidence.

Registered tax and BAS agents in Australia (TASA Code of Professional Conduct)

Code item 6 in section 30-10 of the Tax Agent Services Act 2009 says you must not disclose information relating to a client's affairs to a third party without the client's permission or a legal duty. The Tax Practitioners Board's guidance treats a cloud provider hosting client data as a third party, and hosting outside Australia as offshoring. The relevant guidance statements are:

  • TPB(GS) 31/2018 Outsourcing and offshoring of tax services (formerly TPB(PN) 2/2018; renamed 30 April 2026). Obtain permission from each client before divulging client information to a third party, "by way of a signed letter of engagement, signed consent, or other communication with the client". Tell the client to whom and where the disclosure will be made if known. A general consent can be acceptable, but it should involve a positive step from the client, such as an opt-in. Don't imply all your work is done in Australia if it isn't.
  • TPB(GS) 30/2017 Cloud computing (formerly TPB(PN) 1/2017). Before using a cloud service, consider whether information is held offshore and the consequences, how it's stored and transferred, backups, the security controls each side is responsible for, what happens when the arrangement ends, and whether the provider can change terms unilaterally.
  • TPB(GS) 26/2014 Confidentiality of client information and TPB(GS) 34/2019 Letters of engagement cover what "permission" and a good engagement letter look like.

The Tax Agent Services (Code of Professional Conduct) Determination 2024 adds an obligation to keep clients informed of matters that could significantly influence their decision to engage you (section 45). Whether an overseas-hosted phone system is such a matter is your judgement; disclosing it in the engagement letter covers both bases.

What to do: name Cradle (or "our phone and call-recording provider") and the United States in your engagement letter, with the paragraph below; keep this page, the DPA and the sub-processor register in your outsourcing file; and don't state in marketing that all client work stays onshore.

Members of CA ANZ, CPA Australia and IPA (APES 110)

Section 114 of APES 110 Code of Ethics for Professional Accountants requires you to keep client information confidential and not disclose it without proper and specific authority. APES GN 30 Outsourced Services sets out the due diligence expected when you use a third-party provider. The TPB guidance above points to both. The same engagement-letter paragraph does the job.

Privacy Act 1988 (Cth): APP 8 and your privacy policy

If your firm is an APP entity (annual turnover over $3 million, or you've opted in), APP 8.1 requires you to take reasonable steps, before disclosing personal information to an overseas recipient, to ensure the recipient doesn't breach the APPs. In practice that's a contract binding the recipient. Clause 12.3 of our DPA does exactly that: Cradle agrees to handle personal information in accordance with the APPs and to be bound by them, so you can rely on the APP 8.1 route rather than the APP 8.2(b) consent route (which would require you to tell clients they may have no recourse). APP 1.4 also requires your privacy policy to say whether you're likely to disclose personal information overseas and, if practicable, which countries. Name the United States.

Even if your firm is under the threshold, anyone holding a record that links a tax file number to a person is a "TFN recipient" under the Privacy (Tax File Number) Rule 2015 and is covered by the Notifiable Data Breaches scheme for TFN information. A client reading their TFN on a recorded call puts it in the recording and the transcript. Please don't ask clients to read out TFNs on the phone; where it happens, our systems restrict access and delete on your retention schedule (clause 10.15 of the Terms).

Australian legal practitioners

Rule 9 of the Australian Solicitors' Conduct Rules (confidentiality) permits disclosure of client information only with the client's authority or as permitted by law, and state law societies publish cloud-computing guidance that mirrors the TPB's: know where data is, check the contract, plan the exit. Your costs agreement or engagement terms should authorise the use of cloud and telephony providers located overseas, naming the United States.

New Zealand accountants and tax agents

The Privacy Act 2020 works differently from the Australian Act on this point. Under section 11, information you send to a provider that holds or processes it only on your behalf is treated as still held by you, so sending it to Cradle isn't a "disclosure" under IPP 12 (the overseas-disclosure principle). The Privacy Commissioner's guidance confirms that using an offshore cloud provider purely for storage or processing on your behalf falls in this category. Clause 12.4 of our DPA records that Cradle holds your information as your agent under section 11, and that Cradle is itself an agency subject to the Act.

What still applies to you: IPP 3 (tell people, when you collect their information, who will hold it and that it may be stored overseas), IPP 5 (reasonable security safeguards, which the DPA and our security page evidence), and the CA ANZ Code of Ethics confidentiality requirements for New Zealand members, which, like APES 110, expect client authority before information goes to a third party. Say it in your engagement letter and privacy statement.

New Zealand lawyers

Chapter 8 of the Lawyers and Conveyancers Act (Lawyers: Conduct and Client Care) Rules 2008 requires you to hold client information in strict confidence, and the New Zealand Law Society's Cloud Computing Guidelines for Lawyers (29 May 2024) say to identify where data is stored and which country's law applies, seek contractual protection for confidentiality, understand how government agencies could access it, make sure you can get data out in a usable form when you leave, and confirm deletion. Clients should be told that their information will be held by a third-party provider and may be stored overseas, and the guidelines note that under IPP 3 you should identify who will hold it. Your terms of engagement should carry the paragraph below.

United Kingdom and European firms

Under the UK GDPR you're the controller and Cradle is your processor. Our DPA contains the Article 28(3) terms. Because Cradle is established in New Zealand, which has UK adequacy regulations, your transfer to us needs no International Data Transfer Agreement or transfer risk assessment. Onward transfers to our US suppliers are covered by our own contracts with them. Your privacy notice should say that client data is processed by suppliers in New Zealand and the United States.

Firms in the European Union, Iceland, Liechtenstein, Norway and Switzerland are in the same position under the GDPR (and the Swiss Federal Act on Data Protection): New Zealand has an adequacy decision from the European Commission, and so does the United Kingdom, where your transcripts, AI notes, attachments and recordings are stored. Your privacy notice should name the United Kingdom, New Zealand and the United States.

Wording you can use

Engagement letter or terms of engagement (Australia):

We use Cradle, a cloud phone and messaging system, for calls and messages with you. Call recordings, transcripts, messages and related information may be stored and processed in the United States by Cradle Limited and its service providers, and recordings, transcripts, notes and attachments may be stored in Australia. Cradle is bound by contract to handle your information in accordance with the Australian Privacy Principles. By engaging us you consent to your information being handled in this way.

For New Zealand, replace the last two sentences with: "Cradle holds this information on our behalf, is subject to the Privacy Act 2020, and is bound by contract to protect it. By engaging us you authorise us to use these services."

For the United Kingdom: "Cradle Limited is a New Zealand company and acts as our processor under the UK GDPR; some processing takes place in the United States under contractual safeguards."

Your privacy policy (the countries sentence):

We disclose personal information to service providers that host or process it for us. Some of those providers are located overseas, including in the United States (cloud hosting, telephony, transcription and AI services provided through Cradle) [and New Zealand]. We take reasonable steps to ensure they handle personal information in accordance with the [Australian Privacy Principles / New Zealand Privacy Act 2020].

Your due-diligence file

Reviewers and auditors usually want to see that you checked the provider before you signed. Keep these together:

  1. This page (print to PDF with the date).
  2. The Terms of Use and Data Processing Agreement. Email legal@cradle.io if you need a countersigned copy of the DPA.
  3. The sub-processor register, which lists every supplier, what it processes and where.
  4. The security overview and, on request, our access control, incident response and vendor management policies.
  5. The independent assurance reports for our infrastructure suppliers (Google Cloud and Twilio hold SOC 2 and ISO 27001). These are their reports, not ours; Cradle doesn't hold a SOC 2 or ISO 27001 certification. See our security page for what we do hold.
  6. Your own engagement-letter wording and the date you started using it.

Keeping this current

We give 14 days' notice before adding a supplier or moving a category of data to a different country. The notice is the dated entry on the sub-processor register; we also email your organisation's admins, but the register is the record, so if your firm tracks vendor changes, check it. Adding a storage region closer to you doesn't need notice, but we update the register and this page when it happens. If you need the email sent to a different address, email privacy@cradle.io.

Questions about any of this: legal@cradle.io. We answer these questions every week, so ask.