Data Protection and CRM: What to Watch When You Hold Customer Data
Managing personal data in a CRM: notices, consent, permissions, retention periods, deletion requests and security controls.
Using a CRM means processing personal data. That is not a risk but a responsibility — and it is managed largely through process decisions rather than technical ones.
Note: this article is general information, not legal advice. Consult your legal adviser about your obligations.
Which data in a CRM is sensitive?
- Identity and contact details: name, phone, email, address, national ID numbers.
- Transaction history: purchases, quotes, payment status.
- Communication content: call recordings, message threads, notes.
- Free-text notes: the most overlooked category. An agent’s note that “the customer was ill” can become special-category data.
Five controls to put in place
Permissions
Not everyone should see every record. Department, branch and role-based scope is the fundamental control for both security and compliance.
Audit trail
Who viewed or changed which record and when must be traceable. In a dispute it is your only evidence.
Retention periods
Data cannot be kept indefinitely. Define a retention period per record type and act when it expires.
Deletion and anonymisation
Decide in advance how a record will be deleted when requested — including what happens to related records.
Notice and consent records
How the data was obtained and which permissions were given should be held in the system; marketing consent must be separate.
Transport security
HTTPS is mandatory; where exported spreadsheets end up is a risk in its own right.
Common mistakes
- The habit of bulk spreadsheet exports. Uncontrolled downloads bypass every security control the CRM has.
- Not revoking access when someone leaves. Tie the process to a checklist.
- Not disclosing call recording. If calls are recorded, the caller must be told.
- Confusing marketing consent with being a customer. A service relationship is not consent to commercial messages.
- Using real customer data in test environments. Test data should be masked.
When a deletion request arrives
- Log the request and verify identity.
- Identify where the data appears (contact record, calls, messages, quotes, tickets).
- Separate records you are legally required to retain; these cannot be deleted but access can be restricted.
- Delete or anonymise the rest.
- Record what was done and inform the requester.
Frequently asked questions
Does data have to be hosted domestically?
Transfers abroad are subject to specific conditions. The simplest route is a service that hosts the data in your own jurisdiction — it also simplifies the answer you give your customers.
How long should I keep call recordings?
It depends on the regulation in your sector. Indefinite retention is not a defensible practice; set a period and enforce it automatically.
How do I control what my team writes in notes?
Technically hard, procedurally possible: define a short rule for what must not go in a notes field and repeat it in training.
Next step: to see how permissions and scope controls work, request a demo.