Privacy Policy

_Last updated 6 August 2026_

This covers the Dvaarik Voice API developer platform. It is written from what the system actually does, and every claim below is a description of running code rather than an intention.

The short version

We do not store your prompts, your audio, or your transcripts. They pass through memory for the duration of a call and are gone. What we keep is the account you created and the metadata needed to bill you correctly.

What we hold

Your account — name, email address, company name if you gave one, a one-way hash of your password (never the password itself), and the date and version of the terms you accepted.

Your wallet — balance, lifetime top-ups, and one row per credit or debit so the statement adds up.

Call metadata, one row per call — voice grade, language, voice, sample rates, start and end time, duration, the rate applied, the cost, why the call ended, and any metadata you attached yourself. Note the last one: the metadata field on a call is stored verbatim, so do not put anything in it you would not want retained.

Carrier connections, if you create one — the credentials for your own telephony account, encrypted at rest, and never returned by any endpoint once saved. Not even to you: to change them you replace them.

What we do not hold

• Your system prompt. It is held in Redis with a short expiry so the socket can pick it up, and it is never written to the database.
• Call audio. Neither direction. Nothing is recorded and nothing is written to disk.
• Transcripts. They are streamed to you live as the call runs, and we keep no copy.
• Your card. Payments go through Razorpay's own checkout. We receive an order reference and a signed confirmation; the card never touches our servers.

Who else sees your data

Running a voice call means sending audio and text to the providers who do speech recognition, language modelling and speech synthesis. Audio and text reach them for the duration of the call under their own terms. We deliberately do not publish which providers these are — it is commercially sensitive — and we will tell you under NDA if you need it for your own compliance review.

Also involved: Razorpay (payments), Resend (the emails we send you), Railway (hosting, India-region), and Sentry (error reports, which can contain a request path and a user id but not prompts or audio).

We do not sell your data, and we do not share it for advertising.

How long we keep it

• Account and wallet records: while the account is open, then up to 7 years where accounting law requires it.
• Call metadata: 24 months, then deleted.
• Prompts, audio, transcripts: not retained at all.

Training

Your prompts, audio and transcripts are not used to train any model, ours or anyone else's.

Your choices

Write to dev@dvaarik.com to get a copy of what we hold about you, correct it, close your account and have the personal data deleted, or object to how we are handling something. We will respond within 30 days.

Closing the account deletes the personal data. Billing records are kept where the law requires, with the personal fields reduced to what an audit needs.

Security

Passwords are hashed with bcrypt. Carrier credentials are encrypted at rest with a key held outside the database. All traffic is TLS. API keys are stored only as hashes — this is why we can show you a key exactly once and never again.

Every query in the platform is scoped to the account that owns the data, so one developer's calls, keys and connections are not reachable from another developer's session.

Cookies

The console keeps your login token in your browser's local storage. There are no advertising or analytics cookies on this site.

Changes

Material changes will be emailed to the address on your account before they take effect.

Contact

dev@dvaarik.com — Dvaarik AI, Hyderabad, Telangana, India.