Privacy

Your account: your email address and, if you set one, a password. The password is stored only as a one-way hash, never as text anyone can read. If you turn on two-factor sign-in or add a passkey, the codes and keys that make them work are stored encrypted.

What you tell the camp: your name, handle, country, a photo if you add one, a short bio, what you are bringing, your answers to camp questionnaires, dietary needs, allergies, emergency contacts, and travel and driving plans.

Identity numbers: if you give an ID or passport number (the event needs it for tickets), it is encrypted before it is saved.

Camp records: dues and payments, which team you are on, and the notices the camp has sent you.

We do not use advertising or analytics trackers, and we do not sell or share your information for marketing.

If you choose “Continue with Google”, Google tells us your name, email address and profile picture. We use them only to sign you in and to fill in your account. We do not ask for, and cannot reach, anything else in your Google account (not your mail, contacts, files or calendar), and we never share what Google sends us.

Other members see the camp roster: names, handles, country, role, teams, and the bio you choose to share. They do not see your email, ID number or payments.

Captains, who run the camp, can see what they need to organise it, including your email. They can see an ID or passport number only through screens that record each time it is opened.

Emergency contacts, allergies and anaphylaxis are visible to captains and team leads, because withholding them in an emergency would be the worse failure. The screens that ask for them say so.

If a captain shares the camp’s site plan with neighbouring camps, the page they get shows how many people arrive on each day, never who, and none of the names or notes written on the plan. Members see the same counts on the plan.

When someone opens your ID number, safety details or a captain’s notes about you, that is recorded, so the question “who looked at my information?” has an answer.

Camp 404 runs on Vercel (hosting and private storage for photos) with its database at Neon. Email goes out through Resend, and phone notifications through Google’s Firebase. If you speak an answer instead of typing it, the recording is sent to Groq to be turned into text. If you report a problem, the report is filed as an issue in the app’s public code repository on GitHub with personal details removed, and you can choose to have Anthropic’s Claude tidy it up before it is filed. These services process the information only to do that job for us.

If you connect Claude to your Camp 404 account, Claude can read camp information on your behalf, limited to what your role in the camp may see. You approve the connection first, and you can remove it in Claude’s connector settings.

You can erase your account yourself: in Your profile → Edit profile, press “Delete my account”. Erasure deletes your sign-in (email, password, devices and passkeys), your questionnaire answers, dietary, safety, travel and driving details, and your photos. What stays is a placeholder named “Lost Cat” with a number, so the camp’s history (who was invited by whom, payments already made) still adds up without saying who you were.

You may also ask what we hold about you, or ask for a correction, by contacting a captain in the app or using “Report a bug”.