Don't Get Campussed

Privacy policy

Last updated October 11, 2026. The short version: we keep only what's needed to swap kitchen jobs, we never sell it or show you ads, and we don't track you.

Who we are

Don't Get Campussed (dontgetcampussed.com) is a student-run website that helps Dublin School students trade, cover and swap kitchen job shifts, and keeps track of who owes whom. Only people with an @dublinschool.org email address can create an account. If you have questions about this policy, contact j_davies27@dublinschool.org.

What we collect

  • Your account: your name, your school email address, your class year (optional), and a password if you sign up with one. Passwords are stored scrambled (hashed) by our login provider. Nobody, including site admins, can read them.
  • A contact method, only if you add one on your profile (for example a dorm room or social media handle).
  • What you do on the site: the listings you post (shifts, days, meals and notes), the trades you take part in (who, which shifts, messages, confirmations), any problems you report, and the resulting ledger of shifts owed. Admin notes about disputes, penalties and corrections are part of that ledger.
  • If you choose “Continue with Google”: Google shares your name, email address, Google account ID and profile picture link with our login provider. We use your name and email to set up your account. We don't use the picture, and we get no access to your Gmail, Drive, contacts, calendar or anything else in your Google account.
  • Basic technical data: a login cookie that keeps you signed in, and the standard server logs our hosting providers keep for security and fixing problems (such as IP address, browser type and time of visit).

What we don't do

  • We don't sell, rent or trade your information. Ever.
  • We don't show ads.
  • We don't use analytics or tracking cookies. The only cookie keeps you logged in.
  • We don't send marketing emails. The only emails are sign-in emails (confirming your account, or a login link if you ask for one).

Who can see your information

  • Other signed-in students can see your name, class year and open listings.
  • The person you trade with can see the details of that trade and, once the trade is accepted, your contact method (if you added one).
  • Only you see your own balance and ledger history, apart from the people involved in each entry.
  • Site admins (a small number of students or staff who run the site) can see all accounts, email addresses, listings, trades and balances. They need this to resolve disputes and correct mistakes, and every change they make to the ledger is recorded with a reason.

Services we use

We rely on a few companies to run the site. They store or handle data only so the site can work:

  • Supabase: our database and login system (stores everything listed above).
  • Vercel: hosts the website.
  • Google: only if you choose to sign in with Google.
  • IONOS: our domain name, and may send our sign-in emails.

Your information may be stored on servers in the United States.

How long we keep it

We keep your information while your account exists. Trades and ledger entries are a shared record between two students, so we keep them to keep everyone's balances fair and correct.

Your choices

  • You can see and edit your name, class year and contact method on your Profile page at any time, and remove your contact method by clearing it.
  • You can cancel your own listings at any time.
  • You can ask us to delete your account by contacting j_davies27@dublinschool.org. We'll remove your account and personal details within 30 days. Where another student's balance depends on a trade with you, we may keep that trade record, without your contact details, so their balance stays correct.

Keeping it safe

The site only works over an encrypted connection (https). Database rules decide what each person can see, checked by the database itself on every request, and secret keys are kept on the server, never in your browser. No website is perfectly secure, but we try hard to keep only what's needed and protect it well.

Changes to this policy

If we change this policy, we'll update the date at the top of this page. If a change is important, we'll also mention it on the site.