Consent

Your telecaller asks for consent. Auratel does not.

Recording a business call is normal and lawful in India in the ordinary case, provided the other person is told and agrees. That telling happens out loud, on the call, in your telecaller’s own words. Auratel records what was said after that; it does not obtain consent for you, and it would be dishonest of us to let you think otherwise.

Who obtains consent, concretely

One person, at one moment, in words the customer can answer.

The telecaller says it at the start of the call

Before the conversation gets going, your telecaller states that the call is being recorded, says why, and waits for the customer to agree. In practice that is one sentence and a pause. Something like: “This call is recorded for quality and order accuracy. Is that alright?” Then they wait for the answer, because a question nobody answered is not consent.

If the customer says no

Your telecaller ends the recording arrangement the only way available to them: by not making the call on an enrolled handset, or by ending it. Auratel has no per-call switch that a telecaller can throw mid-conversation, and we would rather state that than imply a control that is not there. If refusals are common in your business, tell us before you buy and we will say honestly whether this fits.

Proving it later is your record, not ours

Under the DPDP Act the business making the call is the Data Fiduciary, which means the duty to obtain consent and to be able to evidence it sits with you. The recording itself usually carries the asking, because the telecaller said it on the call that was recorded. That is a by-product, not a consent ledger, and we do not market it as one.

What Auratel does not do

Listed because a gap you discover after paying is worse than one you read about first.

It does not read a notice to your customer. There is no spoken announcement, in any language. The platform has a configuration value for one; the handset has no code behind it, so it does not exist.
It does not ask for consent, and it does not record the customer’s answer. Nothing in Auratel captures the customer’s yes or no as a field you can filter or report on. There is no consent column on a call, and no record that anybody agreed.
It does not refuse a call for want of consent. Capture is a handset setting, not a per-call decision the software makes.
It does not tell your staff for you. Recording your own telecallers’ voices is also personal data, and that conversation is one you have with them.

Two mechanisms that do exist, and neither of them is consent

A courtesy beep on one capture path. On handsets where Auratel has to record through the microphone instead of reading the dialer’s own file, the app can play a short beep into the call when capture starts. It is a handset setting, it is audible notice at best, and it does not run on the main capture path at all. Your telecaller still has to say the sentence.

A check on whether your telecaller said it. The call analysis records, per call, whether the recording was disclosed, and the console reports it as a percentage for each telecaller alongside the other quality criteria. That is there so you can supervise your own floor: it tells you whether your people are doing what you told them to do.

Read what that is carefully. It is a judgement made by a language model reading a transcript, so it is an indicator and not evidence. It describes what your telecaller said, never what your customer agreed to. It does not make us a party to the consent, it is not a compliance certificate, and it must not be the only thing you rely on if a disclosure is ever disputed.

Built for India's DPDP Act

The mechanisms, each one checkable, and which of us they belong to.

Auratel is built to meet the Digital Personal Data Protection Act, 2023, and the split of duties it sets out. You are the Data Fiduciary: the calls are yours, the customers are yours, and the consent is yours to obtain. Auratel is the Data Processor: we process those recordings on your instructions and for nothing else. That division is written into the data processing agreement, not just described here.

What we provide, as mechanisms

Your data stays in India. The database runs on our own servers in Mumbai. It moved off managed infrastructure in Seoul on 24 September 2026. If you have a residency requirement, this satisfies it.
Isolation enforced by the database. Every table carrying your data is under Postgres row-level security, on a role with no permission to bypass it. A bug in a query cannot return another company’s rows.
A retention window you set. Recordings are deleted when your workspace’s retention period runs out, 90 days by default, by a scheduled job rather than by someone remembering.
Erasure on request, with a receipt. Erasing a call removes the audio, the transcript, the extracted fields, the lead and the CRM delivery record, and writes you a signed receipt. That is what answering a customer’s erasure request actually needs.
An access trail. Reads of your call data are written to an audit log you can read.
A named sub-processor list. Published on how Auratel handles your data, including the one that is not in India.

We take no part in obtaining consent

Auratel is not involved in asking your customer, is not a party to the conversation in which you ask, and carries no responsibility for whether you did. Obtaining consent on the call, and any consequence of not obtaining it, rests with the business making the call. That is not a stance we invented for this page: it is the position our terms of service set out, and the Data Fiduciary duty the Act itself assigns to you.

What stays yours

Saying it on the call. Consent is spoken, by your telecaller, and agreed to by the customer before the conversation proceeds.
Being able to show you did.
Giving your customers the notice the Act requires, in a language they understand.
Telling your own employees that their calls are recorded.
Having a lawful purpose and keeping to it. Recordings collected to improve sales quality should be used for that.
Passing on an erasure or access request, which we then help you execute.

What Auratel cannot record

Stated here so it is never a surprise later.

WhatsApp, Telegram, Signal and other internet calls cannot be recorded. Android gives the messaging app exclusive use of the microphone for the duration of the call, so any recorder receives silence. This is an operating system restriction, we confirmed it on hardware, and no product can work around it. We capture the metadata of those calls, not the audio.

Handsets running the Google Dialer (Pixel, Motorola, Nokia) cannot be used for capture at all. See phone compatibility.

This is not legal advice

We build software, not legal opinions. India’s DPDP Act and the rules under it are still being operationalised, and what applies to you depends on your business, your sector and who you call. If call recording is material to how you operate, get advice from someone qualified to give it.

What we can tell you is exactly what the software does and does not do, which is what this page is for. If something here is unclear, ask. We would rather answer it now than have you find out later.