1.Who we are, and who this covers#
Vaakini is a text-to-speech service for voice agents, operated by Oggnai Technologies Private Limited (CIN U62011DL2025PTC446040), 293 S/F, Western Marg, Saidulajab, New Delhi, Delhi 110030, India (“we”, “us”). This policy covers the website and dashboard at vaakini.com and app.vaakini.com, and the API at api.vaakini.com.
Two groups of people appear in it:
- Customers: the people and organisations with an account. For their account data we are the controller.
- End users: the people whose words a customer’s agent speaks through the Service, and the speakers whose recordings a customer uploads to make a custom voice. For their data we are a processor acting on the customer’s instructions, and the customer’s own privacy notice governs it.
2.What we collect#
Account data. Sign-in is with Google. We keep your email address, your name and your Google account identifier. There is no password.
Org data. Your org’s name, who belongs to it, and for each API key its name, its first characters, a one-way hash and an encrypted copy, so that members of the org who can edit it can show the key again in the dashboard.
Text and audio. The text your agent sends is split into sentences and sent to our own GPU server, which synthesizes each sentence in memory and keeps neither the text nor the audio. The audio is streamed to you and is not stored.
Custom voices. If we have enabled custom voices for your org, each voice you create keeps its name, the reference recording you upload, its transcript and its language. The recording is a real person’s voice, so we treat it as that person’s personal data.
Technical data. Our servers log request metadata: your org, the model, sizes, timings, errors, and IP addresses. They never log sentence text or API keys. We also keep aggregate operational metrics, such as how many characters each org spoke.
Billing data. Your org’s credit balance and its history: the free credit, each purchase and refund with its amount and Razorpay’s identifiers, and the characters spoken each day.
Billing details. The details your org’s GST invoices are made out to: a legal name, a state, an invoice email, and a GSTIN and address if you give them. Each purchase keeps a copy of them as they were, with its amounts, Razorpay’s order and payment identifiers and its invoice. You pay in Razorpay’s own checkout, so your card, UPI or bank details go to Razorpay, never to us. We pass Razorpay your org’s identifier and your name and email address.
3.What we use it for#
- Running the Service: authenticating your requests, synthesizing speech, and showing you your org.
- Security, debugging and abuse investigation.
- Support, when you ask for it, one welcome email when you create an account, and messages about changes that affect your account.
We do not sell your data, and we do not use your text or audio to train models. This site and the dashboard load no analytics or advertising script.
4.Who else sees it#
Where speech is synthesized
We run the text-to-speech model ourselves; no third-party speech provider receives your text. Each sentence goes from our API servers to our own GPU server, hosted by CloudPe in Mumbai, India, over an encrypted connection only our own servers can use. The server synthesizes the sentence in memory and returns the audio; it stores neither, and its logs record lengths and the voice, never the text. The same server holds your org’s custom voices, each with its recording and transcript, so it can speak in them.
Our sub-processors
| Sub-processor | What they do for us |
|---|---|
| Cloudflare | Hosting for this website, the dashboard and the docs (Cloudflare Pages), and DNS for vaakini.com |
| Amazon Web Services | Hosting, in Mumbai, India: the servers and database that run the Service, and the storage that holds custom voices' recordings |
| CloudPe | Hosting, in Mumbai, India: the GPU server that synthesizes speech and holds custom voices |
| Sign-in, and the mailbox that receives support and privacy requests | |
| Resend | Sending the welcome email when you create an account, and the GST invoices for purchases |
Razorpay
Credit is paid for through Razorpay, our payment gateway. Razorpay runs the checkout, takes the payment and processes refunds, and keeps the payment details you give it under its own privacy policy. It sends us confirmation of each payment and refund, with the amount and the order it was for. We issue the GST invoice ourselves and email it to you through Resend.
We disclose data outside these lists only where the law requires it, or to protect the rights and safety of our users, and we will tell you unless we are legally barred from doing so.
5.Where your data lives#
The Service runs on Amazon Web Services in Mumbai, India. Account and org data, the metrics, the logs and custom voices’ recordings are all there. Speech is synthesized on our GPU server in Mumbai, India, which also holds a copy of each custom voice’s recording and transcript.
If you use the Service from outside India, your account data and the text you send are transferred to India to be processed there. For transfers to our sub-processors we rely on the standard contractual clauses in their terms.
6.How long we keep it#
| What | How long |
|---|---|
| Text you send, and its audio | Not stored: our GPU server holds a sentence in memory only while it synthesizes it, and the audio is streamed to you and not kept |
| Custom voices | Until you delete the voice, or your org is erased with your account (below). A deleted voice can't be used from that moment, and its recording and transcript are then deleted from our storage and our GPU server. |
| API keys | The hash and the encrypted copy are deleted the moment you delete the key |
| Sign-in sessions | 30 days, or until you sign out |
| Credit balance and history | As long as the org exists: until it is erased with your account (below). Razorpay keeps its own payment records as the law requires. |
| Purchases and their GST invoices | As long as Indian tax law requires us to keep them (currently eight years), even after the org is erased |
| Account and org data | Until you ask us to delete it |
| Server logs | Short-lived and rotated |
7.How it is protected#
- Traffic between your agent, your browser and the Service is encrypted with TLS.
- API keys are checked against one-way hashes; the copy kept for showing a key again is encrypted with AES-256-GCM and bound to its org.
- Custom voices’ recordings are in a private storage bucket that blocks all public access, encrypted at rest; only our control plane can read them.
- A custom voice can be spoken only by the org that made it.
- The database accepts connections only from inside our private network.
- Our GPU server accepts requests only from our own servers, over TLS, with secret tokens; only our control plane’s token can add or remove custom voices.
If you need something in writing for a procurement review, ask us at [email protected]. If we discover a breach affecting your data, we will tell you and the relevant regulator as the law requires.
8.Your rights#
If you hold an account. Depending on where you live, you may have the right to access, correct, delete or export your data, to object to processing, or to withdraw consent. Write to [email protected]; we will respond within 30 days.
If an agent built on the Service spoke to you, or a custom voice was made from your recording. Your rights are against the business that runs the agent or made the voice; contact them first. If you can’t reach them, write to [email protected] and we will pass the request on.
You may complain to your data protection authority. In India, that is the Data Protection Board.
9.Cookies#
We set these cookies, all sent only over HTTPS and all but vk_signed_in HTTP-only:
vk_sessionkeeps you signed in to the dashboard for up to 30 days. It is sent only to api.vaakini.com.vk_signed_inis set alongside it on vaakini.com and its subdomains, and lasts exactly as long. It holds no identity, only the fact that this browser is signed in, and is used only to take you from our home, log-in and sign-up pages straight to the dashboard.vk_oauthlives for 10 minutes while you sign in with Google, to check that the sign-in you finish is the one you started.
We set no other cookies, and this site loads no third-party script, except Razorpay’s checkout when you buy credit, which may set Razorpay’s own. Fonts are served from our own domain.
10.Google user data#
Our use of information received from Google APIs adheres to the Google API Services User Data Policy. We request only the openid, email and profile scopes, and use them only to sign you in, show you your name and email, and email you about your account.
11.Children#
The Service is a business product and is not directed at children. We do not knowingly collect data from anyone under 18. If you believe a child has given us data, write to [email protected] and we will delete it.
12.Changes to this policy#
We update this page when what we do changes, and revise the date at the top. If a change materially affects how we handle your data, we will tell account holders by email or in the dashboard before it takes effect.
13.Contact#
For a question, an access or deletion request, or a complaint, write to [email protected]. Under India’s data protection rules, that address also reaches our grievance officer.
Oggnai Technologies Private Limited
293 S/F, Western Marg, Saidulajab, New Delhi, Delhi 110030, India
CIN U62011DL2025PTC446040
[email protected]
+91 99101 80529