Trust and compliance
What Vaani will and will not do
These are rules the product enforces. They are not settings a workspace can turn off, unless this page says so.
Vaani refuses cold promotional calls
A promotional campaign dials a person only when your workspace holds that person’s recorded consent, a registered DLT entity id and a 140-series caller number, the do-not-disturb result for the number is fresh, and the time is between 09:00 and 21:00.
If any one of these is missing, the call is refused and the refusal is logged with its reason.
The agent says it is an AI, and says when a call is recorded
An agent that makes outbound calls cannot be published unless it says it is an AI. An agent whose calls are recorded cannot be published without the recording notice.
By default Vaani speaks your disclosure text before the agent’s first message.
Calling hours are a hard limit
Promotional calls are placed only between 09:00 and 21:00. Service calls follow the calling windows and holidays your workspace sets.
Vaani does not scrub the do-not-disturb registry for you
Your workspace exports its numbers, scrubs them on its own DLT portal and imports the result. Vaani enforces the result. It contacts no registry and no carrier.
Everything that reaches a telephone or an inbox is off by default
Outbound calling, campaigns that dial and consent emails are each switched on per workspace, by us, after we have checked who the business is. Paying for a plan does not switch them on.
Two people
A campaign is approved by someone other than the person who wrote or last edited it. A workspace with a single admin can waive this; the waiver is a setting, it is off by default, and each self-approval is recorded.
Complaints stop campaigns
A complaint puts the number on the do-not-call list and pauses every running campaign that has that person on its list. Complaints from three different numbers in ten days put every promotional campaign on hold.
Saying no is easy and takes effect at once
A person who gives consent on a Vaani consent page is given a link that withdraws it, in one step.
When a person asks on a call not to be called again, every number of that contact goes on the do-not-call list and their place in every campaign is closed.
Where data is
The Vaani database, with its backups, runs in Google Cloud’s Mumbai region.
The speech-to-text, language-model, voice and telephony vendors a workspace connects handle call audio and text while a call runs, and may hold recordings. Some of them process data outside India. Which vendors those are is the workspace’s choice.
Each workspace is separate, in the database itself
One workspace’s data is kept from another’s by the database’s own row-level rules, as well as by the application. Asking for another workspace’s record by its id answers “not found”.
Access by role, and a record of every access
What a person can see and do follows their role. Transcripts and recordings each need their own permission, apart from seeing the call list.
Sign-ins, changes, exports and every opening of a transcript or a recording are written to an audit log that cannot be edited.
Vendor keys are encrypted and can be set and tested, never read back.
What Vaani is not
Vaani is not a legal adviser. Your business remains the caller of record and answers for its own consent records and registrations. Vaani enforces the rules above; it does not replace your own compliance review.
What we do not claim
Vaani is new. We publish no accuracy, speed or uptime figures, because we have not measured them yet. Vaani holds no third-party security certification today. When either changes, this page will say so.
Questions, or a call you did not want
Write to us. If a Vaani agent called you and you want it to stop, tell us the number that was called and we will pass it to the business that made the call.
- Email support@aeonx.digital
- Phone +91 79 6548 0527
See Vaani on the calls you run
Tell us what your calls are for. We will show you an agent built around them.