Data Deletion: Dashboard Actions, Not Emails to the Website
Disconnecting a channel, removing a team member from your workspace, and deleting conversation history are three distinct operations. volbor does not treat them as a single blanket «delete everything». There is no public email address for such requests, so emailing an assumed address deletes nothing. This page explains the differences. It does not constitute a formal legal procedure for a specific legal entity and does not guarantee a button if you do not see it in your dashboard.
If there is no specific action available in the dashboard, do not assume data has disappeared on its own.
Rushing into Data Deletion
- Disconnecting a channel and assuming it's done: new messages stop coming in, but existing conversations remain right in your Inbox.
- Offboarding an employee while leaving credentials active: they can still log in and view message history.
- Requesting deletion via email: there is no dedicated inbox on the website, so the request goes unseen.
- Deleting the entire workspace to remove a single thread: this destroys all ongoing conversations currently handled by the active shift.
What to Do Instead of Sending an Email
Halt incoming messages
Disconnecting the channel on the connection screen stops incoming traffic. Test from an external account as outlined in troubleshoot delivery: messages should not appear in Inbox. Historical logs may still remain.
Revoke user access
Deactivate their user profile in your workspace settings. Do not simply change a shared password if logins were personal: shared passwords obscure whether access was truly revoked. Review permissions in security.
Look for deletion controls exclusively inside your dashboard
If a specific action exists to delete a thread or workspace, read the confirmation warning carefully before proceeding. If no such action exists, this website page cannot add one and does not promise a hidden manual queue. Never tell a customer their data is destroyed until you personally verify its absence where it once resided.
Account for external data copies
Messages forwarded to personal chat apps, exports synced via API & Webhooks into your internal database, and legacy CSV exports are NOT deleted by this button. You must delete them directly in the external systems where they reside.
What to Tell a Customer Requesting Data Deletion
First, locate the conversation and inspect what specific actions your dashboard permissions allow. Reply to the customer via the channel you already use to communicate, stating exactly what was done: user access was revoked, the channel was halted, or the thread was deleted if you deleted it. Do not paste this article as legal confirmation. The Privacy Policy explains why data was stored initially, and does not serve as a certificate of deletion.
Questions
Will conversations be deleted if we stop paying?
Do not assume this based on this article. Check your workspace billing warnings. Non-payment and data deletion are not equivalent unless explicitly stated on your dashboard screen.
Can we delete only attachments?
Only if your workspace dashboard provides a dedicated action for this. Otherwise, do not promise partial deletion.
What about backups and specific retention periods?
Exact timelines and backup cycles are not defined here because they are not published in public site cards. Do not invent a «30-day» timeline when replying to a customer.
Who is authorized to execute data deletion?
Only users whose assigned role grants deletion permissions. A team member without appropriate rights cannot bypass permission limits by emailing the website.
Is this a GDPR requirement?
Regulatory frameworks like GDPR provide context for data subject requests, but available controls and retention periods are defined by your workspace plan and contractual terms, not by wording on this page. No single nation's legal standard is substituted automatically.
Related Pages
- Privacy Policy
Why it matters: Understand what data you actually intended to retain before promising deletion.
Without it: Teams wipe the wrong data while leaving copies behind. - Security
Why it matters: Revoke login access for departed team members.
Without it: History is assumed «deleted», but credentials remain live. - Message Delivery
Why it matters: Verify via testing that incoming messages no longer enter after disconnecting a channel.
Without it: Teams consider a channel disabled just because a toggle was flipped. - Webhooks and API
Why it matters: Account for exports to your internal system that the dashboard cannot wipe.
Without it: Conversation copies remain in your CRM or ERP. - Contact
Why it matters: Avoid searching for a non-existent email address for data deletion requests.
Without it: Customers are given an invalid contact email. - Terms of Service
Why it matters: Do not confuse technical deletion guidance with legal contracts.
Without it: This article is mistakenly presented in disputes as formal corporate legal procedure.