Contents
1 Who we are
Aunbound is an AI voice-calling platform ("Aunbound", "the Service", "we", "us"). People use it in two ways: individuals create scheduled calling agents that call them or numbers they have verified, and businesses run bulk outbound campaigns and inbound answering. Aunbound is operated from Bengaluru, Karnataka, India.
This Privacy Policy describes how we collect, use, disclose, store, and protect personal data in connection with the Service, including our website, dashboard, the voice agent itself (MAYA), and the channels it operates over (outbound and inbound voice, SMS where used, and email).
2 Scope and our roles
Personal data flows through Aunbound in two distinct ways, and our legal role differs in each:
- As a Data Fiduciary / Controller — for personal data about our account holders and their authorised users, whether an individual on a Free or Pro plan or a business account: signup phone number, login details, billing contacts, and the agents they create. We decide why and how this data is processed.
- As a Data Processor — for personal data about the people our users call: numbers a user verifies and schedules an agent against, lead lists a business uploads, and the recordings and transcripts of those calls. Here the user is the Data Fiduciary and decides the purpose; we process on their instruction under our Terms of Service.
Where we act as a Processor, the user is responsible for having a lawful basis to call each recipient — including when an individual points an agent at a family member, a tenant, or a contact. This Policy still tells recipients how to reach us and exercise their rights.
One case has no second party: on the Free plan an agent can only call the account holder's own verified number, so the only recipient is the user themselves.
3 Data we collect
From account holders
- Signup and account data — the phone number you sign up with and the one-time code we send to it by call or SMS to verify it; name, email, business name and role where provided; password (hashed) or, if you sign in with Google, the email, name and account identifier Google returns.
- Verified numbers — the phone numbers you verify as numbers your agents are allowed to call.
- Agents you create — the name, description, schedule and settings of each agent, and for agents you write yourself, the instructions and opening line you supply. We store these as account content, process them to run your calls, and may review them to investigate abuse or a support request.
- Billing data — plan, subscription status, minutes used, invoices and payment metadata, and for business accounts any wallet balance, transaction history and GST details. Card and bank details are handled by our payment processor, Razorpay; we never receive or store full card numbers.
- Usage data — agents and campaigns created, calls placed and their outcomes, dashboard activity, configuration and logs.
- Technical data — IP address, device and browser type, and cookies or similar identifiers needed to operate the dashboard, keep you signed in, and keep it secure.
- KYC data — for Business accounts that need to call numbers beyond their own verified contacts, the identity and business documents we ask for as part of approval.
About the people our users call
- Recipient data — phone number, and any name or other detail the user supplies for the call. For business campaigns this includes the columns of an uploaded contact list: name, phone, email, company, job title, and any other field the customer chooses to upload and have the agent use during the call.
- Interaction data — the recording and transcript of the call, its duration and cost, the outcome our system classified it as, and the notes the agent recorded about what was said. For business campaigns this may also include AI-generated research notes about the contact or their company, used to personalise the call.
4 If you received a call or message from Aunbound
If you are a person who received a call from Aunbound, your number was provided by one of our users — an individual or a business — who is responsible for that call. Every Aunbound call states that it is automated, and ends the call if you ask not to be called again. You can also:
- Ask to know which account initiated the call;
- Ask to be removed from that account's lists and not called again;
- Request a copy or deletion of any recording or data we hold about you, subject to our verifying your identity and the customer's instructions.
Reach us at dhipinkumar@gmail.com. We will route your request to the relevant account holder where they are the Data Fiduciary, and we honour opt-outs across our platform.
5 Call recordings and transcripts
Every call placed or answered through Aunbound is recorded and transcribed — including calls made by an individual's own agent, not only business campaigns. We do this to operate the Service, show you what happened on a call, classify its outcome, meter billing, resolve disputes, and keep compliance records.
- Recordings are produced by our telephony provider and stored on our infrastructure in India; a copy may also be retained briefly by that provider.
- Transcripts are generated by automated speech recognition. Our agent also records a short outcome and notes describing what happened on the call.
- Recordings and transcripts are accessible to the account holder who owns the call and to our authorised staff for support, billing and security investigations.
- Our agent always states that it is an automated call, and answers honestly if asked whether it is a human. Users remain responsible for ensuring that recording a given call is permitted under applicable law.
- How long we keep them is set out in section 10.
6 How we use data
| Purpose | Examples |
|---|---|
| Provide the Service | Place calls, send messages, run campaigns, show results in the dashboard. |
| Run your agents | Render the agent's prompt, place the call at the scheduled time, retry an unanswered call. |
| Personalise outreach | Generate per-contact research and conversation hooks, on a business customer's instruction. |
| Safety | Apply the rules that sit around every agent's prompt, and review calls reported as abusive. |
| Billing | Meter minutes used, charge your plan and any overage, issue invoices. |
| Support & quality | Diagnose issues, review recordings for accuracy and complaints. |
| Security & fraud | Detect abuse, protect accounts, maintain audit logs. |
| Legal compliance | Respond to lawful requests; keep records we are required to keep. |
We do not sell personal data, and we do not use your contacts or lead lists for our own marketing. We do not use your call recordings, transcripts or the agents you write to train our own models; the third-party AI providers listed in section 8 process this data to deliver the call and are contractually restricted to that purpose.
7 Lawful basis and consent
For customer and account data, we process on the basis of contract performance, our legitimate interests in operating the Service, your consent where required, and compliance with law. Under India's Digital Personal Data Protection Act, 2023, where consent is the basis, you may withdraw it at any time.
For outbound calling, users must comply with applicable telecom and unsolicited-communication rules, including TRAI regulations and Do-Not-Disturb requirements. Account holders — business or individual — are responsible for honouring DND registrations and consent requirements for the people they call. Calling numbers beyond your own verified contacts requires an approved Business account.
8 Sharing and sub-processors
We share data with service providers ("sub-processors") who help us run the Service. They are permitted to use the data only to provide their service to us. As of the date of this Policy they are:
| Provider | What it does | What it receives |
|---|---|---|
| Plivo | Telephony — places and answers calls, records them, sends SMS | Phone numbers, call audio, call metadata |
| Deepgram | Speech recognition during the call | Call audio, transcribed text |
| Sarvam AI | Text-to-speech — the agent's voice | The text the agent is about to say |
| Cerebras | Language model that runs the conversation | The agent's prompt and the running transcript |
| Groq | Classifying call outcomes, and lead research for business campaigns | Transcripts, contact details |
| Google (Gemini, Cloud OAuth) | Lead research for business campaigns; "Sign in with Google" for the dashboard | Contact and company details; your Google account email and name |
| Serper | Web search used for lead research | Company or contact search terms |
| Resend | Transactional email (verification, notifications) | Your email address and the message |
| Razorpay | Payments and subscriptions | Billing contact details and payment metadata |
We update this list when we change providers. If you need notice of changes for a contractual reason, ask us.
We may also disclose data to comply with law, enforce our Terms, or protect rights and safety. If our business is involved in a merger or acquisition, data may transfer as part of that transaction, subject to this Policy.
9 Where data is stored and processed
Customer accounts, campaign data, recordings, and transcripts are stored on infrastructure located in India (Bengaluru region).
However, to deliver the Service in real time, some data is processed by sub-processors that may operate outside India — for example, speech recognition, language-model inference, and lead-research providers. This means certain personal data (such as call audio, transcribed text, and contact details) may be transmitted to and processed in other jurisdictions during a call or campaign. We use such providers under contractual terms intended to protect that data. By using the Service, customers instruct us to carry out this processing.
10 Retention
We keep personal data only as long as needed for the purposes above, then delete or anonymise it.
- Call recordings and transcripts — retained for 12 months from the date of the call, then deleted, unless a longer period is required by law or the recording is subject to an open dispute or investigation.
- Call metadata (time, duration, outcome, cost) — kept for the life of the account, because it underpins your usage history and our billing records.
- Account and billing records — kept for the life of the account and thereafter for the periods required by tax and accounting law.
- Agents you create — kept until you delete them or close your account.
You may ask us to delete a specific recording, or all of your data, at any time using the contact details below. On account closure we delete your account data, agents and recordings, other than records we must keep by law.
11 Security
We use technical and organisational measures to protect personal data, including access controls, encryption in transit, tenant isolation, and audit logging. No system is perfectly secure; see our Security page for details and how to report a vulnerability.
12 Your rights
Subject to applicable law, you may request to access, correct, update, or delete your personal data, withdraw consent, or object to certain processing. To exercise these rights, contact us using the details below. We may need to verify your identity. Where we act as a Processor for a customer's contact data, we will direct your request to that customer.
13 Children
The Service is intended for businesses and is not directed to children. We do not knowingly collect personal data from children. If you believe a child's data has been provided to us, contact us and we will delete it.
14 Changes to this Policy
We may update this Policy from time to time. We will post the revised version here with a new "Last updated" date, and where changes are material we will take reasonable steps to notify customers.
15 Contact and grievances
For privacy questions or to exercise your rights, contact:
- Email: dhipinkumar@gmail.com
- Grievance Officer: Dhipin Kumar Ramesh, dhipinkumar@gmail.com
- Location: Bengaluru, Karnataka, India. Our postal address is available on request if you need to write to us.
As required under Indian law, we will acknowledge and respond to grievances within the statutory timeframe.