Contents19 sections
This policy explains what personal data Decrackle collects, why we use it, the legal basis for each use, who we share it with, where it goes, how long we keep it and what rights you have. It is written first for the EU General Data Protection Regulation (GDPR) and also for India's Digital Personal Data Protection Act, 2023 (DPDP Act) and the DPDP Rules, 2025.
It covers all of our services, which this policy calls the "Services":
- our website, www.decrackle.io;
- Decrackle Studio at studio.decrackle.io, including Clarity, Scribe, Narrate, voice cloning and multi-voice conversations;
- the Decrackle API; and
- Decrackle Agents, our voice agents, including the website widget and test calls.
"Personal data" means any information about a person who is identified or can be identified.
Who we are and how to reach us
Decrackle, Inc. decides how and why the personal data described here is used. It is the "controller" under the GDPR and the "Data Fiduciary" under the DPDP Act.
Decrackle, Inc.
651 N Broad Street, Middletown
New Castle County, Delaware 19709
United States
- Privacy questions, rights requests and grievances: support@decrackle.io. Please put "Privacy" in the subject line.
- Grievance Officer (India): our Grievance Officer answers questions and grievances about personal data under the DPDP Act. Write to the Grievance Officer at support@decrackle.io.
- Copyright matters: copyrights@decrackle.io.
- Contact page: decrackle.io/contact.
Decrackle's contact team in India can be reached at Next Cowork, 5th floor, Aranya Nagar, Scheme 78, Vijay Nagar, Indore, Madhya Pradesh 452010. This team is not part of Decrackle, Inc. It reads and answers messages sent to support@decrackle.io on our behalf. The controller for your data is Decrackle, Inc. at the address above.
Our two roles
We hold personal data in two different roles.
When we decide (controller). We decide how to use the data about our own users and visitors: accounts, billing, website visits, messages to us, marketing choices, security records and analytics. This policy fully covers that data. We are also the controller when we use customer content to train our models (see AI model training).
When we act for a customer (processor). Customers use the Services to process their own material, which often contains personal data about other people: callers who phone a business that uses Decrackle Agents, guests on a podcast, people in a recorded meeting. For that material, the customer decides what is collected and why, and the customer's own privacy notice applies. We process it to provide the Services to that customer.
If you think a Decrackle customer holds your data, please contact that customer first. If you write to us instead, we will pass your request to the customer where we can identify them.
If you use Studio for your own projects and your recordings include other people, you must have the right to record and process their voices.
Personal data we collect
Some data is needed to provide the Services. An account needs an email address and a password or Google sign-in, and paid plans need billing details. If you do not give them, we cannot create the account or provide the paid plan. Before you first use Studio, you must also give the details listed below under "Before you first use Studio", except the tax ID, your product news choice and how you heard about us, which are optional. Your profile details are optional.
Account details
- When you sign up: email address, password or Google sign-in, and your name. With Google sign-in we receive your Google account ID, email address, name and profile picture. You can also give an alternate email address and a company name.
- Before you first use Studio: first and last name, country, account type (personal or business), company name for business accounts, an optional tax ID, what you plan to use Decrackle for, whether you will work with other people's voices, confirmation of your age, and when you accepted the Terms. You can also tell us whether you want product news and how you heard about us.
- Optional profile details: display name, phone number, job title, time zone, language, a short bio and a photo.
- Your choices: your settings, your cookie choice (saved with your account so it applies when you sign in), and a partner code if you arrived through a partner's link (see Cookies).
Billing details
Payments are handled by Stripe on Stripe's own checkout page. Stripe collects your card details, billing name and address, and any tax ID you give. We receive your plan, payment and invoice history, and only the card brand, last four digits and expiry date. We never receive the full card number.
Content you send to the Services
- Studio and the API: audio and video you upload and their file names; enhanced audio from Clarity; transcripts, captions and speaker labels from Scribe; the text you enter in Narrate and the speech it generates; scripts and audio for multi-voice conversations; and your projects. The API stores the same kinds of content as Studio.
- Voice clones: up to 10 voice samples, a short reference clip cut from them, and a voice model. The voice model includes a speaker embedding, a set of numbers that describes how the voice sounds. We also store the transcript of the samples, the labels you choose (language, gender, age group, accent, use case), a description, and the consent record described in Voice data.
- Agents: the caller's phone number (or a test number for web test calls); call transcripts; call times and duration; what the agent did during the call, such as tickets it opened; and an automatic summary after each call with the caller's name and the answers to the questions the customer set. In what the agent did, Indian mobile numbers, Aadhaar and PAN numbers are masked to their last four digits. Agents remember returning callers by phone number by default: the caller's name, the number of calls, the last three call summaries and open tickets. The customer can turn this off. Agents also hold the customer's knowledge base text (we keep the text and a search index, not the uploaded file), data tables, test conversations and settings.
Messages and forms
- Website forms: the demo form (first and last name, email, company, job title, phone number, what you are asking about, notes, preferred date and times, and time zone); the contact form (first and last name, email, job title, topic and message); the about form (first and last name, email and message); the waitlist and the newsletter sign-up (email). We record demo, contact and about messages in our admin panel. If you ask for a copy of a demo request or message, we email it to the address you entered.
- Studio contact form and support: name, company, email address, topic and message, and your support tickets.
- Email: what you write to support@decrackle.io or copyrights@decrackle.io.
Data collected automatically
- Device and connection data: IP address, browser and device type, and the pages and features you use.
- Security data: failed sign-in attempts and request limits per IP address. A Cloudflare bot check runs when you sign in or sign up.
- API logs: for every request made with an API token, we record the endpoint, method, response status, time, IP address and browser or client name.
- Analytics: only if you accept analytics. See Cookies.
Data about people who do not deal with us directly
Some data reaches us from our users rather than from the person it is about: the voice of someone whose samples a user uploads to make a voice clone, people heard in uploaded recordings, and callers to a customer's agent. The kinds of data are those listed above under "Content you send to the Services". If you think your data reached us this way, write to support@decrackle.io.
Voice data
A recording of a person's voice is personal data whenever the person can be identified. This is how we handle it:
- Only for the feature you use. We use voice data to enhance, transcribe and generate speech, to make and use voice clones, and to run agent calls. We may also use it to train our models unless you opt out (see AI model training).
- We do not identify people by their voice. No feature identifies or verifies who a speaker is. Scribe gives the speakers in each file numbered labels, which you can rename, without knowing who they are. A voice clone's speaker embedding is used only to generate speech in that voice, never to match or recognise people. Agents recognise returning callers by phone number, not by voice.
- Voice clones need permission. Before every clone you must confirm: "I confirm I have all necessary rights or consent to upload and clone these voice samples, and I won't use the generated audio for anything illegal, fraudulent or harmful. I agree to Decrackle's Terms and Privacy Policy." We record when you confirmed, which version of this text you saw, and your browser. You may clone only your own voice, or the voice of someone who has given you written permission.
- If your voice was cloned without your permission, write to support@decrackle.io.
AI model training
Training our models on customer content is on by default. Unless you opt out, we may use the content you send to the Services to train and improve our models.
Every user can opt out. To opt out, write to support@decrackle.io from the email address of your account.
Zero data retention is offered to enterprise customers only. To ask about it, write to support@decrackle.io.
For this use we rely on our legitimate interest in improving the quality of our models. You have the right to object to it at any time (see Your rights).
How we use personal data and our legal bases
For each use, this list names the legal basis under GDPR Article 6. For content we process for a customer, the customer decides the legal basis.
- To create and run your account and provide the Services: sign-in, running Clarity, Scribe, Narrate, voice cloning, Agents and API requests, and storing your files and projects. Basis: contract.
- To bill you: payments through Stripe, invoices and plan changes. Basis: contract. Keeping billing and tax records: legal obligation.
- To send service emails: email verification, sign-in codes, password resets, billing notices and account deletion confirmations. Basis: contract.
- To answer your messages and demo requests and give support. Basis: contract, or steps you asked for before a contract; otherwise legitimate interests (answering people who contact us).
- To keep the Services safe: limits on sign-in attempts, the bot check, API logs, preventing fraud and misuse, keeping voice-clone consent records and enforcing our Terms. Basis: legitimate interests (protecting accounts, the Services and the people whose voices are used).
- Analytics with PostHog, Google Analytics and Cloudflare Web Analytics. Basis: consent, given in the cookie banner or settings.
- Hourly totals without identifiers (see Cookies). Basis: legitimate interests (understanding how the Services are used).
- To train and improve our models, unless you opt out. Basis: legitimate interests (improving our models).
- To send product news and the newsletter. Basis: consent.
- To credit a partner who referred you (the dc_ref cookie and the partner code saved with your account). Basis: legitimate interests (paying partners who refer customers).
- To meet legal duties and protect our rights: answering lawful requests, keeping records, and bringing or defending legal claims. Basis: legal obligation; legitimate interests (protecting our rights).
- For a merger, acquisition or sale of assets: due diligence and transfer. Basis: legitimate interests.
Where we rely on legitimate interests, we have weighed our interests against your rights. You can ask us for the details of that assessment and object at any time.
India. Under the DPDP Act, we process personal data on the basis of consent you give after reading this notice, or for a legitimate use the Act allows, such as data you give us voluntarily for a purpose you know about. You can withdraw consent at any time (see Your rights).
Automated decisions
We do not make decisions about you based solely on automated processing that have legal or similarly significant effects on you. Automatic security measures, such as pausing sign-in after repeated failed attempts, do not have such effects.
After each agent call, an AI model reads the call transcript (text only, not the audio). It writes a summary and checks the call against the questions the customer set. These results go to the customer, who decides what to do with them.
International transfers
Decrackle, Inc. is in the United States, and several of the providers above are in the United States. When we send personal data from the EU or EEA to Amazon Web Services, Stripe, PostHog, Google, Cloudflare, Groq or OpenAI, these safeguards apply:
- EU-US Data Privacy Framework (DPF): the European Commission has decided that US companies certified under the DPF protect personal data adequately. Amazon (covering Amazon Web Services), Stripe, PostHog, Google and Cloudflare are certified.
- Standard Contractual Clauses (SCCs): contract terms approved by the European Commission. They are part of the data processing terms of Amazon Web Services, Stripe, PostHog, Google, Cloudflare and Groq. Groq is not certified under the DPF, so transfers to Groq rely on SCCs.
- OpenAI: transfers to OpenAI are covered by our data processing agreement with OpenAI.
Brevo SAS is in France, so sending data to Brevo is not a transfer out of the EU.
From India: the DPDP Act allows personal data to be processed outside India, except in countries the Government of India restricts. We will not transfer personal data to a restricted country, and we will meet any conditions the Government of India sets for transfers outside India.
You can ask us for a copy of the safeguards at support@decrackle.io.
How long we keep data
We keep personal data only as long as we need it for the purposes in this policy, or as the law requires. We may keep data longer if we need it for a legal claim or a legal hold.
- Your account: while it is open. You can close it in Studio under Settings, Account. We send you a link to confirm, valid for 24 hours. We delete your account 14 days after you confirm, or at the end of a cancelled plan's paid period if that is later, and you can cancel the deletion until then. Deletion removes your Studio files, library, jobs, transcripts, generated speech, voice clones and their consent records, conversations, projects, support tickets, API tokens and their logs, profile photo, and the analytics data in PostHog that is linked to your account.
- What stays after your account is deleted: a minimal record with your account ID, a one-way coded fingerprint of your email address (so support can tell whether an address had an account), your Stripe customer ID, how you signed in, your role and key dates.
- Billing and tax records (ours and Stripe's): kept after account deletion for as long as tax and accounting law requires.
- Files and items you delete yourself: the audio is deleted at once. The text of a deleted transcript or Narrate run, and the record of a deleted voice clone with its consent record, stay until your account is deleted. Voice samples stay in your Library until you delete them there.
- Agents data: call records, transcripts, caller memory, tickets and data tables have no fixed end date. You cannot yet delete call records in the product, and closing a Studio account does not delete Agents data. Deleting an agent hides it but keeps its data. Deleting a knowledge base deletes its searchable text and search index; the list of its documents is hidden but kept. To have Agents data deleted, write to support@decrackle.io.
- Messages, form submissions and the Studio contact form: no fixed end date, and not removed when your account is deleted. You can ask us to delete them.
- Newsletter: an unconfirmed sign-up is deleted after 7 days, and the confirmation link works for 48 hours. A confirmed address is kept until you unsubscribe or ask us to delete it.
- Sign-in: you stay signed in for 30 days, or until you close the browser if you turn off "Remember me". Email verification links last 24 hours, password reset links 1 hour and sign-up codes 10 minutes.
- Analytics: Google Analytics deletes user-level and event-level data after 2 months. PostHog data linked to your Studio account is deleted when you delete the account.
- Cookies: your cookie choice is kept for 6 months and the partner cookie dc_ref for 90 days. See Cookies.
- Job applications: see Job applicants.
How we protect data
We protect personal data with technical and organisational measures, including:
- HTTPS on our sites;
- sign-in sessions held in cookies that page scripts cannot read;
- limits on sign-in attempts and a bot check at sign-in and sign-up;
- encrypted storage of secrets that customers save for their agents, such as API keys;
- masking of Indian mobile, Aadhaar and PAN numbers in what an agent records about its actions; and
- session recordings that hide everything you type and all text on the page.
No method of sending or storing data is completely secure, so we cannot guarantee absolute security.
Your rights
To use any right below, write to support@decrackle.io. Please write from your account's email address, or include it, so we can identify you. You can also do some things yourself in Studio: edit your profile, delete files, transcripts, voices and projects, turn emails off, change your cookie choice and close your account. We may need to confirm your identity before we act. Requests are free unless the law allows a fee, for example for requests that are clearly unfounded or excessive.
If your data is customer content, for example because you called a business that uses Decrackle Agents, please send your request to that business. We will help them answer it.
EU and EEA
You have the right to:
- access your personal data and get a copy;
- correct data that is wrong or incomplete;
- erase your data;
- restrict how we use your data, for example while we check a complaint;
- data portability: receive the data you gave us in a machine-readable format, or have it sent to another company;
- withdraw consent at any time, as easily as you gave it. This does not affect what we did before you withdrew. For analytics, use Cookie settings on decrackle.io or Settings, Privacy and data in Studio;
- not be subject to a decision based solely on automated processing that has legal or similarly significant effects on you; and
- complain to a data protection authority, in particular in the EU country where you live or work, or where you think the law was broken. We would welcome the chance to fix the problem first.
We answer within one month. If a request is complex, we may take two more months, and we will tell you why within the first month.
Your right to object
You can object at any time to our use of your personal data based on legitimate interests, including model training. We will then stop, unless we have compelling legitimate grounds that override your interests, rights and freedoms, or we need the data for a legal claim.
You can object at any time to the use of your data for direct marketing. We will then stop using it for marketing.
India
Under the DPDP Act, you have the right to:
- get a summary of the personal data we process about you and how we process it, and the names of the other Data Fiduciaries and Data Processors we have shared it with;
- have your data corrected, completed, updated or erased;
- withdraw your consent at any time, as easily as you gave it. We and our processors will then stop processing your data, unless the law allows us to continue. Withdrawal does not affect processing done before it;
- have your grievances addressed by our Grievance Officer at support@decrackle.io. We answer grievances within 90 days; and
- nominate another person to use your rights if you die or become unable to act. To nominate someone, write to support@decrackle.io with their name and contact details.
If you are not satisfied with our answer to your grievance, you can complain to the Data Protection Board of India through its online platform, as described on the Board's website.
Other countries
If you live elsewhere, you may have similar rights under local law. Write to us and we will help.
Children
The Services are not for children. When you set up Studio, you must confirm your age:
- 16 or older if you choose the United Kingdom, Germany, France or Spain; and
- 18 or older for every other country, including India and all other EU countries.
In India, anyone under 18 is a child under the DPDP Act, and processing a child's data needs verifiable consent from a parent or lawful guardian. We do not collect that consent, so people under 18 in India must not use the Services. In the EU, each country sets its own age at which a child can consent to online services, and it is never higher than 16.
We do not knowingly collect personal data from anyone below these ages. If you believe a child has given us personal data, write to support@decrackle.io and we will delete the account and its data.
Job applicants
We advertise jobs and receive applications on Wellfound. When you apply, we receive the application you send through Wellfound. Wellfound handles your data under its own privacy policy.
We use your application only to assess you for the role and to contact you about it. Basis: steps you asked for before a possible employment contract, and legitimate interests (hiring). In India, this is a legitimate use the DPDP Act allows for employment purposes.
We keep applications with no fixed end date. You can ask us at any time to delete your application by writing to support@decrackle.io. You also have the other rights described in Your rights.
Links to other websites
The Services link to websites run by others, such as Wellfound and our social media pages. We do not control those sites and are not responsible for how they handle personal data. Please read the privacy policy of each site you visit.
Changes to this policy
We will update this policy when the Services or the law change. The date at the top shows when it last changed. If we make a material change, we will tell you by email or with a notice in the Services before the change takes effect.
Contact and complaints
- Privacy questions, rights requests and grievances (including our Grievance Officer): support@decrackle.io
- Copyright matters: copyrights@decrackle.io
- Contact page: decrackle.io/contact
- Post: Decrackle, Inc., 651 N Broad Street, Middletown, New Castle County, Delaware 19709, United States
If you are not happy with our answer, you can complain to the data protection authority in your country. In India, you can complain to the Data Protection Board of India.
Questions about this document?
Write to support@decrackle.io or reach the team directly.