Anonymity Policy
A plain-language explanation of how we protect candidate identities — technically and legally.
Structural Anonymity
Anonymity on Skill Nexus is not a UI toggle. The candidate_profiles database table contains no name, email, photo, or contact fields. This data structurally cannot be queried, because it is not stored there.
Row-Level Security
Supabase Row Level Security (RLS) policies enforce that published candidate profiles return zero identifying information to any authenticated user. Even a direct database query from an employer account cannot return identifying data.
The Identity Reveal
When a candidate accepts an interest, a server-side API route creates a record in the identity_reveals table. Employers can view it only after an included or paid reveal unlock is recorded in employer_reveal_unlocks.
Candidate Obligations
To preserve your own anonymity, your profile bio and experience descriptions should not include your name, current or past employer names, or links to personal social media. We recommend writing in industry-level terms only.
Employer Obligations
Employers who attempt to de-anonymise candidates through indirect means (e.g. cross-referencing unique skill combinations with LinkedIn) violate our Terms of Service and will be permanently banned.