Who can read a conversation.
Your customers are trusting you with their messages; you are trusting us. Here is exactly how that trust is handled — in plain words, not badges.
Encryption at rest
Every connection to Bzzip is encrypted in transit. Passwords are stored only as hashes. The access tokens Meta issues when you connect through Meta, and any AI key you bring, are encrypted at rest.
Who sees which workspace
Every business's data is separated from every other's. Inside your business, admins and managers see all your workspaces; everyone else sees only the workspaces they are assigned to.
How your channels connect
A WhatsApp number connects through Meta's Cloud API or by QR code, the way WhatsApp Web does; the QR method is not approved by Meta. Instagram connects through Unipile, a method Meta has not approved either. Either way, Bzzip sends the platform nothing beyond what delivering your messages requires.
Data residency
Production data is stored on our servers in Helsinki, Finland, in the European Union. We follow the LGPD for Brazil and the GDPR for the EU; a copy or deletion of your data is yours to ask for at privacy@bzzip.com.
Who can read a conversation
The people in your business who can see that workspace. Not other businesses. A small number of Bzzip staff can reach production systems to run and support the service, and use that access only for that.
Your AI key
A bring-your-own key is used only for your workspace's AI Agent — its replies, drafts and tests — is encrypted, never shown again after you save it, and can be revoked on your provider's side at any moment. We do not train on your conversations.
Something we have not answered? Ask us directly — security questions get a person, not a form letter.