Security and calling controls
Tested. Trusted. Calls that follow the rules. Data that stays yours.
What runs today and what is not in place yet, in plain words. Every call carries an opt-out and goes out only inside the calling hours you allow. You stay responsible for consent on your own forms. The legal detail is in our DPA, privacy policy and sub-processor list. Hiring with Dial? How applicants are treated: trust and data.
Calling
Calling, checked in code.
Each item marked Live or Shipping next.
Calling hoursLive
Calls go out only inside the hours and days set for the workspace, in the local time of the person called. The rule runs in code on every dial; outside it the call waits.
Caller IDLive
Calls go out on real numbers from our telephony carrier
AttemptsLive
Two attempts at most. Retries stop the moment someone picks up.
Destination controlsLive
Only domestic numbers in the allowed ranges are ever dialled: no international, premium-rate or short-code numbers, with hourly and daily call ceilings
Consent before diallingLive
Consent and opt-out are checked before every call; a person who has opted out is never dialled
Hiring questionsLive
Screening calls never ask about religion, caste, gender, marital status or health, and ask age only to confirm 18 or over
Do-not-call registry checksShipping next
Each number checked against the national do-not-call registry before it is dialled, from the product
Data
Data, checked in code.
Each item marked Live or Shipping next.
EncryptionLive
TLS in transit. At rest by our database and object-storage providers.
Connected accountsLive
Ad account and CRM access tokens encrypted with AES-256-GCM
Phone numbersLive
Stored encrypted (AES-256-GCM) and matched through a keyed one-way index; screens show them masked unless your role allows the full number
Tenant isolationLive
Every record is scoped to its workspace; one customer's data is never pooled with another's
Media linksLive
Recordings and files open through signed links that expire after a short time
Deletion on requestLive
A person's data is erased from our systems, and the voice provider's copies of their calls deleted, on request
Access
Access, checked in code.
Each item marked Live or Shipping next.
PasswordsLive
Stored only as scrypt hashes, never in plain text
Two-step sign-inLive
Authenticator-app codes with one-time recovery codes; an owner can require it for the whole workspace
Sign-in protectionLive
Sign-in attempts are rate limited, and repeated wrong passwords lock the address for a while
SessionsLive
Signing out ends the session on our side; you can see and end your other sessions
Our staff's accessLive
Revvox staff cannot open your workspace without a time-limited grant with a stated reason, which appears in your own audit log; you can require your approval first. Staff accounts must use two-step sign-in.
Role-based accessLive
Salespeople see leads and calls, never billing or connection keys
Audit logLive
Logins, exports and setting changes are logged
Webhook signaturesLive
Inbound webhooks from ad platforms, messaging channels, the voice provider, the telephony carrier and the payment provider are verified before use
Not yet in place
What we don't have yet.
Named here before you have to ask.
SOC 2 or ISO 27001Not yet
No certification yet. It will be named here when we have one.
Independent penetration testNot yet
Not done yet.
Where data lives
Storage and suppliers.
Every kind of supplier listed.
Storage
Servers and files in Bengaluru, India; the database in Mumbai, India; call recordings with our voice AI provider in the United States.Sub-processors
Every kind of supplier, what it sees and where it runs: sub-processor list. Customers get the names on request.
Report a vulnerability
Found something?
Tell us first, and we will fix it.
How to report
Email hello@revvox.io with “Security” in the subject, the steps to reproduce and what you could reach. We acknowledge every report and tell you when it is fixed.Please
Test only against your own account, do not read, change or delete other people’s data, do not place calls to real numbers, and give us a reasonable time to fix before you publish. We do not run a paid bug bounty.Machine-readable