Overview
Turn privacy policies into an actionable risk brief.
This tool separates the process into clear stages: first define privacy sensitivity, then submit the policy text, then review what data the product asks for and where the policy is vague, excessive, or trackable across services.
Why this matters
Most privacy harm starts before you notice it.
Platforms do not just collect data. They connect behavior across sessions, infer interests, classify people, and optimize what to show next. That is where routine browsing becomes behavioral profiling.
What this tool checks
- What data a product says it collects
- Which items are merely operational and which enable profiling
- Whether the policy suggests cross-service tracking or third-party sharing
- Where vague wording hides real risk
What to look for
- Advertising IDs, device fingerprints, SDK identifiers
- Long retention windows and silent data combination
- Permissions framed as “necessary” without narrow justification
- Inference, audience segmentation, and manipulative targeting
Classification
Privacy risk levels
Analyze
Submit a privacy policy
Waiting for input
Connection
Policy text
Drop a policy file here
or click to import `.txt`, `.md`, `.html`, or `.json`
Findings
What this product wants, and where the traps are
Overall risk
Not analyzed
High-impact items
0
Cross-service tracking
Unknown
Collected data
Run an analysis to populate this section.
Key pitfalls
Run an analysis to populate this section.
Recommended checks
Run an analysis to populate this section.
Model summary
Run an analysis to populate this section.