Use this process to request deletion of data stored by WABA Connect. Removing the application from Bitrix24 disables the integration; it does not automatically delete communication history.
Send a deletion request
- Open EMCsoft support or use the EMCsoft contact page.
- State that the request concerns WABA Connect and provide your Bitrix24 portal address.
- Describe the scope: the entire installation, a particular customer's communications, an employee's access, or installation contact information. Include relevant record identifiers and date ranges where possible.
- Tell us whether the integration is still in use. We will verify your authority and confirm the scope before deleting data.
Never send your Twilio API Secret, Bitrix24 client secret, OAuth tokens or extension authorization code. Support can verify the request without those credentials.
What the request can cover
- Messages, call metadata, permission requests and related application history.
- Employee assignments and extension access associated with your installation.
- Installation contact details and support information held by EMCsoft.
- Credential records and background synchronization data for a discontinued installation.
Some records may need to be retained to meet applicable obligations, resolve disputes or maintain evidence of accepted terms. We explain any applicable retention when handling the request. No fixed automatic deletion period is currently implemented.
Copies in Bitrix24 and Twilio
Messages exported to CRM timelines, registered call activities and uploaded recordings are stored in your Bitrix24 account. Twilio also retains provider records and recordings according to your account configuration and its policies. Removing WABA Connect data does not remove those copies automatically. Coordinate their removal with your Bitrix24 and Twilio account administrators.
If you only need to stop access
An administrator can revoke or replace an employee's extension authorization code, remove the employee in Users, or uninstall the application to disable the integration. Signing out of the extension disconnects that browser session. These actions are different from deleting archived communications.
Read the Privacy Policy for the complete processing description.