Calling rules
- Do-Not-Call is checked before every dial
- Local-time calling windows, including windows that cross midnight
- Consent announcements and AI disclosure at the start of the call where required
Trust and security
Controls built for
regulated industries
Voice AI touches phone numbers, recordings and consent rules. These are the controls that sit in the call path, and an honest note on what we don't claim yet.
Caller rights
- Callers can ask for a person at any time
- Data-erasure requests handled with a cancellation window
- AI opt-out register, available on request
Data protection
- Transcripts encrypted with AES-256
- Phone numbers masked in the interface
- Automatic PII redaction in transcripts
- Recording retention you set, with automatic deletion
Oversight and control
- AI kill switch, effective mid-call
- No script change goes live without human approval
- Full prompt version history and rollback
- Weekly persona-drift check and a full audit log
Access security
- Multi-factor authentication
- Role-based access by workspace
- Login lockout and session protection
- Scoped API keys for integrations
Isolation for partners
- A separate workspace per client
- Each client's data kept separate from the others
- Your own brand and domain on the white-label setup
Rules you will hear about, by region
VoiceBridg gives you the controls above. Which rules apply, and how to configure a campaign to meet them, is up to you and your advisers. This is not legal advice.
| Region | Rules to know about |
|---|---|
| United States | TCPA, state call-recording consent rules |
| Canada | CRTC rules, CASL, PIPEDA |
| United Kingdom | UK GDPR, Ofcom, TPS |
| Australia | ACMA, the Do Not Call Register, Privacy Act |
| India | TRAI consent and Do-Not-Disturb rules |
| United Arab Emirates | Responsible-AI expectations for consumer-facing AI, such as human oversight and a way to reach a person |
What we don't claim yet
We don't yet hold a SOC 2 report or a HIPAA attestation. If you need either, tell us before you deploy, and we'll say plainly what we can and can't support today.
Is VoiceBridg compliant with TCPA, CASL or UK GDPR?
VoiceBridg provides the controls these rules ask for: Do-Not-Call checked before every dial, local-time calling windows, consent announcements, recording with an audit trail, data-erasure requests and encrypted transcripts. Whether a campaign is compliant depends on how you configure and use it, and this page is not legal advice.
Does VoiceBridg have a SOC 2 report or HIPAA attestation?
Not yet. If you work in a regulated setting such as US healthcare, tell us your requirements before you deploy and we'll be straight about what we can and can't support today.
Can I stop the AI immediately?
Yes. The AI kill switch stops AI handling across your workspace, including calls already in progress, and routes callers to people.
Who can see call transcripts?
Only people you give access to in your workspace, under role-based permissions. Transcripts are encrypted with AES-256, phone numbers are masked in the interface, and there is an audit log.
Can the AI change itself?
No. A suggested script change waits in your Attention Inbox with the transcript excerpts behind it. Nothing goes live until you approve it.
Talk to us about your requirements
We'll walk your risk and compliance team through the controls on a live demo.