Source privacy
Privacy and retention for newsroom leads.
Leed is built to help newsrooms work audience tips without turning source contact details into public content. Public story context and private source identity are handled as separate data classes.
What is public
Public pages can show the story lead, location, public-interest summary, beat tags, signal language, and non-contact source display metadata. They do not select or render contact name, contact email, or private contact-request responses.
What stays private
Contact details, contact preferences, safety notes, and reporter outreach decisions are kept behind authenticated workflows. Verified journalists can request contact; the source chooses whether to accept or decline before any follow-up moves forward.
Retention frame
Public story lead fields
Title, body, location, non-contact source display metadata, AI summary, beat tags, and vote totals remain available while the lead is active or needed for newsroom review.
Private source contact fields
Contact name, contact email, contact preferences, and contact-request responses are kept out of public pages and shared only through verified source-consent workflows.
Sensitive and held leads
Spam, PR, serious accusation, privacy, minors, whistleblower, medical, legal, or otherwise sensitive leads can be held for human review before discovery.
Audit and safety records
Admin actions, reports, and moderation decisions are retained so newsroom owners can explain why a lead was held, restored, removed, or routed.
Customer newsroom contracts may set shorter retention periods. A source, newsroom owner, or authorized administrator can request review, correction, export, or deletion at hello@leed.media.
Support and escalation
For urgent source-safety, legal, takedown, account, or newsroom access issues, contact hello@leed.media. Production customers should also name an owner for incident response, auth delivery, AI triage failures, and moderation escalations before launch.