Anonymity Scorecard
Twelve questions on your existing feedback channel, scored across the five layers where identity leaks.
4 min · free · no account
- Identity
Does writing in require an account or a login?
- Identity
Do you store the sender's IP address or email?
- Tracking
Does the form set any analytics or advertising tracker?
- Tracking
Do you load fonts or scripts from a third-party network?
- Access
Can a manager see who submitted a given message?
- Access
Is access to identifying content logged with a stated purpose?
- Aggregate
Do published breakdowns suppress very small categories?
- Aggregate
Could a chart of one small team identify an individual?
- Derived
Are names written into the box repeated back in summaries?
- Derived
Is the original message kept exactly as written?
- Integrity
Can you detect a flood from one device?
- Integrity
Is anything deleted without an audit record?
0/100
Answer to begin
0 of 12 answered. Yves scores 100 on this scorecard by construction, because every one of these is an architectural decision rather than a policy.
The twelve questions map to the five layers where identity leaks from a feedback channel: identity, tracking, access, aggregate and derived text, plus the integrity trade-off that keeps the channel usable.
Yves scores 100 by construction, because each of these is settled in the architecture rather than in a policy document.
Taxonomy Builder
Start from a sector template, edit every category, set escalation floors, and export the taxonomy your institution signs off.
OpenConfidence Calculator
Wilson 95% intervals on any share, with the sample size you would need to halve the uncertainty.
OpenDuplicate Detector
Paste real messages and watch the near-duplicate engine cluster them live, in your browser, with the similarity scores shown.
Open
These tools use the same logic
that runs in production.
Start a trial and point them at your own corpus instead of a sample.