Appearance
Erasure and deletion requests
When one of your customers asks you to delete their data, an admin can erase their conversations and the records built from them in a few clicks, for requests under GDPR Article 17 and similar laws. The owner can also delete the whole workspace. Both remove data from Overdesk's own store only. Neither reaches into your help desk, so handle the help desk side there.
Erase one customer
Admins and the owner can erase a customer from Settings → Privacy & Data.
- Open Settings → Privacy & Data.
- Under Privacy requests, enter the customer's email address.
- Select Erase data, read the confirmation, and select Erase.
Overdesk then tells you how many conversations and related records it erased. The erasure cannot be undone.
What it removes
Overdesk finds the customer through their conversations in your knowledge base, matched by email address, and deletes:
- those conversations from the knowledge base
- the drafts, triage results and guardrail decisions for those conversations
- the record that Overdesk sent a reply on those conversations
- the record of any test site run for those conversations
- the comparisons that paired a draft with the reply your agent sent
- the links from any finding to those conversations, and a finding left with no other conversation behind it, or a confirmed defect left with no conversation that confirms it, since its diagnosis was written from the conversations that confirm it
A churn or frustration finding may also keep what the customer holds in Freemius or Stripe. That is found by a stand-in for their address rather than through the knowledge base, so it goes even from a conversation that is still open, along with every finding's link to that conversation.
It also adds those conversations, and the address you erased, to lists Overdesk checks before it works on a conversation again. The next sync does not import them. If the customer writes into one of them again, Overdesk does not draft or send a reply, write a follow-up nudge, classify it or grade it, and an @Overdesk note on it is not answered; the conversations an @Overdesk answer can search leave out that customer's. Asking for a draft or a classification on it says why. No analysis links a finding to them again, even one already running, and no later analysis looks the customer up again. Overdesk keeps a record that the request was made: the address erased, who made the request, and when. Because the address is checked as well as the conversation, this covers every conversation of that customer, one Overdesk had not imported yet and one still open in your help desk included: no drafted reply, no follow-up nudge and nothing sent. Asking for a draft or a classification on one of them by hand says why and does nothing, as it does for an imported one. On Intercom, which names a customer only through their contact, Overdesk reads the contact to compare it with the addresses you erased, and leaves the conversation alone when it cannot read who the customer is. If Overdesk cannot read that list when the daily follow-up run starts, the run stops, and the Runs page says "Overdesk could not confirm which conversations have been erased, so follow-ups stopped rather than risk nudging one. It will try again on the next run."
What it does not reach
- Your help desk. The customer's conversations, and the notes and drafts Overdesk placed on them and any reply or nudge it sent, stay in your help desk. Delete them there if the request covers them.
- Stored results for conversations Overdesk has not imported. Your knowledge base holds closed conversations, so drafts and triage results for a conversation that is still open are not found by an erasure. Overdesk still skips that customer's open conversations from then on. They age out after 180 days with everything else.
- Reports and alerts. A model writes them, so a customer named inside one leaves nothing to match on. They age out on the retention schedule.
- The knowledge-base search log, which ages out after 90 days.
- Conversations indexed before Overdesk last changed its encryption key, which an erasure can no longer match.
- New conversations from the same person. An erasure removes what Overdesk holds when you run it. Overdesk then skips a later conversation from the same address too, because the address is kept, so it is not drafted for, nudged, classified, answered on an
@Overdesknote or sent a reply. Overdesk also never sends a reply on its own that would reach an erased address as someone copied on another customer's conversation, however long ago the request was made. It holds that reply for your team.
Delete the workspace
Only the owner can delete the workspace. The control sits in the Danger zone at the bottom of Settings → Privacy & Data.
- Open Settings → Privacy & Data.
- In Danger zone, type your workspace's short name exactly as the box asks.
- Select Delete workspace.
Overdesk cancels your billing first. If billing cannot be reached, nothing is deleted and you see an error. Then it permanently removes the workspace and everything in it, straight away: every conversation, draft, report and team member, along with your connections and their stored credentials. There is no grace period and no export, and everyone on the team is signed out.
What remains is the legal and audit record, including: that the workspace was deleted, and by whom; each person's acceptance of the Terms of Service and Privacy Policy; and each erasure request made from the workspace, with the address erased, who asked, and when.
What it does not reach
- The Overdesk webhook in your help desk. Overdesk cannot remove it for you, so delete it in your help desk. Until you do, it keeps sending events that Overdesk rejects.
- Your help desk's own data, including the notes, drafts and tags Overdesk placed there.
- Access you granted in other services, such as a help desk API key or the Slack app. Revoke it in those services.
Erasing a customer and deleting the workspace both work after a trial has ended. For the settings tab itself, see Privacy and data.