Security and data
Your customers' data, kept in its lane.
Customer conversations carry personal data all day. Here is how OVOKY separates accounts, limits access and keeps a trail of what changed.
Account isolation
Every record carries an account identifier and every query is scoped to it automatically, with automated tests that check for cross-account access.
Deny-by-default permissions
59 permissions in 16 groups, 3 roles and visibility scopes for own records, team or account.
Encrypted credentials
Stored credentials such as SIP and SMTP passwords are encrypted. API keys have scopes, expiry and IP or domain allowlists.
Sign-in protection
Login lockout per email and IP, IP blocking, idle-session timeouts and token revocation on logout.
Audit trails
Changes to phone numbers are logged, and every e-signature envelope keeps an audit trail chained by hashes.
Web hardening
HTTPS everywhere with HSTS, and a Content Security Policy on the application.
Security questions
Short answers to what teams ask us most. Something else on your mind? Talk to us
OVOKY SAS, 157 Avenue des Minimes, 31200 Toulouse, France. For data protection requests, write to hello@ovoky.io.
Not today. Users sign in with email and password, or with Google. Tell us if you need SSO or two-factor authentication so we can discuss the roadmap.
Only when recording is switched on for a campaign. Recordings are kept on object storage and playable from the contact timeline by users with permission.
We don't claim certifications we don't hold. Ask us for our security documentation and we will answer your questionnaire.
Bring every customer conversation into one place
Calls, SMS, WhatsApp, email and chat in one inbox, on one invoice. Start with one team, then grow.