Clearer data. A safer digital world.
Consentlytics is the intelligence layer for consent operations. It turns public-page consent signals and discovered resources into evidence your team can review.
View an illustrative sample reportStart free with up to 3 scans and 3 consent tests each month. Choose a paid plan when you need more coverage.
Start with an authorized public-page scan.
Create a workspace, enter a public URL your organization owns, and receive a saved inventory of observable technology signals to review next.
Current MVP scope: returned public HTML and discovered resource URLs only—not browser-level interactions or network requests, dynamic regional rendering, or legal certification.
Signature consent test
State
Indeterminate
Target / test timestamp
◉ Observedhttps://example.org · saved static test
Before
Observed resource inventory
Returned HTML and discovered URLs
Action
No static route sent
Not a browser click
After
No comparable response
Static scan cannot establish a result
Observed
Direct saved HTML/resource evidence
Inferred
Cautious review interpretation
Indeterminate
Explicit static-scan uncertainty
Audit decision and retest lineage
No decisionShows the saved test context without claiming browser-level validation.
01
Observed behavior stays distinct from declared configuration.
02
Experience testing centers on clarity, not dark patterns.
03
Useful visibility without a claim of legal certification.
The operational layer
Today, Consentlytics saves public HTML and resource observations around consent controls so teams can investigate the technology signals they can actually see.
Current static evidence
Observe returned public HTML, identified consent controls, and discovered resource signatures. When a clear static reject or essential-only route is available, compare its saved response with the initial response.
Browser interactions, live consent clicks, and network verification are planned future capabilities, not current scanner behavior.
Continuous monitoring, regional or device experimentation, and always-current vendor inventory are planned rather than active today.
A focused workflow
The current workflow observes public returned HTML and discovered resources. It does not verify browser clicks, network behavior, dynamic regional variants, or legal compliance.
Review initial returned HTML and public resource signals, with one static reject or essential-only path when it is unambiguous.
Compare returned HTML and resource inventories before and after a safely identified static control, then retain the evidence for review.
Give each team a focused record of exceptions, configuration changes, and the audit context behind them.
Designed for shared visibility
Move from spot checks to a shared operational record of public, static consent evidence and its limits.
Use saved public-page evidence to focus manual review of consent clarity and configuration changes.
Surface observed scripts, tags, and changes that deserve browser or implementation-level investigation.
Plans for every operating stage
Choose a monthly plan for the current static evidence workflow and shared review context your team needs.