Your Customer Data Protected End to End
Data from the customers you talk to on WhatsApp Business is collected in one panel. With role-based access, each team member sees only the conversations and customer details they are authorised for. We configure access and permission settings for you during setup. Compliance is assessed together with your organisation's own processes and consents.
Customer data is collected in one panel. With role-based access, each team member sees only the conversations they are authorised for. We configure access and permissions during setup. Compliance is assessed together with your organisation's own processes and consents.
Security Settings
Configured together during setup
Is the data you collect on WhatsApp putting you at legal risk?
Who can see the customer data you collect on WhatsApp? Under which consent is it processed? How will it be deleted when someone asks? If these do not sit in one place, the whole burden stays with you. Chatinbox lets you run this from one panel: data processing agreement (DPA) support, tracking of explicit consent records, and deletion or anonymisation on request. Compliance itself is assessed together with your organisation's processes and consents.
- Data processing agreement (DPA) ready
- Tracking of explicit consent records
- Deletion and anonymisation on request
Are your messages really encrypted, or is it just a claim?
All traffic between the panel and the server travels over HTTPS/TLS. Customer conversations never pass over an open connection. Role-based access decides who can open which conversation. We go through the technical details on the storage side, and your own information security questions, one by one in the initial call.
- Encrypted connection over HTTPS/TLS
- Visibility limited by role-based access
- Your information security questions answered one by one in the initial call
TLS
Panel connection is carried encrypted
Access Control
Two-factor authentication
Enabled
IP-based restriction
3 IPs defined
Session management
Automatic timeout
Do you really control who logs into the panel?
If panel login is protected by a password alone, one stolen password opens the entire customer history. Chatinbox two-factor authentication works over SMS and email. With IP allow and deny lists, login opens only from the locations you permit. When an unknown login attempt happens, you are told at once.
- Two-factor login via SMS and email
- Allowed and blocked IP lists
- Instant alert on unrecognised logins
When an employee leaves, who keeps the customer history?
When conversations pile up on an agent's personal phone, the customer history leaves with that person. In Chatinbox, conversations and the customer record sit in one panel. When a user's access is removed, the past conversations stay with the organisation. Role-based access decides who sees which conversation and customer detail. When a deletion or anonymisation request comes in, the related records are processed on request.
- Conversations in one panel, not on personal devices
- History stays with the organisation when access is removed
- Who sees what is set by role
- Deletion and anonymisation processed on request
User Permissions
Admin sees all conversations
Across every channel and team
Team lead sees their own team's conversations
Other teams' threads are closed
Agent sees only assigned conversations
Customer details limited by permission
Departed user has access closed
Past conversations stay in the panel
Do not leave your customer data to chance
You decide with role-based access who sees which conversation and customer detail. Conversations sit in one panel, not on personal phones. We do the setup. Compliance is assessed together with your organisation's processes and consents.
How to do it
Step-by-step guides from the help center for this feature:
