Consent Records & Export
Fields, pseudonymous data, filters and the 10,000-row export limit.
Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.
Evidence with limits
ConsentEase records received visitor interactions/decisions. These records can support an audit, but they do not prove every tag respected a choice or provide everything a regulator might require. Missing/blocked log requests can leave gaps.
Recorded and exported fields
The dashboard CSV includes Timestamp, Visitor ID, Action, IP Hash, User Agent, Country, Region, Consent Choices, Banner Version, Policy Version and Expires At. Some fields can be empty, depending on the recording path and available information.
For new records, Expires At means scheduled decision renewal, not proof expiry or a deletion deadline. It uses the reported decision timing/period, or the current site setting from receipt time when timing is absent. Historical rows retain their older fixed-year metadata. Timestamp is the server's recording time and can differ from the sender's decision time. See Re-consent & Evidence Retention for fallback and verification limits.
A visitor ID or hashed IP is pseudonymous, not automatically anonymous. User-agent/location/context can add identifying information. Do not describe this dataset as containing no personal data.
View and filter
Select the website in Consent Logs. Narrow by available date, action, visitor-ID search and country filters. Accept all, reject all, custom and dismissed are distinct; legacy dismissal labels can be normalised by the service.
Export carefully
- Choose the website and filters.
- Click the CSV export control.
- Check the row count and requested range before relying on it.
Each dashboard export returns at most 10,000 records. It is not a guarantee of a complete all-time export. Split manageable ranges and reconcile totals; if a single range still exceeds the cap, use the paginated read API or contact support for a complete retrieval procedure. Do not assume every additional filter is available on REST consent-log.
Retention and withdrawal
Re-consent, record expiry and log retention are separate. By default, ConsentEase keeps each record until its scheduled renewal date + 24 months, and never shorter than recording time + 365 days + 24 months; after that, it becomes eligible for removal by a daily retention cleanup. See Re-consent & Evidence Retention for examples.
A withdrawal is a new record with its own timestamp and follows the same rule; it does not delete earlier records. As the controller, export anything you must keep longer before its retention date, and protect exports.
Website deletion can remove related records; preserve legitimately required evidence before a destructive action.