Consent

Consent management with a record of each choice

Collect a choice once, keep the consent log, and let the person withdraw without losing the audit trail of what was agreed.

Create a workspace View consent platform pricing

What is consent management?

Consent management is the practice of presenting a privacy choice, recording what the person decided, letting them change or withdraw that choice, and applying the current choice to the systems that process their data.

Collection without history does not travel

Teams often store a boolean on a profile and call it consent. That boolean cannot show the notice, the purposes, or a later withdrawal. Consent tracking needs those fields.

Consent Guru records the decision, the policy snapshot, and subsequent changes. Current state and historical evidence are not the same row rewritten in place.

From collection to withdrawal

Step 1
Collect
The banner or preference center asks for a specific action against the purposes you defined.
Step 2
Store
The consent record includes an identifier, timestamp, locale, and the notice snapshot.
Step 3
Track
Status can move from granted to denied or withdrawn. Analytics summarizes outcomes. The evidence snapshot remains.
Step 4
Prove
A consent receipt can carry cryptographic proof of the recorded decision for the snapshot that was signed.

Key capabilities

Consent records

The operational record of a person’s current choice for a site and policy.

Consent history

Changing a choice writes the new decision. Automated cleanup does not delete historical evidence unless retention is explicitly configured and no legal hold applies.

Consent audit trail

Workspace audit logs cover configuration and access changes alongside the consent evidence itself.

Withdrawal

A visitor can change or withdraw optional purposes in the preference center. The SDK follows the updated record.

What teams use it for

Purpose-level consent instead of one site-wide flag.
A receipt path for the decision you need to explain.
Retention settings for evidence, records, audit events, and rights requests.
Portable consent export between domains you configure.

Regulated products

Show a purpose list that matches the processing the product actually performs.

Support and privacy teams

Look up a consent identifier when someone asks what they agreed to.

Cross-domain journeys

Exchange portable consent across domains that you have explicitly configured.

Privacy considerations

Consent is only one lawful ground. Do not label a record as consent if the organization is relying on another basis.

Retention of evidence can itself be personal data processing. Set retention in the product to match the policy you have adopted, and use legal holds when a matter requires preservation.

Technical capabilities

Consent API

Server-side collection and lookup go through authenticated API keys, separate from the public SDK endpoints the browser calls.

Webhooks

Consent and rights events can be posted to your endpoint with an HMAC SHA-256 signature.

Questions

1.What is user consent management?

It is the ongoing process of collecting, storing, updating, and enforcing a person’s choices about specific purposes.

2.What is a consent audit trail?

It is the retained history of the decision and of administrative changes, so a reviewer can see what was recorded and what was later configured.

3.Does withdrawal delete the old record?

No. The current choice updates, and historical consent evidence is kept according to your retention settings and any legal hold.

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.