Consent preference records

Detects consent and preference records: a consent record / consent register / marketing or privacy consent phrase combined with populated consent data - rows keyed by a customer identifier, labelled consent status/date/version values or labelled customer identifiers. Phrase-only mentions (privacy notices, cookie banners) stay discovery-only.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Enforce tiers require populated dataset structure (a data row keyed by a customer/record identifier, a labelled value or a labelled identifier) beside the topic phrase; a column header on its own only counts toward 85, so blank extracts stay at 65. Help pages, policies, product copy and news that only name the topic stay at 65. Medium because internal analytics documentation with worked examples can still reach 75.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: Privacy Act 1988 (Cth), Spam Act 2003 (Cth), Information Privacy Act 2009 (Qld), NDB Scheme (Cth), GDPR
Frameworks: ISO 27001, ISO 27701
Data categories: pii
Scope: wide
Risk rating: 5
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?i)\b(?:consent\s+(?:preference\s+)?records?|consent\s+(?:register|logs?|receipts?)|(?:privacy|marketing|cookie|data\s+processing)\s+consents?(?:\s+(?:records?|logs?|status))?|consent\s+management\s+(?:platform\s+)?(?:exports?|extracts?|data)|communication\s+preferences)\b

Corroborative evidence keywords

privacy notice version, consent withdrawn, double opt-in, proof of consent, IP address, source channel, preference centre, granular consent, data subject

Proximity: 300 characters

Should match

Consent preference records - CMP export customer_id,consent_purpose,marketing_email,marketing_sms,consent_version,consent_timestamp 88104421,marketing,true,false,v3.1,2026-08-02T10:14:22Z 88104437,analytics,false,false,v3.1,2026-08-03T19:02:11Z Proof of consent held with IP address and source channel. — CMP export - header, customer rows and proof-of-consent evidence (85)
Privacy consent record Customer ID: 88104421 Updated via the preference centre. — Single labelled customer identifier (75)
Marketing consent record - subscriber profile Subscriber ID: SUB-4410982 Marketing email: withdrawn Marketing SMS: opted out Consent withdrawn: 03/10/2026 Source channel: preference centre unsubscribe link Original sign-up captured double opt-in under privacy notice version 4.2. — Subscriber profile with labelled ID, per-channel consent values and withdrawal date plus withdrawal/source-channel evidence (85)

Should not match

Policy guidance: keep consent records showing when and how each person gave marketing consent, and honour withdrawals promptly. Our privacy notice explains the purposes. — Privacy guidance
Consent register customer_id,consent_purpose,marketing_email,consent_timestamp — Blank register - column header only (65)
Regulators found cookie consent banners on 40% of sites did not record valid consent, a news report said. — News item
unrelated generic text without domain phrases — Unrelated
customer invoice — Generic word pair

Known false positives

Privacy notices, help-centre articles, product pages and policies describing consent and preferences. Mitigation: They name the topic without populated rows, labelled values or identifiers, and guidance/help framing is excluded, so they stay at 65.
Analytics training material and documentation with worked examples of consent and preferences. Mitigation: Training and template framing is excluded; unframed worked examples with realistic rows can still reach 75.
News and industry commentary with aggregate statistics. Mitigation: Aggregate percentages are not keyed to a record identifier, so they do not satisfy the row or labelled-value structures.