Understand How WhatsHub Handles Security and Access

Review the controls available in WhatsHub, the difference between connection methods, and the responsibilities shared by workspace administrators and users.

Core Capabilities

• Secure Transport

  Application and API traffic is sent over HTTPS in supported production environments.

• Workspace Access Controls

  Workspace roles and protected routes limit access to authenticated product areas.

• Clearly Labelled Connections

  Official Meta Cloud API and QR-based connection methods are presented separately because their capabilities and risks differ.

The Operational Workflow

1. Choose the Connection Method: Review official API and QR-session differences before connecting a number.
2. Assign Workspace Access: Give team members only the roles and product access they need.
3. Review Activity and Privacy Requests: Use available logs and the documented data-deletion process to manage account activity.

Included Product Capabilities

• Privacy Request Process: Published privacy and data-deletion pages explain how users can request account-data actions.
• Authentication Controls: Protected application routes require an authenticated account and enforce workspace access in the product.
• Customer Responsibilities: Workspace owners remain responsible for recipient consent, team permissions, credentials, and applicable messaging rules.

Ideal Fit

Compliance managers and business owners who require secure data handling.

Common Queries