Privacy of Records & Exports

Pseudonymous is not anonymous

An identifier or hash can still relate to an identifiable person when combined with other information. The GDPR, recital 26 distinguishes anonymity from pseudonymisation.

Minimise access and copies

Give dashboard/agency access only to authorised people. Use least-privilege API keys, protect backups, and avoid emailing raw CSV files or posting visitor IDs/user agents in public support threads.

Exports are independent copies. Removing a website or revoking a key does not erase files already downloaded or data already shared with another system.

Retention policy

Keep evidence while necessary for the relevant consent-based processing. After that processing ends, further retention requires documented necessity for legal obligations or claims; blanket indefinite retention is not appropriate.

ConsentEase's default retention keeps each record until its scheduled renewal date + 24 months, never shorter than recording time + 365 days + 24 months; then it becomes eligible for removal by a daily cleanup. The website owner is the controller: document the evidence purpose, grounds and review triggers (processing ends, consent is withdrawn, purposes/notices materially change, an obligation or claim arises), and export and safeguard records you must keep longer before their retention date. Browser renewal settings and expiresAt on their own never authorise deletion.

Evidence beyond log rows

Keep the relevant notice text, category purposes, banner/tag configuration and change history. Version fields can be absent or generic; a row alone does not reconstruct every historical screen.

Support and processors

Supply redacted observations for troubleshooting. Review applicable privacy terms and processor arrangements for your account and connected providers. These technical guides do not replace a legal agreement or confer anonymous-data status.