Who this is about
Bellatech Marketing Pvt. Ltd. (“we”) operates Tone, a telephony API that lets our customers give AI agents an Indian phone number. This policy covers two different groups of people, and the distinction matters throughout:
- Our customers — the businesses and developers who hold a Tone account. We are the data fiduciary for their account, billing and compliance data.
- People our customers call — the subscribers on the other end of a call. For their personal data we are a data processor acting on our customer’s instructions. The customer decides who is called and why, and is responsible for having a lawful basis to call them.
If you received a call and want it to stop, you do not need to contact us first: say so on the call, or press 9 during it, and the number is suppressed. You can also write to hello@usetone.ai.
What we collect
| Category | What it is | Why |
|---|---|---|
| Account | Name, work email, organisation name, password hash, sign-in history | To create and secure the account |
| Business identity | GSTIN, CIN, PAN, authorised signatory details, DLT Principal Entity ID and any documents uploaded to support them | Telecom regulation requires us to know who is placing calls before we let them place any |
| Call data | Numbers dialled and received, call times and durations, outcomes, audio recordings, transcripts and generated summaries | To place the call, to bill for it, and to give the customer the record of what happened |
| Compliance records | Consent records, opt-outs, do-not-call entries and the pre-dial checks run before each call | Evidence that a call was permitted. Required by TRAI’s TCCCPR and kept as a tamper-evident record |
| Billing | Wallet balance, ledger entries, payment identifiers from our payment processor | To take payment and produce invoices |
| Technical | IP address, browser and device details, request logs | To keep the service running and to investigate abuse |
We do not store card numbers. Payments are handled by Razorpay; card details go to them and never reach our servers.
How call recordings and transcripts are handled
A recording exists because a customer switched recording on for a number. Customers can turn it off per number, and where the deployment has recording disabled a per-number setting cannot turn it back on.
Recordings and transcripts are stored encrypted, in India, and are visible only to the customer who owns the call and to the small number of our staff who need them to investigate a fault. Our logs are configured so that the words spoken on a call are never written into them — only lengths and identifiers.
Who else sees it
We do not sell personal data and we do not share it for advertising. We use the following processors, each for the stated purpose only:
| Processor | What it does | Where |
|---|---|---|
| Amazon Web Services | Application, dashboard and documentation hosting, database, and object storage for recordings, transcripts and KYC documents | Mumbai, India (ap-south-1) |
| Zoho (ZeptoMail) | Transactional email — sign-up codes, password resets and account notices | India (Zoho's India data centre) |
| Exotel | Telephony carrier — places and receives calls, issues phone numbers | India |
| VoiceLink | Telephony carrier — places and receives calls, issues phone numbers | India |
| Plivo | Telephony carrier — places and receives calls, issues phone numbers | India (Plivo's India data region) |
| Sarvam AI | Speech recognition and speech synthesis during a call | India |
| Murf AI | Speech synthesis during a call, for agents that use a Murf voice | Mumbai, India (Murf's India region) |
| Cartesia | Speech synthesis during a call, for agents that use a Cartesia voice | United States |
| Google Cloud (Vertex AI) | The language model that generates an agent's replies during a call, and knowledge-base embeddings | Mumbai, India (asia-south1) |
| Microsoft Azure (Azure OpenAI) | The language model behind post-call summaries, the dashboard's agent-editing assistant, translations of an agent's custom lines, knowledge-base answer previews and the documentation site's assistant — and an agent's replies during a call, for agents set to use it | Chennai, India (South India region); questions typed into the documentation site's assistant may be processed in other Azure regions |
| Meta Reach Marketing (FilterDND) | Checks the phone numbers of PROMOTIONAL calls against India's DND register before they are placed. Numbers for transactional and service calls are never sent | Germany (the lookup server); the company is in Noida, India |
| Razorpay | Payment processing for wallet top-ups | India |
| PostHog | Product analytics and dashboard session recording | European Union |
| Slack | Internal notifications to our team: new sign-ups (name, email, organisation), payments, support conversations and service alerts | United States |
We also disclose data where the law requires it — to a court, to TRAI or an access provider investigating a complaint, or to a law enforcement request we are satisfied is valid.
Where it lives
Primary storage is in India — Mumbai (ap-south-1) for the application, dashboard, documentation, database, recordings, transcripts and documents, and Mumbai (asia-south1) for the language model that generates an agent’s replies on a call. Some processing happens outside India: the dashboard’s agent-editing assistant runs on Google’s global endpoint, product analytics for our own dashboard are processed in the European Union, the documentation assistant runs in the United States, and our team’s internal notifications are delivered through Slack in the United States.
How long we keep it
| Data | Retention |
|---|---|
| KYC documents you upload | 180 days after a decision, then deleted automatically |
| Verification responses from identity providers | 3 years |
| Pre-dial compliance checks and call evidence | 3 years. These are the record that a call was permitted and are append-only — they cannot be edited after the fact, by us or by anyone else |
| Wallet ledger and invoices | Retained for as long as tax and company law require, and not deleted on account closure |
| Call recordings, transcripts and summaries | Retained while the account is open, and deleted on request. We do not yet apply an automatic expiry to these — if you want a specific retention period applied to your account, ask us and we will set it up |
| Account data | Deleted within 90 days of account closure |
Your rights
Under the Digital Personal Data Protection Act, 2023 you may ask us to:
- tell you what personal data of yours we hold and who we shared it with;
- correct anything inaccurate, or complete anything missing;
- erase data we no longer have a reason to keep;
- nominate someone to exercise these rights if you cannot; and
- withdraw consent you previously gave, as easily as you gave it.
Write to hello@usetone.ai. We will respond within 30 days. Where the data belongs to someone our customer called, we will pass the request to that customer, since they decide what happens to it — and we will tell you that we have.
Grievance Officer: Ridhith Arora, hello@usetone.ai. If we do not resolve your complaint you may escalate it to the Data Protection Board of India.
Security
Tenant data is isolated at the database level, so one customer’s query cannot reach another’s rows even if the application is wrong. Credentials our customers store for their own integrations are encrypted with a key that never leaves our servers. Traffic is encrypted in transit, and identifiers such as phone numbers are masked in our operational logs, readable only under an audited permission.
No system is perfectly secure. If you believe you have found a vulnerability, write to hello@usetone.ai and we will acknowledge within two working days.
Cookies
We use a session cookie to keep you signed in, and a small number of first-party analytics events to understand which parts of the dashboard are used. We do not use advertising cookies and we do not run third-party trackers on the dashboard.
Session recording
To understand where the dashboard is confusing or broken, we record how it is used — the pages visited, and where a pointer moves and clicks. Recordings cover the dashboard only. They never include your calls, recordings of calls, transcripts, or the contents of a campaign.
What you type is masked before it leaves your browser, so passwords, phone numbers, GSTIN and identity numbers are never captured. We do not record network request or response bodies.
Recordings are held by PostHog in the European Union, are kept for a limited period and are then deleted. Our staff may open a recording while investigating a support request; every such access is logged against the staff member who made it. Write to hello@usetone.ai to ask us to stop recording your sessions, or to delete recordings we already hold.
Children
Tone is a business product and is not directed at anyone under 18. We do not knowingly collect data from children.
Changes
If we change this policy in a way that materially affects you we will email account holders before it takes effect. The date at the top is always the current version.
Contact
Bellatech Marketing Pvt. Ltd.
PT2 804, 8th floor, Pinnacle dreams, Nipania, Vijay Nagar, Indore- 452010, Madhya Pradesh
hello@usetone.ai