Safety and consent
The controls we operate, and the ones we don't claim
Four controls, and how each one works
Consent is a gate, not a setting
Two confirmations are required before any clone runs: that you have the right to use the recording, and that you will not use the result to impersonate anyone. Both are stored against your account with a timestamp, and the server re-validates them independently of the interface. There is no path — through the app or otherwise — that creates a voice without them.
Submitted clips are screened
Reference recordings are checked against known voices before a voice is approved for use. Matches are held for human review rather than auto-approved or auto-rejected, and reviewed voices can be disabled. Cloning public figures is not permitted regardless of stated intent.
You can delete voices and your account
Cloned voices can be deleted individually from the voices screen, which removes the associated reference recording. Deleting your account removes your voices, recordings and generation history. Retention periods and the legal basis for anything we keep are set out in the privacy policy.
There is a real route to report misuse
A monitored grievance address (grievance@bimbient.com) is in the footer of every page, and reports are reviewed by a person. Include the audio or a link, timestamps and any account details you have — reports with evidence are actionable; reports without it usually are not.
What we will not claim
Every safeguard above has limits, and stating them is the only way the rest of this page is worth reading.
- Screening is not perfect.Voice matching reduces the chance that a well-known voice is cloned here. It does not guarantee it, and it cannot detect a private individual’s voice being used without permission.
- A consent checkbox is an assertion, not proof. It records who claimed the right and when, which makes accountability possible after the fact. It does not verify the claim at the time it is made.
- Watermarking is not a universal detector. It provides provenance for audio generated here. It says nothing about audio generated elsewhere, and no watermark survives every possible transformation.
- We cannot claim India-only data residency. The app plane runs in an India region, but generation may involve providers processing data outside India. We disclose that rather than making a cleaner claim that would be false.
- We are not a fraud-detection service. If you have received a suspicious call, the useful response is verification through a second channel — see protecting your voice from cloning.
If someone has cloned your voice
You do not need an account here to report it. Email grievance@bimbient.com with the audio or a link to it, timestamps, and anything you know about where it was published. Preserve the evidence before reporting elsewhere — content usually disappears once a platform acts on it.
If audio was generated on Mayantar, we can act on the account behind it. If it was not, we will say so rather than leave you waiting, and the steps in this guide are the fastest route to a result.
Who operates this service
Mayantar is operated by Horanadu Corporation Pvt. Ltd., registered in Lucknow, Uttar Pradesh, India. Legal enquiries go to legal@bimbient.com, privacy enquiries to privacy@bimbient.com, and grievances to grievance@bimbient.com.
The binding documents are the terms, the privacy policy and the acceptable use policy. Where this page and those documents differ, those documents govern.
Frequently asked questions
Is AI voice cloning safe to use?
Cloning your own voice for your own content is low-risk. The risk in voice cloning is impersonation of other people, which is why platform controls matter: consent capture, screening of submitted recordings, watermarking of output, and a working abuse route. Judge any provider on whether it can answer those four questions plainly.
Is generated audio watermarked?
Yes. Generated audio carries an inaudible watermark, and free-tier output is watermarked as a condition of the tier. We keep model watermarks rather than stripping them, because provenance signals are the main practical defence against synthetic-voice fraud.
Can I clone a friend's or colleague's voice?
Only with their permission, which you are asked to confirm at the point of cloning. Get it in writing and keep it: the confirmation records that you asserted permission, it does not create permission. Their recording is their personal data and they retain rights over it, including withdrawal.
What happens to my reference recording?
It is stored so the voice you cloned remains usable, and it is screened as described above. Deleting the voice deletes the recording. Full retention detail is in the privacy policy.
Where is my data processed?
The app plane runs in an India region, but generation providers may process voice samples and scripts outside India. We disclose this rather than claiming India-only residency, because the claim would not be true. The privacy policy sets out the detail.
What do you prohibit outright?
Cloning public figures, impersonation, fraud, non-consensual cloning, and content that is unlawful in India. The full list is in the acceptable use policy, and enforcement includes disabling voices and terminating accounts.
Keep reading
Clone your own voice, properly
Consent recorded, output watermarked, deletion in your hands. Start on the free tier.