Privacy choices for organizers

Organizers decide how findable an event is. They also decide how long personal data stays in the system. This guide is the practical version of the Privacy Policy.

What is public by default

The event page is reachable by URL as soon as the sign-up exists. Title, description, location text, dates, slot names, and remaining capacity are visible to anyone with the link. Do not put student last names, medical notes, or gate codes in the description field.

Public listing is off unless you turn it on. With it off, Search, the team page, and the creator page omit the event. With it on, those directories can show the title and a short summary. Details are still on the event page.

What stays with the organizer

Full rosters, contact details collected on the registration form, and dashboard analytics are for the team that owns the event. Treat that list the way you would treat a paper sign-in sheet: do not publish it, and do not export it into a random spreadsheet you later email to the whole group unless people expect that.

Accounts and deletion

Creating an organizer account stores name, email, and login method (password, Google, or Facebook). You can delete the account from Account Settings or the user deletion page. That removes your profile and associated personal data. If teammates still need the events, transfer or close them first.

Attendees who never created an account exist only as registration rows. Removing those rows, or using their unregister link, is how that data goes away.

Cookies and ads

Sign-in cookies keep organizers logged in. If ads are enabled on a public page, advertising partners such as Google may set cookies as described in the Privacy Policy. Login, registration, and settings pages are not ad surfaces.

A short checklist

• Write descriptions as if a stranger will read them, because a stranger with the link can.
• Leave public listing off for closed groups.
• Do not collect data you will not use.
• Delete test registrations and unused accounts.