Consent records
Each decision keeps an identifier and a policy snapshot so a later review can see what was actually presented.
Product
Consent Guru is consent management software that helps organizations present a choice, store the consent record, and apply that choice to cookies, tags, and later privacy requests.
A Consent Management Platform (CMP) is software that helps organizations collect, manage, store, communicate, and enforce user consent and privacy preferences across digital experiences. Consent Guru is that kind of platform. Using it does not by itself make an organization legally compliant.
Many sites collect a click and then lose the context: which notice version was shown, which purposes were optional, and whether the person later withdrew. A consent management platform keeps that context with the decision.
Consent Guru is built as that system for websites. Legal and product teams publish a policy. The SDK presents it. The workspace keeps the consent log, the preference center, and the signals other tools are allowed to use.
Step 1
Mark what is required for the service and what is optional, then map vendors and trackers to those purposes.
Step 2
Draft the banner and preference-center copy, then publish a version. The live site uses the last published version.
Step 3
The SDK stores the decision with a consent identifier, timestamp, locale, and a snapshot of the notice that was shown.
Step 4
Optional scripts wait on the recorded choice. Teams review consent analytics, audit logs, and later withdrawals from the same workspace.
Each decision keeps an identifier and a policy snapshot so a later review can see what was actually presented.
Scan a site for cookies, scripts, and third-party trackers, then classify them against purposes and vendors.
Returning visitors can review purposes and change an earlier choice without contacting support.
Issue API keys and deliver consent and rights events to endpoints you operate.
Publish per website, with domain checks so a site key is used on the host it was registered for.
Connect consent records with rights-request intake in the public Privacy Centre.
Use the same workspace for DPDP-oriented notices and for GDPR or CCPA/CPRA preference flows.
A consent management platform helps you implement a process. It does not decide your lawful basis, and it does not make an organization compliant by itself.
You still need notices, contracts, and a retention position that match the processing you actually do.
Install the SDK so the recorded choice can be applied before optional scripts run.
When enabled for a website, purpose choices can be mapped to Google consent signals, including ad_storage and analytics_storage.
It is software that helps an organization present privacy choices, store the resulting consent records, and pass those choices to the tags, cookies, and systems that depend on them.
No. The platform publishes the notice you configure and records the choice. Your privacy policy, contracts, and legal review remain your responsibility.
Yes. Decisions keep a consent identifier, timestamp, locale, and policy snapshot. Workspace audit logs also record configuration and access changes.
This page describes how Consent Guru supports privacy operations. It is not legal advice, and using the product does not by itself make an organization compliant with GDPR, CCPA, CPRA, the DPDP Act, or any other law.