Adoption and Operations

CRM and GDPR: Lawful Basis, Consent, Retention, and Subject Rights

In a B2B CRM, GDPR compliance relies on four configurable pillars: documenting the lawful basis for each data category, recording granular consent by channel and purpose, enforcing automated data retention policies, and ensuring the technical capacity to fulfill data subject access requests promptly across all native modules.

Data within a CRM consists primarily of professional contact details-yet these remain personal data under EU law. The practical distinction lies in the lawful basis: legitimate interest for business-to-business relations versus explicit consent for marketing communications.

This guide outlines the functional requirements a system must support to ensure compliance; it does not replace specific legal counsel tailored to your company's jurisdiction and operations.

In short

  • Documented lawful basis of processing per data category.
  • Consent recorded by channel and purpose, including timestamp and source.
  • Immediate application and propagation of consent withdrawal.
  • Automated retention policies, moving beyond mere declarative statements.
  • Data export and deletion capabilities for subject requests with full traceability.

Concrete System Configurations

Ensure your Smart Operations Layer includes these five essential elements:

  • Consent fields with a complete versioned history of changes.
  • Role-based access control (RBAC) to restrict data visibility to necessary staff.
  • Audit logs for access to sensitive or high-volume data categories.
  • Anonymisation or deletion rules triggered upon retention expiry.
  • A documented technical procedure for responding to data subject requests.

Frequently asked questions

See how it works in CRMconnect

Native modules for sales, quoting and reporting, integrated with the ERP you already run.

From the same topic: adoption and operations

All pages about adoption and operations