Privacy risk dashboard
Sample scan state · public-facing reviewReview practical privacy and cookie gaps, then use the next actions to move the public record forward.
Privacy Risk Score
26/100
Critical Risk
Issues found
6
Needs attention
2
high-priority gaps
Privacy Risk Score
26/100
Critical Risk
High-impact public-facing gaps need prompt review before lower-priority work.
This score reflects the full sample scan, not the active severity filter. It summarizes visible public-facing findings only—not legal compliance, certification, or a guarantee.
Critical: 0 × 35 points = −0
High: 2 × 20 points = −40
Medium: 3 × 10 points = −30
Low: 1 × 4 points = −4
Findings
Analytics and advertising-style requests begin on the marketing site before an affirmative consent choice is recorded.
Source: homepage request review · cookie banner interaction
Recommended next action
Hold non-essential tags until visitors opt in, and test reject, dismiss, and revisit-banner paths.
The banner presents an immediate acceptance path, while declining or changing preferences takes extra navigation.
Source: cookie banner controls · desktop viewport
Recommended next action
Place accept, reject, and preference controls at the same decision level with plain-language labels.
The public cookie notice describes categories broadly but does not help visitors connect listed purposes to the trackers found on page load.
Source: cookie notice compared with public page requests
Recommended next action
Add a maintained cookie table with provider, purpose, duration, category, and relevant preference control.
The policy mentions personal information generally, but public forms and product flows suggest additional categories such as account, usage, and support data.
Source: privacy policy · public contact and sign-up surfaces
Recommended next action
Map each public collection point to the data categories, purpose, and sharing language in the policy.
The policy says information is retained as needed without explaining the criteria or typical periods for common customer records.
Source: privacy policy retention section
Recommended next action
Describe retention criteria and publish practical ranges where they can be stated accurately; align them with internal deletion practices.
A general inbox is visible, but a dedicated privacy or data-processing route is not clearly signposted from policy and footer pages.
Source: footer links · privacy policy contact section
Recommended next action
Add a clear privacy contact route and link it from the policy, cookie notice, and website footer.
ClearMinder highlights public-facing signals for operational review. It is not legal advice, a complete audit, or a compliance guarantee.