Toolkits · Free
Privacy-First Publishing Checklist (Free)
A practical checklist and rewrite patterns to reduce accidental identification risk (“doxxing-by-detail”). Education only. Not legal advice.
Who this is for (and who it is not for)
Privacy-first
Education only
No case review
No outcomes sold
For
- Individuals who want a calm, repeatable pre-publish privacy check.
- Writers/creators who need safer wording (de-identification) without losing meaning.
- Anyone building a public-interest post while minimizing accidental exposure.
Not for
- Legal advice, emergency situations, or time-critical professional decisions.
- Document review, “tell me what to file,” or case/outcome strategy.
- Publishing raw evidence that contains identifiers (names, addresses, private IDs).
Do not include identifying details (read first)
- Do not publish full names, addresses, phone numbers, emails, usernames, or personal IDs.
- Avoid faces, license plates, signatures, unique workplace identifiers, or private threads.
- Be cautious with screenshots: headers, footers, filenames, and metadata often reveal identity.
- Indirect identifiers matter: time + place + role can triangulate a person even without names.
Redaction vs de-identification (plain English)
- Redaction removes or blocks a specific identifier (for example, a name or address).
- De-identification reduces the chance someone can be identified from combined details (time + place + role).
- Safer default for public posts: redact direct identifiers and also generalize indirect identifiers.
Privacy checklist (minimum standard)
- Direct identifiers: names, addresses, phone/email, IDs, account numbers, faces/plates.
- Indirect identifiers: exact dates/times, precise locations, niche titles, one-of-one events.
- Searchability: paraphrase quotes that can be searched; avoid verbatim message text.
- Attachments: crop aggressively; remove headers/footers; rename files to neutral labels.
- Publish-safe framing: separate what is known from what is not known; label limits clearly.
- Default rule: keep raw evidence private; publish the pattern and defensible claims.
5-minute pre-publish check
- Can a stranger identify a person from time + place + role?
- Is any detail unnecessary for public understanding?
- Are you publishing “proof” that also exposes private identifiers?
- Does the post include minors or vulnerable people in identifiable ways?
- Did you add a corrections path (how updates will be noted)?
Free vs Pro vs Training
| Option | Best for | What you get |
|---|---|---|
| Free (this page) | First pass, quick hygiene | Checklist + copy patterns + one worked example |
| Pro PDF ($19) | Repeat use, printing | Printable worksheets + expanded drills + formatted examples |
| Training ($99) | Skill-building | Structured drills to build habits (no case handling) |
Copy patterns (safe rewrite recipe)
Worked example (before → after)
Before (too identifying)
“On March 12, 2025 at 8:40am, I met a manager at a specific building near a major street.
They told me to ‘stop complaining’ in front of two staff members. I have an email thread and a screenshot.”
After (de-identified)
“In early 2025, I raised concerns in a workplace setting with a senior staff member present.
The response included dismissive language in front of others. Private records exist, but identifying details are not published here.”
- Exact time + place removed (reduces triangulation risk).
- Rare title generalized (reduces one-person identification).
- Evidence referenced as privately retained, not published as raw screenshots.
Limits & safety boundaries
- Education only. Not legal advice.
- No case review: no document review, no “tell me what to file,” no strategy.
- No guarantees: this reduces risk; it cannot eliminate risk in all contexts.
- Do not send sensitive personal data: avoid identifiers and private records in messages.
- Editorial firewall: support and purchases do not buy coverage, outcomes, or favourable treatment.