Customer data, privacy & anonymisation
Support conversations hold personal data: names, email addresses, what a customer said about their problem, and sometimes the contents of their account. This page explains how Helpin treats that data and what "anonymised" means for a conversation.
What a conversation holds
The customer's identity — name, email, and a link to the matching CRM contact where one exists.
Message content — everything both sides wrote, plus attachments.
Conversation metadata — priority, tags, assignee, request type, custom field values, SLA state.
Related records — tasks and deals created from the conversation, and the company the customer belongs to.
Because these are linked, deleting one piece does not remove the rest. Plan privacy requests around the whole set rather than a single field.
Anonymised conversations
A conversation can be marked anonymised. An anonymised conversation is treated as no longer carrying the customer's identity:
It is not shown to the customer in the customer portal, even if they were the one who raised it.
It remains in the workspace for reporting and audit continuity rather than being deleted outright.
The practical effect is that anonymising a conversation keeps your aggregate history intact while removing the customer's access to it — useful when a volume or SLA figure should not change because one person asked for their data to be removed.
Working with privacy requests
Identify everything the person touches — conversations, CRM contact, company association, attachments, tasks and deals created from their conversations.
Start with the CRM record. If the contact is wrong, every conversation attached to it inherits the error.
Anonymise rather than delete conversations you still need counts from. Deleting changes your historical reporting; anonymising does not.
Check the portal exposure. An anonymised conversation is hidden from the portal, so the customer will not see it there after anonymisation. If they still need the record, export or answer them first.
Do not rely on a display name alone. A conversation with the name cleared but the email still in the thread has not really been anonymised.
What anonymisation does not do
It does not rewrite the message text a customer wrote. If they included personal details in their own reply, those words remain in the thread.
It does not remove the conversation from reporting totals.
It does not touch records outside Support, such as the CRM contact.
Treat anonymisation as one step in a process, not a single button that makes a person disappear.
Related pages
Was this article helpful?