01 / ProblemWhat needed to change.
Professional communities and workplace-review products often force a trade-off between credibility and privacy: people want trustworthy company or university context, but exposing real names, login identities, employment evidence, or student records creates unnecessary personal risk.
02 / ApproachWhat I built or explored.
Built a privacy-first identity and verification architecture around Firebase Authentication and Supabase. LinkedOut maps each Firebase UID to a separate random internal UUID before creating a pseudonymous public profile. I added employment verification through work-email OTP or private evidence, student verification, searchable company selection, company and university entity catalogs, and Resend-backed verification emails. Sensitive evidence stays in a private Supabase Storage bucket; privileged writes pass through Next.js server routes that verify Firebase ID tokens; restricted views/RLS and Edge Functions handle public reads, moderation, and aggregate company summaries.
03 / ImpactWhy it matters.
Turned LinkedOut from a social-product prototype into a trust-aware professional network with an explicit separation between authentication, internal identity, public pseudonyms, employment or student verification, and public entity pages. Reviews can carry verification signals without publishing the user's real name, login email, Firebase UID, or private evidence.