Prototype privacy information

Account and profile information

Registration sends your name, email address, password and chosen mentorship role to Supabase Auth. Supabase manages account authentication. Profile information supports mentorship discovery and connections; optional profile pictures are stored in Supabase Storage and can be accessed by signed-in members.

If you choose Google sign-in, Google and Supabase handle authentication and provide basic account identity details. The app requests only identity, email and profile scopes; it does not request Gmail or Google Drive access.

Please use test details for prototype evaluation. Do not enter national ID, passport or staff identification numbers in your profile, biography, skills or other free-text fields, or upload identity-document photographs.

Cookies and local storage

AlumniKonneQt uses cookies and browser local storage for operational, functional, and evaluation purposes:

• Strictly Necessary: Supabase authentication session tokens and security tokens required to keep you signed in securely and protect against cross-site request forgery, as well as preserving your consent decision (alumnikonneqt-cookie-consent).
• Preferences & Functional: Local storage used to preserve interface customizations across sessions, including your light or dark appearance preference (alumnikonneqt-theme).
• Analytics & Usability: Aggregated, privacy-preserving usage telemetry via Vercel Web Analytics to measure page navigation and platform stability. No personal identifiers or individual user data are recorded or shared.

You can review or change your cookie choices at any time: Manage cookie & storage settings.

Identity verification is not active

The membership fields on registration are a disabled design preview. They are not submitted or saved. Registration and email confirmation do not establish airline employment, association membership or verified identity.

Proposed association privacy notice

Your information is protected under the Data Protection Act and will only be used for alumni association purposes.

This is proposed wording for a future association-operated service, not a verified assurance about this prototype. A live service must identify its responsible operator and contact, explain its lawful purposes and necessary data, and establish access, correction, deletion, retention, security and incident-handling procedures before relying on this statement.

Those processes and the hosted safeguards have not been verified here. There is currently no self-service account deletion or data-rights request workflow. A research use also needs its own clear explanation and appropriate permissions; the proposed association-only sentence would not cover an undisclosed research use.