Back to Community
Home / Community / Plugin → Cookie notice & compliance for gdpr / ccpa

Understanding and Accessing User Consent Logs in Cookie Notice & Compliance

27 threads Sep 9, 2025 Plugin → Cookie notice & compliance for gdpr / ccpa

Content

One of the most common questions from website administrators using the 'Cookie Notice & Compliance for GDPR / CCPA' plugin is about user consent logging. Many users need to access a record of which visitors have accepted or rejected cookies to comply with regulations like the GDPR, which often requires keeping proof of consent.

What is the Consent Log and Why is it Important?

Regulations such as the GDPR stipulate that a service provider must keep a record of user consent. This record should ideally include information like a timestamp and the user's choice (accept or reject) so it can be provided as proof if required. The core question from users is: "Where can I see the users' consent information?" and "Is there a report or protocol of users who accepted?".

How the Plugin Handles Consent Storage

Based on user reports and discussions, the method for storing consent depends heavily on which version of the plugin's ecosystem you are using.

1. Basic Free Version (Cookie Notice)

The standalone free 'Cookie Notice' plugin primarily stores the user's consent choice in their browser as a cookie named cookie_notice_accepted. This cookie contains a simple true or false value. A significant limitation, as noted by many users, is that this method does not create a centralized log or database record on your website by default. There is no built-in admin area to view a list of user consents, which is a critical feature for GDPR compliance.

2. Integrated Cookie Compliance Service

Several threads reference a more advanced 'Cookie Compliance' service. When the plugin is integrated with this service, consent data is stored in two places:

  • Locally in the user's browser (the cookie_notice_accepted cookie).
  • In a cloud-based dashboard, which serves as the official consent proof for the site owner.

Users who have signed up for this service report seeing activity in the Cookie Compliance dashboard. However, some note that the "Consent Logs" within their WordPress admin area might remain empty, suggesting the cloud dashboard is the primary interface for accessing this logged data.

Common Challenges and Solutions

Problem: No Built-in Consent Log in Free Version

Many users find the lack of a logging feature in the free version to be a major hurdle for compliance.

Potential Solutions:

  • Custom Development: It is possible to create your own logging mechanism. The plugin triggers a JavaScript event (setCookieNotice) when a user makes a choice. You can hook into this event with custom code to send the consent decision, along with a timestamp and IP address, to your database via an AJAX call. This approach requires development knowledge.
  • Explore the Cookie Compliance Service: The 'Cookie Notice & Compliance for GDPR / CCPA' team suggests that their Cookie Compliance service provides the necessary consent logging features in its cloud dashboard.

Problem: Consent Log is Empty in WordPress Admin

Some users with the Cookie Compliance service report that the consent log within their WordPress admin is empty, even though data appears in the cloud dashboard.

Explanation: This indicates that the primary storage and interface for consent logs are managed within the cloud service's dashboard, not the local WordPress database. The local admin area may have limited or different functionality.

Problem: Understanding the Data in Logs

Users sometimes see consent IDs in logs but struggle to correlate them with specific visitor information.

Explanation: The data stored is designed for proof of consent as required by law, which may not always include personally identifiable information like IP addresses by default. The structure and content of these logs are defined by the Cookie Compliance service.

Key Takeaways

  • The basic free plugin stores consent only in a browser cookie and does not maintain a central log.
  • For a full consent log that meets regulatory requirements for proof, the plugin is designed to integrate with the separate Cookie Compliance service, which stores data in the cloud.
  • Creating a local consent log requires custom coding to capture the consent event and store the data.
  • If you are using the integrated service and your WordPress admin log is empty, check the cloud-based dashboard for the complete consent records.

When evaluating your compliance needs, carefully review the features of the free plugin versus the integrated Cookie Compliance service to ensure your setup can generate the necessary proof of consent.

Related Support Threads Support