Data encryption
All traffic to BookifyCall uses HTTPS (TLS 1.2 or newer). Plain HTTP requests are redirected to HTTPS, and browsers are told to use HTTPS only.
Call recordings, uploaded files and our daily database backups are stored in Amazon S3 with server-side encryption. That storage refuses connections that aren’t encrypted.
The most sensitive values are also encrypted one by one with AES-256-GCM before they’re saved: sign-in tokens for the calendars and apps you connect, webhook signing secrets, credentials for custom tools and your two-factor secret.
Passwords are stored only as bcrypt hashes. API keys are stored as one-way hashes, so you see a full key once, when you create it.
Accounts and access
- Two-factor authentication with an authenticator app, plus 10 single-use recovery codes.
- Sign-in attempts are rate limited, and a code from your authenticator app works only once.
- Settings → Security lists the devices where you’re signed in. You can sign out one device, or every device except the one you’re using.
- Changing your password signs out your other devices. We email you when your password changes and when two-factor authentication is turned on or off.
Roles and permissions
Each person on your team has one of five roles: owner, admin, manager, member or viewer. Only owners and admins manage the team, integrations, webhooks and API keys, and only they can delete recordings. Viewers can read calls but can’t play recordings. You can limit managers, members and viewers to specific AI receptionists, for example one location; they then see only those receptionists’ calls, leads and appointments, plus items not tied to any receptionist. Role changes and removals take effect right away.
Our staff
BookifyCall staff accounts need two-factor authentication. Without it, staff permissions don’t apply.
If our support team needs to see your account as you see it to help with a problem, they open a view-only session. It needs a stated reason, can’t change anything, ends after 30 minutes at most and is recorded in our audit log. You’re told by email and in the app, with the staff member’s name and the reason.
Call recordings and transcripts
Recording is a setting on each AI receptionist. When a call is recorded, your AI receptionist starts with a short notice, such as “This call may be recorded for quality.”, in its own language. You can change the wording or turn the notice off. Some states and countries require every person on a call to agree to recording, so check your local law before you turn it off.
- Who can listen. Owners, admins, managers and members can play recordings; viewers can’t. People limited to certain AI receptionists hear only those calls. Recordings play through private links that expire after an hour.
- Where they’re kept. After a call, the recording is copied to our encrypted storage and the copy at Twilio is deleted.
- How long. Recordings are kept until an owner or admin deletes one. A daily job then removes the audio from storage. Call details and transcripts are deleted automatically once a call is a year old. A call that still has a recording keeps its details and transcript until the recording is deleted; after that, the same one-year rule applies.
Sub-processors
These services process data for us so BookifyCall can work.
| Service | What it does | Data it handles |
|---|---|---|
| Twilio | Phone numbers, phone calls and call recording | Call audio, phone numbers and call details |
| OpenAI | The AI voice on calls, transcripts, call summaries and call analysis | Call audio and transcripts, and the business details your AI receptionist uses |
| ElevenLabs | AI voices and voice conversations on calls, and custom voices | Call audio and transcripts, and voice samples you upload |
| Amazon Web Services (AWS) | Hosting and file storage, in the United States | The data stored in BookifyCall, including recordings and backups |
| Stripe | Payments, subscriptions and invoices | Billing name, email and card details (entered on Stripe’s pages) |
| Our email delivery provider | Account and notification emails, such as call summaries | Email addresses and the content of those emails |
| Google Calendar, only when you connect it | Calendar availability and the appointments your AI receptionist books | |
| Microsoft | Outlook and Microsoft 365 calendars, only when you connect one | Calendar availability and the appointments your AI receptionist books |
Other apps you connect in Settings receive only what you choose to send them.
Payments
Payments run through Stripe Checkout and Stripe’s billing portal. You enter card details on Stripe’s pages, so we never see or store your card number.
Reporting a security issue
If you think you’ve found a security problem in BookifyCall, email support@bookifycall.com with “Security” in the subject and the steps to reproduce it. Please don’t access other people’s data, disrupt the service or share the issue publicly before we’ve fixed it.
For IT and security reviews
- Where data lives. BookifyCall runs on Amazon Web Services in the United States, including recordings and backups.
- Separation. Every request is limited to your organization’s data, and people limited to certain AI receptionists see only those.
- Retention. Recordings are kept until you delete them; call details and transcripts are deleted after a year (see Call recordings above).
If your company needs a security questionnaire answered, email support@bookifycall.com with “Security review” in the subject. We answer plainly, including where we don’t meet a requirement.
What we don’t claim
- We don’t hold SOC 2 or ISO 27001 certification.
- BookifyCall is not designed for patient health information.
- We don’t publish an uptime guarantee.