Legal
What's changing in our Terms of Use, and why
AI tools and the suppliers behind them are changing quickly. This update sets out where your data is stored, how retention and deletion work, who at Cradle can see your data, and what our AI features do, so you can meet your own privacy obligations. Here is each change and the reason for it.
We've updated the Cradle Terms of Use and the Data Processing Agreement that forms part of them. The new version was published on 18 November 2026. It applies to new customers straight away and to existing customers from 18 December 2026.
This page summarises each change that matters and the reason for it. It's a guide to help you read the Terms, not a replacement for them: the Terms themselves are what apply, and if this page and the Terms differ, the Terms govern.
Why we've made this update
The world of AI tools, and of the suppliers that process data for them, is moving very quickly. Cradle now records, transcribes and summarises calls, files notes into your practice systems, and relies on specialist suppliers to do it. Those suppliers change their products, their terms and where they operate more often than traditional phone suppliers ever did.
Our customers are accounting, tax and legal practices and other businesses with privacy and professional obligations of their own. You need to know where your clients' information goes, who can see it, how long it's kept and what an AI feature does with it. Our aim with this update is to do our best to help you meet those obligations, and to be a careful custodian of the data you trust us with.
In practice that meant three things:
- Describing what happens to your data precisely. The July terms listed eight countries where data "may" be stored. That was accurate but didn't help a firm that has to tell its clients where their information goes. The new terms set out what is stored where, and what is processed where.
- Answering the questions your reviewers ask. Vendor reviews keep asking the same things: what's the authoritative record of a call, what happens to data after retention, can deletion be paused for a legal matter, and who at Cradle can hear a recording. The terms now address each one.
- Keeping one published set of terms. Some Proposals issued since July included clauses on early termination charges and recovery costs that weren't yet in the version on our website. The new terms include those clauses, and make clear that the version on our website is the one that governs.
Because suppliers and the service will keep changing, the new terms also say how we'll tell you about changes, and what we'll do if we find the service isn't operating as the terms describe.
Changes that ask more of you, or differ from what you had before
We've put these first so they're easy to find.
Notice of supplier changes is 14 days, previously 30 (DPA clause 6.4). We used to give 30 days' notice before adding a sub-processor. It's now 14 days, and it also covers something the old clause didn't: moving a category of your data to a different country. The notice is the dated entry on our sub-processor register. We also email your admins, or an address you nominate, but the register is the record. Adding a storage region closer to you doesn't need notice. Why: AI and cloud suppliers change quickly, and sometimes the right thing for your data is to move away from a supplier promptly. The old clause also said nothing about location changes. If you object within the 14 days and we can't resolve it, you can end your agreement without an early termination charge (DPA clause 6.6).
Our staff use an AI tool with your emails and messages to us (clause 9.10). Our team uses Anthropic's Claude, under business terms, to read, search, summarise and draft replies to emails, messages and support tickets you send us, to prepare quotes, proposals and presentations (including from recordings and notes of our calls and meetings with you), and to keep our customer records. Our engineers also use it to diagnose faults, with error reports and logs from Cradle after an automated process has removed names, email addresses, phone numbers, IP addresses, account and device identifiers, anything you typed, and any call or message content. Our accounts team also uses it with our records of your account (invoices, payments and your billing contacts' details) to reconcile payments and prepare invoices and credit notes; a person approves every change, and it doesn't make payments or refunds. It isn't used to open your recordings, transcripts, AI notes, attachments or messages in your Cradle account, and it doesn't train on your information. Anthropic is a new supplier on our register. Its retention is longer than our other AI suppliers': it keeps information in our workspace until we delete it, then for up to 30 days, and can keep anything its systems flag as possible abuse for up to 2 years. It may also process that information in Europe, Asia and Australia as well as the United States. Please don't email us call recordings, transcripts, card details, tax or IRD numbers, passwords or health information: if you need us to look at a call, ask us to through Cradle. Why: AI tools help a small team answer you faster and more thoroughly. We chose a provider whose business terms rule out training on your information, and we keep it away from the content stored in Cradle.
Anonymised data can be stored anywhere (clause 10.5 and DPA clause 3.6). We've always been able to use anonymised, aggregated data derived from use of Cradle for research and product development. The terms now define "Anonymised Data" strictly: data that can't reasonably be used to identify your organisation, any other customer or any individual, even combined with other information we hold. Data with names or numbers swapped for codes doesn't count while it could still be traced back, and stays your Data with all its protections. Anonymising happens only where your Data is already stored. Once data is truly anonymous, it's no longer your Data or personal information, so the storage locations in the terms don't apply to it, and we may store and analyse it in New Zealand or elsewhere. We can also use it before it's aggregated, but we still share only aggregated statistics with anyone outside Cradle. Why: so we can study how settings such as ring groups affect answer rates across customers, and use that to set better defaults and give you better advice, without needing to keep that analysis in the same country as your call data.
Objecting to a change to these terms has a deadline (clause 2.2). If a change materially and adversely affects you, you can tell us you don't accept it and stay on the previous terms until your current term ends. That notice now needs to reach us within the 30-day notice period, before the change takes effect. Why: so that you and we both know which version applies to your account.
Negotiated terms carry over; the published version governs (clauses 2.6 and 19.3). If your Proposal expressly varies a clause, that variation continues under each updated version. A Proposal that only attaches or refers to a copy of the terms doesn't fix that copy in place, and the version on our website governs if the two differ. Why: one authoritative version is easier for everyone to rely on.
Early termination and recovery costs are in the published terms (clauses 11.8 and 16.5 to 16.9). If your Proposal has a fixed term and you want to leave early, there are two options: pay the remaining months of your minimum monthly commitment, with 20 business days to pay, or let the contract run to its original end date, keep the service and keep paying monthly as normal. The charge doesn't apply if you leave because we raised prices, changed the terms in a way you've objected to under clause 2.2, added a sub-processor you object to, or breached the agreement. Separately, if an invoice goes unpaid we can recover the reasonable costs of collecting it. Why: these terms belong in the published version where everyone can read them. Publishing them also added the run-out option, a longer payment period, and a requirement that the charge is stated in the commercial summary of your Proposal.
Australian and UK customers need to give us a tax number (clause 11.9). We supply Cradle to businesses only. Australian organisations need to give us an ABN and confirm they're registered for GST, and UK organisations need to give us a VAT number. Why: Cradle is a New Zealand company, and this supports the correct tax treatment of a service supplied to you from overseas.
Liability for a breach of confidentiality is now capped (clauses 15.3 and 15.4). Our liability for breaching confidentiality, and for breaching privacy law, now shares one cap: the lesser of NZD 100,000 and twice the Fees you paid in the 12 months before the event. Before, a breach of confidentiality had no cap. Liability for death or personal injury, fraud and wilful misconduct remains uncapped. Why: almost any data incident can be described as a breach of confidentiality, so the separate privacy cap gave no real limit. One cap for both makes our exposure clear and insurable.
UK customers: no automatic renewal for a new fixed term (clauses 2.2A and 16.10). If your business address is in the UK, your fixed term no longer renews automatically. Between 30 and 40 days before it ends, we'll email your admins with the options: renew for a further fixed term at your current price (unless we've already given notice of a price increase), or end your subscription when the term ends. If you do neither, your subscription continues month to month at 25% more than your current price or our list price, whichever is higher, and you can leave on 30 days' notice without an early termination charge. We'll also email UK customers about every change to these terms, and if a change isn't solely to your benefit, you can end your contract without an early termination charge by telling us within one month. Why: this follows Ofcom's rules for UK business customers.
Automated fraud protection can restrict calling without advance notice (clause 17.6 and the fair use policy). Our systems monitor for patterns associated with toll fraud or a compromised account, and can restrict calling, messaging or sign-in automatically. Where that happens, we contact your admins as soon as reasonably practicable and restore access once we're reasonably satisfied the activity is legitimate or the account is secured. Why: toll fraud can run up large charges (six to seven figures) very quickly, often within minutes, and overnight, so acting first protects you. This is how the service already operates; the terms now describe it.
No service level agreement unless your Proposal has one (clause 4.7). We publish live status and incident history at status.cradle.io. Standard plans don't include a service level agreement or service credits. Why: reviewers ask, and the terms should give a clear answer.
Storage during a paused deletion is charged (clause 10.14). See "Pausing deletion" below.
When you leave, uninstall (clause 18.7.6). Remove the desktop, mobile and browser-extension apps from your devices within 10 business days of leaving, and remove Cradle from your Google or Microsoft sign-in settings. Why: apps left installed after an account closes keep trying to sign in, which is a security risk worth removing for both of us.
Sensitive information (clauses 8.4 and 10.15). Please don't take card numbers, tax file numbers or IRD numbers, passwords, or health information over a recorded line or by message, and pause recording if it happens. Why: the service isn't designed or certified for that kind of information, and anything read aloud on a recorded call ends up in the recording and the transcript. The terms set out how we handle it if it turns up anyway.
Where your data is stored
The eight-country list is replaced with specific locations (clause 10.9). Transcripts, AI summaries and notes, and message attachments are stored in your organisation's "Home Region": Sydney for AU and NZ businesses, London for businesses in the UK, the EU, Iceland, Liechtenstein, Norway, Switzerland and the Crown Dependencies, and the US for everyone else. Call records, contacts, message text and account data are stored in the United States, and transcription and AI processing take place there. Why: so you can tell your own clients, accurately, where their information goes.
Call recordings are now stored in your Home Region (clause 10.9.2). Recordings and voicemails used to be stored in the United States. Since 13 October 2026, each new recording is copied to your Home Region when the call ends and the US copy deleted, and by 16 October we had moved your older recordings the same way. The admin portal shows where yours are stored. Why: recordings are among the most sensitive things we hold for you, and customers asked for them to be stored with the transcripts.
Stored in your region doesn't mean processed only in your region (clause 10.9.4). We aim to carry and mix the live audio of a call in the region closest to you, and a call may be carried through another region, including the United States, if there's a fault or a faster path. Suppliers that process your data may hold it for a "processing window" of up to 24 hours to complete the job, after which they're required to delete it. Why: we'd rather set out the limits clearly than have "stored in Sydney" read as "never leaves Australia". Please don't describe Cradle to your clients as keeping data in one country.
A guide for firms with disclosure obligations (clause 5.9). If you're a tax practitioner, accountant or lawyer, your professional obligations about telling clients where their information goes remain yours to meet. To help, we publish the information you need, and there's a new guide with suggested engagement-letter wording: Where your data is stored, and what to tell your clients. It's general information, not legal advice.
Retention, deletion and access
Deletion is permanent (clause 10.13). We hold a single copy of each recording, transcript, AI note and attachment, and no backup of them. Data deleted under your retention settings, by your team, or at the end of your contract is permanently destroyed, and we don't restore it. Our deletion process takes up to 14 days to complete, which the terms call the deletion window. Why: firms asked whether "deleted" means deleted. Because it does, please set retention to match your own record-keeping obligations and export anything you need first.
Three retention settings (clause 10.13). Recordings, transcripts and AI notes, and message attachments each have their own retention period. If your organisation was created before 8 October 2026, nothing has changed: recordings keep the period you had, and transcripts, AI notes and attachments are kept until you ask us to set a period. Organisations created from that date start at 365 days for all three. Why: many firms keep the transcript longer than the audio, because it becomes their record once the audio has gone.
Presence history is kept for 28 days (DPA Schedule 1). Cradle records each person's status (available, busy, away, offline) so that wallboards, reports and support can show who was available when a call rang. That history is now deleted automatically after 28 days, and when your account closes. Why: it's information about your staff. Four weeks is enough to answer questions about recent calls, and we don't want to build a long record of when people worked.
Deletion applies to what Cradle holds (clause 10.16). Deleting something in Cradle doesn't delete a copy already filed to FYI, XPM, Karbon, HubSpot or another system you've connected. Why: that copy is your record in your own system, under your agreement with that provider. We can't see or manage it.
Pausing deletion for a legal matter (clause 10.14). If you're facing a legal proceeding, regulatory inquiry or professional-conduct matter, an admin can ask us in writing to suspend automatic deletion of specified data until it's resolved. The pause starts only when we confirm it in writing, so please check you've heard back. It works by extending your retention period, the additional storage is charged, and it doesn't stop your own team deleting things. Why: you may have a duty to preserve records, and until now there was no way to ask us to stop a retention sweep.
Who at Cradle can see your data (clause 10.3 and DPA clause 4.3). Our people don't listen to recordings or read transcripts or messages except when you ask us to for support, or where it's necessary to investigate a security incident, suspected fraud or a breach of the terms. The service is designed to support this: our staff can open your calls, recordings, transcripts and messages through Cradle only while one of your admins has granted support access in the admin portal. Each grant lasts no more than 24 hours, and your admins can see each request made under it. Why: "who can hear our recordings?" is the question we're asked most, and the answer belongs in the contract.
If the service isn't operating as the terms describe, we correct it and tell you (clause 4.8). Why: the service and the suppliers behind it change frequently. If we discover a discrepancy, or you tell us about one, the terms commit us to correct it as soon as reasonably practicable and to tell you where it has affected your data.
AI features
Recordings are the record; AI output is an aid (clause 9.2). The recording is the authoritative record of a call. Transcripts, summaries and notes are generated automatically, may contain errors, and need a person to review them before they're relied on. Why: AI notes are filed straight into client records, and firms asked which one counts if the two differ.
AI training (clause 9.6 and DPA clause 3.5). We don't use your data to train general-purpose AI models or models made available to other customers, unless you expressly opt in. We contractually require our AI suppliers not to train on it, and we've added that we configure those services so your data is excluded from any "model improvement" programme, and that suppliers don't keep it beyond the 24-hour processing window, apart from abuse monitoring (below). If a supplier changes its terms in a way that conflicts with this, the terms say what we'll do about it. Why: supplier defaults and terms change, so a commitment about our own conduct needs to be matched by how those services are set up and monitored.
Abuse monitoring by AI providers (clauses 3 and 9.6, DPA clauses 3.5 and 6.4). Keeping a short-term copy of requests to check for misuse is now standard practice among the major AI providers, and a condition of using their services. It's also becoming the price of access to the best models: more and more of the newest and most capable models are offered only on the condition that abuse logging stays switched on, with no option to turn it off. Allowing for it means we can keep offering you better AI features as those models arrive, within the limits below. The terms call this "Safety Retention" and set firm limits on it:
- the provider keeps the copy only to detect and prevent abuse, fraud and other security or safety threats;
- only its automated safety systems and the people responsible for safety review can access it;
- it isn't used to train models or for anything else;
- it's deleted at the end of the period shown for that provider on our sub-processor register, which can never be more than 90 days. Today that's up to 90 days for Google's Gemini models and none for AssemblyAI. If a provider's period goes up, we give you 14 days' notice and you can object, as for a new supplier;
- nobody at Cradle, and nobody at your firm, can see or retrieve the copy.
We seek exemptions where a provider offers them on reasonable terms, and when one is confirmed we'll reduce the period on the register.
Why it protects you: AI services are targets for criminals, who use them to write scam messages, impersonate people and probe for weaknesses. Abuse monitoring is how providers spot that, including attempts to misuse an account like ours if credentials were ever stolen. It also keeps the service you rely on available: a provider that can't check for misuse is more likely to restrict or suspend an account when something looks wrong.
Why it protects Cradle: it's a condition of using the enterprise AI services we've chosen. Writing it into the terms, with limits, means our promises to you stay accurate, and a provider doing what its terms require doesn't put us in breach or force us to switch off features you use. A blanket "no retention" promise would have been simpler to write, but not true.
Local processing and redaction (clauses 9.8 and 9.9). We're developing an option to record, transcribe and summarise on your own computer using open-source models, and an opt-in feature that attempts to redact information you classify as sensitive before it's stored or filed. Neither is available yet. Please read the clauses before you turn either on: the local models run on your machine at your own risk, and redaction is best effort, not a guarantee. Why: describing them now means the terms are already in place when they're released.
Privacy law and housekeeping
Australian, NZ and UK privacy law, addressed directly (DPA clause 12). The DPA now sets out how it works under APP 8 for Australian firms, section 11 and IPP 12 of the NZ Privacy Act 2020, and the UK GDPR. Why: this is the wording your own privacy policy or engagement letter can refer to.
Integrations (clause 5.8). The permissions an integration asks for are shown on the partner's own authorisation screen (HubSpot, Xero, FYI and so on) before you approve it. That screen is the one to review.
Fair use, rewritten. The previous fair use policy dated from 2019 and capped calling minutes and stored contacts per user. Both caps are gone. The new policy describes normal use in plain terms and explains what happens if usage is flagged.
Where notices go (clause 20.5). Notices to us about the terms go to legal@cradle.io, and about the DPA to privacy@cradle.io. Notices to you go to your admins or billing contact, so please keep those current.
Smaller changes. The browser extension is now covered by the software definition, "Recording" means the audio and "Transcript" means the text, and some cross-references were corrected.
What you need to do
For most customers, nothing. Four things are worth checking:
- Retention. Check your retention periods against your own record-keeping obligations. To change one, email help@cradle.io from an admin account.
- Client disclosure. If you're a tax practitioner, accountant or lawyer, read the client disclosure guide and check that your engagement letter or privacy policy names the countries where Cradle holds data.
- Tax number. If you're in Australia or the UK and we don't have your ABN or VAT number, we'll be in touch to ask for it.
- Notices. If supplier-change notices should go to a compliance mailbox, email privacy@cradle.io with the address.
If you don't accept a change
If a change materially and adversely affects you, clause 2.2 lets you tell us in writing that you don't accept it, and the previous terms keep applying until your current term ends. Your notice needs to reach legal@cradle.io before 18 December 2026.
We'd also like to hear from you if something here doesn't fit how your firm works. Questions to legal@cradle.io.