Account and platform decisions
Keep the original notice, rule cited, account or content identifier, appeal history, and response dates together.
European Commission — Digital Services ActDigital-rights record readiness
Preserve the decision, incident, and account record
Digital-rights routes depend on the service, event, location, and data involved. Compens.ai keeps official source context separate from your private records so you can prepare without an outcome estimate or automatic submission.
Keep sensitive details private
Account identifiers, breach notices, identity records, screenshots, and private messages belong in your workspace, not on this public page.
Start with the event you can document
These route groups organize preparation. They do not decide whether a law applies or whether a platform, company, or authority will act.
Data exposure or identity misuse
Preserve the notice, affected data types, account alerts, unfamiliar activity, and the steps already taken.
Review record promptsPlatform or account decision
Keep the decision notice, stated rule, content or account identifier, appeal history, and response dates together.
Review record promptsImpersonation or deceptive content
Capture URLs, timestamps, account names, original files, reports, and observable harm without republishing sensitive material.
Review record promptsUnderstand the digital record
A useful digital-rights record preserves what the service or authority actually said, what data or account was involved, and when the event occurred.
Security and identity incidents
Preserve notices and observable account activity; use current security guidance before sharing any sensitive detail.
CISA Secure Our WorldPrivacy routes depend on location
The relevant regulator and process can differ by jurisdiction, service, and event. Recheck the official source before acting.
European Data Protection BoardExplore digital-rights case topics
Choose a topic to keep its existing information and preparation route available. These links organize public information; they do not determine responsibility or an outcome.
Data breach and privacy
Social media account issue
AI bias and discrimination
Healthcare data breach
Platform or algorithm issue
Deepfake or impersonation
Biometric privacy
Build a reviewable record
Original notices
Keep the complete notice, sender or service, date, reference number, stated reason, and any deadline.
Timeline and responses
Record when the event was discovered, security changes, reports, requests, appeals, and each response.
Account and identity links
Connect account identifiers and affected data without storing passwords, recovery codes, or unnecessary identity documents.
Source and route checks
Save the current official instruction, its jurisdiction and scope, and the date you checked it.
A controlled preparation flow
1. Stabilize access
Use the service's current security guidance where access or identity may be at risk, and preserve what changed.
2. Preserve the original record
Keep notices, URLs, timestamps, identifiers, and source files before editing screenshots or writing a summary.
3. Check scope and route
Confirm the service, country, data, decision, and deadline against a current official source.
4. Choose what leaves the workspace
Review sensitive details and decide for yourself whether to use a service, regulator, reporting body, professional, or another route.
Current official route context
Open the relevant source and recheck its instructions before taking an external step. Coverage and process vary by jurisdiction, service, and event.
Sources reviewed: 2026-07-10
U.S. Federal Trade Commission
Identity theft and recovery routes
Current U.S. consumer guidance on recognizing identity misuse and using IdentityTheft.gov for a recovery plan.
Open official sourceCybersecurity and Infrastructure Security Agency
Account and phishing safety
Protective guidance on phishing, strong passwords, multifactor authentication, and software updates.
Open official sourceEuropean Commission
Digital Services Act user routes
EU context for covered platform notices, internal appeals, and certified out-of-court dispute settlement.
Open official sourceEuropean Data Protection Board
Find the relevant data-protection authority
Official context for contacting an organization or the relevant national authority; the EDPB does not handle individual complaints.
Open official sourceYou control every external step
Compens.ai organizes records and source context. It does not contact a platform, company, regulator, police service, or court; submit a report, complaint, appeal, or takedown request; provide legal or cybersecurity advice; represent you; or predict recovery or outcome.