Privacy and data handling

LaunchPad stores profile, company, job, and application data needed to run the recruitment workflow. Student profile details are saved in PostgreSQL through Supabase, and authentication is handled by Supabase Auth.

Passwords are not stored in plain text inside the application tables. For email-based authentication, Supabase stores hashed credentials in the managed `auth.users` schema. The public application schema only stores profile and business data needed for the product experience.

For Google sign-in, LaunchPad relies on Supabase OAuth. The application receives a Supabase session after the provider flow completes and then creates or updates an application-level profile record in the `profiles` table.

Row Level Security policies are enabled so users can only mutate their own profile data, and recruiters can only manage companies, jobs, and applications that belong to them.

Faculty reviewers and contributors can read the full technical explanation on the documentation page.