1. When this applies
These terms apply whenever Revvox handles personal information on your behalf — which is most of what the product does. They form part of our terms of service. Where they conflict with the main terms on a data-protection question, these terms win.
2. Who is who
For the information about the people your ads generate — the leads we call — you are the controller and we are the processor. You decide those people are contacted and what is asked; we carry it out on your instruction.
If you are an agency acting for a client, you confirm you have your client’s authority to give us those instructions, and that your client understands an automated caller will be phoning their leads.
For information about your own staff and account, we are the controller — see our privacy policy.
3. What we process, and why
| Subject matter | Contacting, qualifying and booking the leads your advertising generates, and reporting outcomes back to the advertising platforms you connect |
| Duration | For as long as your account is open, plus the retention periods in our privacy policy |
| Nature and purpose | Placing telephone calls, recording and transcribing calls, extracting answers, scoring them against your rules, storing the result, and sending conversion reports |
| Types of personal information | Name, telephone number, email address, postal area, the answers given on the call, call audio and transcript, and the permission record attached to the lead |
| Categories of people | Members of the public who submitted an enquiry to you or your client |
| Special category data | Not requested and not required. If your questions could elicit it — health, finances, or similar — tell us before you go live so it can be handled properly. |
4. Acting on your instructions
We process personal information only on your documented instructions, which includes your configuration of the product. If we believe an instruction breaks the law, we will tell you rather than carry it out. We will not sell it or share it for advertising purposes.
5. Our people
Everyone at Revvox who can reach customer data is bound by confidentiality, and access is limited to those who need it to do their job. Access is logged.
6. Security
We maintain measures appropriate to the risk, including:
- Encryption in transit (TLS). Encryption at rest provided by our database and object-storage providers, and application-level encryption (AES-256-GCM) of the access tokens for your connected ad accounts and CRMs.
- Role-based access, so salespeople see leads and calls but never billing or connection keys
- An audit record of logins, exports and setting changes
- Separation of each customer’s data, with no pooling between accounts
- Encrypted database backups, kept off the database server, and a written process for restoring them
We hold no third-party security certification (such as SOC 2 or ISO 27001) yet, and no independent penetration test has been done yet. We will update this section when that changes. More detail is on our security page.
7. Sub-processors
You give general authorisation for us to use sub-processors in the categories below (list last updated 29 October 2026; also published at /legal/subprocessors). On request, before you sign up or at any time after, we give you the name, location and role of each sub-processor in each category. We impose data-protection obligations on each of them no weaker than these, and we remain responsible to you for what they do.
| Category | Purpose | Data | Region |
|---|---|---|---|
| Cloud hosting and file storage | Servers that run the Revvox API, call gateway and workers, and store files (interview videos, voice samples, uploads, ID photos); encrypted backups | Everything the service processes passes through these servers | India (Bengaluru) |
| Database | Primary database | Account, workspace, lead, contact, call, chat and billing records | India (Mumbai) |
| Website and app hosting | Serves this website and the Revvox web app | IP address, pages requested, and the app traffic passing to our API | Global edge; app functions in India (Mumbai) |
| Voice AI | Runs the voice agent: speech recognition, speech synthesis, the call's language model, and call recordings | Call audio, transcripts, the phone number dialled, the lead or candidate details the agent needs on the call | United States |
| AI language models | Website and messaging chat replies, call analysis and summaries, reading uploaded documents, drafting agents, chatbots and workflows, and the in-app assistant | Chat messages, transcripts, extracted answers, documents and descriptions you send, the context needed to answer | United States |
| Telephony carriers | Phone numbers, placing and carrying calls | Phone numbers, call audio in transit, call metadata | Global |
| Payments: merchant of record | Takes payment, issues invoices, handles tax and refunds | Billing name, email, country, tax ID if given, what was bought; card and UPI details go to the payment provider, never to us | Global |
| Transactional email | Account emails: sign-in codes, verification, password reset, invitations, receipts and notices | Recipient email address, the email's content, delivery and bounce events | Outside India (Japan sending region) |
| Feature switches and product analytics | Feature switches for every workspace; product analytics in the app only for people who say yes to it | Workspace ID and which features are on; for those who agreed, pages and buttons used (never what you type) | European Union |
| Early-access sign-ups | A private spreadsheet that stores the website's early-access form | What you type into the early-access form | Global |
| Sign-in provider you choose (only if chosen or switched on) | Lets you sign in with an account you already have, only if you choose it | Name, email and profile photo it shares at sign-in; for Experts interviewers, their professional headline too | Global |
| Bot protection (only if chosen or switched on) | A bot check on sign-up and website chat, when switched on | IP address and browser signals during the check | Global |
| Video rooms and shared code pad | The video room and the shared code pad for Experts interview rounds | Audio and video of the round, display names, code typed during the round | Global |
Apps you connect (stores, CRMs, team chat, messaging channels, calendars, ad platforms for lead forms and conversion events, your own phone numbers) receive only what you choose to sync, under your own agreement with them.
The names of our sub-processors are given to customers under our data processing agreement. Email hello@revvox.io for the current list. We tell customers 30 days before adding or replacing a sub-processor, and they can object.
You will get notice before we add or replace a sub-processor: 30 days’ notice, by email to the account owner. If you reasonably object on data-protection grounds, you may terminate the affected part of the service without penalty.
8. Helping you meet your obligations
We will help you, at your cost where the effort is significant, with:
- Requests from people to see, correct, delete or export their information
- Data-protection impact assessments and prior consultations
- Producing the permission and blocked-call evidence a regulator or a court might ask for — this exports as a file rather than requiring you to ask us to compile it
9. If something goes wrong
If personal information we hold for you is breached, we will tell you without undue delay and in any event within 72 hours of becoming aware, with what we know, what we are doing, and what you may need to do. We will not make a public statement identifying you without talking to you first, unless the law requires it.
10. Return and deletion
On termination you can export everything. After the export window in our terms, we delete it, except where the law requires us to keep something — and permission and do-not-call records, which we keep for longer on purpose because deleting them would destroy the evidence that a call was allowed.
11. Audits
We will make available the information needed to show we are meeting these terms, and will allow an audit by you or an auditor you appoint, no more than once a year unless a regulator requires otherwise, on reasonable notice and without disrupting other customers.
12. International transfers
Our servers and stored files run in India (Bengaluru) and our database in India (Mumbai). Call recordings are held by our voice AI provider in the United States, and AI language models run in the United States. Some other sub-processors in section 7 process data outside India, mainly in the United States; the table shows which. Where personal information is transferred to another country, we put the safeguards required by law in place for that transfer, such as standard contractual clauses where those apply.
© 2026 Revvox OS. Revvox is pre-launch. This document describes how the service is built to operate and the commitments we are prepared to make in writing. Privacy · Terms