Trust and data handling
How the public preview protects privacy, provenance, and deadline-aware listings.
Source review before amplification
Seeded events and opportunities should link to official or canonical sources. Fixed-date records use explicit calendar dates rather than rolling countdowns.
Privacy thresholds on people data
Salary and talent density surfaces suppress low-count cells. Practitioner location is opt-in and fuzzed before public display.
Provenance stays visible
Official baselines, employer-posted ranges, curated listings, and community reports remain separate so readers can judge the source of each claim.
Paid tools do not rewrite consent
Employer and recruiter tools are funded separately from community access. Paid visibility does not expose private practitioner data.
Measurement without surveillance
Traffic is measured first-party and in aggregate. Arrival events record only the referring site's hostname and campaign tags (utm parameters); full URLs, IP addresses, account identifiers, and per-user tracking identifiers are deliberately not collected or stored for analytics. One visit per browser session is marked by a flag that stays in the visitor's own browser and is never sent to the server.
Public preview data checks
- Event dates, program deadlines, venue names, and source URLs are checked against organizer or official program pages before announcement pushes.
- Records with no confirmed current-cycle date should use a neutral official link or stay out of public preview inventory.
- Support, data-correction, and moderation paths stay available so visitors can report stale or inaccurate listings.