Privacy
What we store, and why.
This describes how the Fork website handles the information members give it.
What we store
- Account: your name, email address and a one-way hash of your password. We never store the password itself.
- Profile (all optional): phone, institution, department, batch, student ID, GitHub and LinkedIn links, and a short bio.
- Username: a public handle you choose. Other signed-in members can find you by it, and see your name beside it, so that a team leader can invite you to a team.
- Profile picture (optional): one small image, visible to you and to Fork organisers.
- Registrations: which events you registered for, when, and whether you attended.
- Sessions: a record of each device you are signed in on, so you can sign them out.
- Contact messages: what you send through the contact form.
Who can see it
- Your profile is visible to you, and to Fork organisers with administrator access, for running events you register for.
- Signed-in members with a confirmed email can look up your username and name. Teammates see the usernames and names of the others in their team. Nothing else about you is shown to other members.
- Nothing about members is shown to the public.
- Sensitive administrative actions, such as exporting a registration list, are recorded.
Cookies
One cookie keeps you signed in. It cannot be read by scripts and is not used for tracking. There are no advertising or analytics cookies.
We email you to confirm your address, reset your password, confirm event registrations, and tell you if an event you registered for is cancelled or moved. Emails are delivered through an email provider and may show the provider's address as the sender, under the name Fork.
Your choices
You can edit your profile, download a copy of your data, or delete your account at any time from your account page. Deleting your account removes your profile and anonymises past registrations.
Questions
Use the contact page.