Your trust.
Our starting point.

01Information you provide

The information involved depends on the feature you use:

Sign-in

When authentication is connected, your school email and verification details are processed by Supabase to create or access your account. Multi-factor authentication uses an authenticator app when enabled.

Ratings and reviews

The demo lets you enter scores and review text. Those entries are not currently published or saved to a ratings database.

Recruitment profile

Fields such as your name, photo, year, major, GPA, bio, and interests update the preview in your browser. The current demo does not upload your photo or deliver your profile to selected chapters.

Contact

If you send an email, the team receives your email address, message, and anything you attach through your email provider.

02Browser storage and sessions

When sign-in is configured, the authentication client stores session information in your browser to keep you signed in. Ferda also uses temporary session storage to return you to the page you were viewing after verification.

The current ratings and recruitment demos do not implement persistent draft storage. Reloading or leaving the page may clear your entries, even if a demo confirmation says a draft was saved.

On a shared device, sign out when finished. Clearing site data removes locally stored session information; it does not delete an account or emails already sent to the team.

03What “anonymous” means here

Ferda’s rating interface is designed to show feedback without displaying a reviewer’s name or school email to other visitors. The current rankings are sample data, and live review publishing is not connected.

Anonymous display is not a promise of complete anonymity. An authentication provider processes account information when you sign in, and identifying details in a review or email can reveal who you are. Avoid including personal information in public-facing feedback.

04Services involved

When enabled, Supabase handles account authentication and related security information. Visiting a hosted version also sends normal connection information, such as your IP address and browser request details, to the hosting service.

The current app code does not include advertising trackers or third-party analytics. This describes the app’s implementation; hosting and email providers may keep their own operational logs.

The Contact page prepares a draft in your email app. It does not send a message automatically or store your contact-form text in a Ferda database. Your email provider processes the message when you choose to send it.

05Your choices and requests

You can browse the prototype without signing in and choose what to enter into optional fields. Only include information you are comfortable sharing.

For questions about an account, information you have sent, or a request to access, correct, or delete it, email the team with a privacy request. The team may need to verify that the request concerns your own information.

Account records and support emails are separate from browser data. The prototype has no automated account-deletion or retention controls, so requests concerning those records require team follow-up.

06As the project grows

This page describes the current implementation. It should be updated as live ratings, profile storage, chapter access, analytics, or other data-handling features are introduced. The date above identifies the latest update to this notice.