Consent Audit Log Guide
The Consent Storing page provides a detailed registry of all consent events on your website. This is your primary tool for proving compliance with data protection regulations like GDPR, CCPA, and othe
📑 Understanding the Audit Log
Every time a user interacts with your cookie banner, an entry is created in this table. Here is what each column represents:
- User IP: The IP address of the visitor.
- Event ID: A unique identifier for the specific consent action.
- Action:
- AcceptAll: The user accepted all cookie categories.
- Reject: The user rejected all non-essential cookies.
- Update/Custom: The user saved specific preferences.
- Source: The exact URL where the consent was given.
- Categories (Necessary, Analytics, etc.): A visual indicator (Check for accepted, X for rejected) of which categories the user consented to.
- Timestamp: The exact date and time the action occurred.
- Technical Details: Includes the Browser (User Agent), Platform, and Language to provide a full context for the event.
🔍 Managing Your Logs
1. Search & Filter
You can use the search bar at the top to find specific events. You can search by:
- IP Address: Find all actions taken by a specific user.
- Event ID: Locate a specific transaction if a user provides their ID for a support request.
- Action type: Filter by "Accept" or "Reject".
2. Pagination
We store all history. Use the pagination at the bottom to browse through older logs.
🛡 Why is this important?
Under GDPR, the "burden of proof" is on the website owner. If a regulatory body or a user requests proof that they gave consent, you can use this log to provide:
- Who gave consent (IP/ID).
- When they gave it (Timestamp).
- What they consented to (Specific categories).
- How they gave it (Action and Source).
TIP
These logs are stored securely and cannot be modified, ensuring they serve as a reliable "Audit Trail" for legal purposes.