Version 2026-10-13
Burnbase is provided by Captain Jack's App Factory in the Netherlands, registered with the Chamber of Commerce (KvK) under number 42136234. In this notice "we" means that provider. Our details, and a link to our registered address on the KvK register, are on the About page. You can reach us through the contact page.
We are responsible for Burnbase and for the data it holds. A camp's leads are responsible for how they use what their camp can see, under the rules in the terms. We have no data protection officer, because the law does not require one for a provider of our size. We will look at this again as Burnbase grows.
If we work with you, or may work with you, as an organiser, partner or other business contact, the privacy notice for business contacts covers that.
Everything you do in the demo at /demo (your persona, camps, roster, shifts, meals, packing lists, lifts, shared costs and any receipt photos you add) is stored only in your own browser (local storage). It is never sent to a server, stored remotely or shared. Use the "Reset demo" control at any time to clear it.
The app stores what you and your camps enter so that your camp can run on it. Where the table says there is no fixed period yet, we keep the data until we set one, and this notice will say so when we do.
Your account, profile and the camps you belong to
Why, and on what basis: To provide Burnbase, under our agreement with you (the terms)
How long: Until your account is deleted
Disability, allergies, diet and neurodivergence
Why, and on what basis: Only if you add them, on your explicit consent (see "Sensitive details" below)
How long: Until you clear them, or your account is deleted
Your emergency contact
Why, and on what basis: So the right people can reach someone if you are hurt or unwell
How long: Until you clear it, or your account is deleted
A camp's own records: arrivals, shifts, meals, program, packing, lifts, budget, shared costs, forms and payments
Why, and on what basis: To run the camp, under our agreement with each member
How long: As long as the camp keeps them. A camp's record of who paid what stays with the camp after you leave it
The version of the terms you agreed to and when, and your neurodivergence consent
Why, and on what basis: To show what you agreed to, which the law asks us to be able to do
How long: As long as your account exists
Sign-in sessions
Why, and on what basis: To keep you signed in and your account safe, under our agreement with you
How long: A session ends after 14 days unused, or 30 days at most. The record of an ended session has no fixed period yet
A log of changes to camp seats and memberships, and of every time someone opens an emergency contact or a bank account number in full
Why, and on what basis: To keep Burnbase secure and to find out what happened if something goes wrong, on our legitimate interest
How long: No fixed period yet
Invitations to people without an account
Why, and on what basis: So a camp can reach the people it wants to invite, on our legitimate interest (see "Email from camps")
How long: 60 days after the last invitation, or until you decline
A record that a camp email was sent, and whether it arrived, without your address or the message
Why, and on what basis: To know that camp mail works, on our legitimate interest
How long: No fixed period yet
Photos
Why, and on what basis: To show them where you or your camp put them, under our agreement with you
How long: See "Photos" below
Messages through the contact and feedback forms
Why, and on what basis: To answer you, on our legitimate interest in replying
How long: As long as the email is in our inbox
Your email address on the mailing list
Why, and on what basis: To send occasional updates about Burnbase, on your consent
How long: Until you unsubscribe
Usage analytics (PostHog)
Why, and on what basis: To understand how Burnbase is used and improve it, on your consent
How long: No fixed period yet
Counts of consent choices
Why, and on what basis: To know how many people accept or decline analytics, on our legitimate interest
How long: Hourly totals only, with nothing that identifies you
| What | Why, and on what basis | How long |
|---|---|---|
| Your account, profile and the camps you belong to | To provide Burnbase, under our agreement with you (the terms) | Until your account is deleted |
| Disability, allergies, diet and neurodivergence | Only if you add them, on your explicit consent (see "Sensitive details" below) | Until you clear them, or your account is deleted |
| Your emergency contact | So the right people can reach someone if you are hurt or unwell | Until you clear it, or your account is deleted |
| A camp's own records: arrivals, shifts, meals, program, packing, lifts, budget, shared costs, forms and payments | To run the camp, under our agreement with each member | As long as the camp keeps them. A camp's record of who paid what stays with the camp after you leave it |
| The version of the terms you agreed to and when, and your neurodivergence consent | To show what you agreed to, which the law asks us to be able to do | As long as your account exists |
| Sign-in sessions | To keep you signed in and your account safe, under our agreement with you | A session ends after 14 days unused, or 30 days at most. The record of an ended session has no fixed period yet |
| A log of changes to camp seats and memberships, and of every time someone opens an emergency contact or a bank account number in full | To keep Burnbase secure and to find out what happened if something goes wrong, on our legitimate interest | No fixed period yet |
| Invitations to people without an account | So a camp can reach the people it wants to invite, on our legitimate interest (see "Email from camps") | 60 days after the last invitation, or until you decline |
| A record that a camp email was sent, and whether it arrived, without your address or the message | To know that camp mail works, on our legitimate interest | No fixed period yet |
| Photos | To show them where you or your camp put them, under our agreement with you | See "Photos" below |
| Messages through the contact and feedback forms | To answer you, on our legitimate interest in replying | As long as the email is in our inbox |
| Your email address on the mailing list | To send occasional updates about Burnbase, on your consent | Until you unsubscribe |
| Usage analytics (PostHog) | To understand how Burnbase is used and improve it, on your consent | No fixed period yet |
| Counts of consent choices | To know how many people accept or decline analytics, on our legitimate interest | Hourly totals only, with nothing that identifies you |
Information about your health or disability, your allergies, your neurodivergence, and a diet that reflects a medical need or a belief is sensitive. All of it is optional. If you add none of it, you can still use Burnbase.
Neurodivergence. You choose who can see it when you add it. Choosing that audience and saving is your explicit consent, and we keep a record of it. You can take it back at any time by clearing the field, and it stops being shown straight away.
Disability, allergies and diet. We store these only because you chose to add them, and we treat adding and saving them as your explicit consent to store them and show them to the people listed under "Who sees what". You can take it back at any time by clearing the field, and it stops being shown straight away. Unlike neurodivergence, Burnbase does not yet keep a separate record of this consent, and does not yet ask whether a diet is for a medical reason or a belief.
Emergency contact. It is there so that, if you are hurt or unwell, a lead can reach someone for you. Tell the person you add that you have added them. In a real emergency we and your camp's leads may use it to protect your life or health.
Your profile has fields that every signed-in Burnbase user can see, fields your camps can see, and fields only the people responsible for you can see. Nothing on your profile is on the public web.
Every signed-in user sees your name, nickname, pronouns, photo, city, nationalities, whether you live nomadically, bio, links, languages, burn history and whether you are over 18. They also see each contact detail you set to everyone: your phone, your email or another contact method. Each is set on its own, and none is set to everyone unless you choose it.
Your camps see your gender, your age (worked out from your birthday, which itself is never shown), diet, allergies, skills, physical capacity, certifications, disability, and your phone and email. Each other contact method you add is seen by the audience you pick for it. "Your camps" means the people you share a camp with as members, the camp and joining leads of a camp you are a member of or applied to, and the people at a burn's organising camp who hold the burn members seat or lead it. Your note to your camps is seen by the first two of those. Your note to a burn's organisers is seen only by the third.
Only the people responsible for you see your emergency contact: the camp and joining leads of a camp you are a member of, and the burn members seat or the lead of the organising camp of your burn. Reading it in full is logged.
Neurodivergence is seen by the audience you chose: the people responsible for you (the default), the people at your burns' organising camps who hold the burn members seat or lead it, the members and leads of your camps, or every signed-in user.
Three kinds of page are on the public web, for anyone and for search engines: the list of burns and festivals that chose to be listed, a burn's profile, and a camp's profile. They show what a burn's organisers or a camp's leads wrote there, such as a name, description, photos, links and whether the camp is taking applications. No member, no roster and none of your profile is on them. Every other page needs an account, your own profile included, even when you share its address.
Photos are stored in the EU, with DigitalOcean in Amsterdam. Anyone who has a photo's link can open it without signing in, so only add photos you are happy for anyone with the link to see. When you remove or replace a photo, Burnbase does not yet delete the old file from storage. Ask us through the contact page and we delete it.
You sign in with Tonomy ID, which proves your email address to Burnbase and shares nothing else. The database and photos are hosted by DigitalOcean in Amsterdam. The website is served by Vercel. Email from Burnbase, camp mail and the mailing list included, goes through Resend. Analytics, with your consent, go to PostHog, hosted in the EU. The contact forms go through Web3Forms, and booking a call uses Google Calendar. Each of them processes data only to provide its service to us.
Transfers outside the EU. Resend, Web3Forms, Google and Vercel are companies based in the United States, and DigitalOcean and PostHog are owned by US companies although they keep Burnbase's data in the EU. Where data goes to the United States, we rely on the EU-US Data Privacy Framework for a provider certified under it, and otherwise on the EU's standard contractual clauses.
We never sell your data, and we make no decision about you by automated means.
A camp's leads can invite you by email, and a camp can email you when you apply, are accepted, are declined or join by link. Burnbase sends these from its own address through Resend, which processes your address and the message only to deliver them. The camp writes the words. It never sees your address through Burnbase unless you share it.
If a lead invites you before you have an account, they give Burnbase your email address and the name they know you by, so the invitation can reach you. We hold them to deliver that invitation, on our legitimate interest in letting camps gather their people, and the email tells you so. If you decline, the invitation is withdrawn, and your name and address are deleted unless another camp has also invited you. If you do nothing, they are deleted 60 days after the last invitation sent to you. From the same link you can also ask never to be emailed by Burnbase again. We then keep a fingerprint (a hash) of your address, so that no camp can invite it, and nothing else about you.
Some data reaches us from someone else: the name and email address a lead gives us to invite you, and the name, phone number and relationship of an emergency contact a member adds. We hold an invitation as described under "Email from camps". We hold an emergency contact for as long as the member keeps it, and show it only to the people responsible for that member. If your details are on Burnbase because someone else added them, you can ask us through the contact page to see them or remove them.
Burnbase is for people aged 16 and over. If you are 16 or 17, make sure a parent or guardian knows you use it. Camps and content marked as for adults are for people aged 18 and over.
Three places ask for something: the contact form, the feedback form and the email signup. All three are optional.
The contact and feedback forms pass what you type (your name and email where you give them, your message, and the event details you fill in) to Web3Forms, which delivers it to our inbox as an email. Burnbase stores none of it. We use it only to reply and, where you asked, to help you get set up. Email on the feedback form is optional; leave it out and we cannot write back.
The email signup passes your email address to Resend, which holds the mailing list. We use it only for occasional updates about Burnbase, on your consent, given when you press "Sign me up". You can withdraw it at any time with the unsubscribe link in any email, or by asking us, and the address is then deleted from the list.
If you book a call, the booking page (Google Calendar) collects your name, email and anything you add, so we can prepare for and hold the call. We keep it while the conversation is relevant.
Connections to Burnbase are encrypted. Bank account numbers are encrypted where they are stored. What each person sees is limited by their place in a camp, as described above, and opening an emergency contact or a bank account number in full is logged. The data is hosted in the EU. No system is perfectly secure. If a breach of your data happens, we tell the Dutch Data Protection Authority within 72 hours where the law requires it, and we tell you directly where the risk to you is high.
You can ask for a copy of what we hold about you, and ask us to correct it, delete it, restrict how we use it or give it to you in a form you can take elsewhere. You can object to what we do on our legitimate interest, and withdraw any consent at any time. Ask through the contact page. We answer within one month. If a request is complex, we may take up to two more months, and we tell you within the first month if we do.
Burnbase does not yet have a working button to download your data or delete your account. Until it does, ask through the contact page and we do it by hand. A camp's record of who paid what stays with the camp after your account is deleted.
If you are not satisfied with our answer, you can complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
With your consent, we use PostHog (hosted in the EU) to measure usage: page views, interactions such as clicks and navigation (with anything you type, the text on the page, and the codes and tokens in a link all masked), and product events like "a camp was created", "a shift was claimed" or "signed in". Product events carry only kinds, counts and choices (for example which door on the landing page was taken, or which starting template was picked), never names, text you wrote, amounts, or which camp or burn it was. We do not record your screen or sessions. PostHog runs as its own project for Burnbase. Without your consent, nothing is captured and no analytics cookies are stored.
Every page view sends one anonymous count to our own server, whatever you choose in the cookie banner. It records which choice was in effect (accepted, necessary only, or not decided yet) and whether the banner was showing. Clicking a banner button sends one more count, recording which button. Nothing else is sent. It tells us how much of our traffic the analytics below can't see, so a quiet week and a blocked week don't look the same. The count carries no identifier, no page address and no cookie, and it is stored only as running totals per hour, so it can't be traced back to you.
We do this on the basis of our legitimate interest in knowing how complete our analytics is. Nothing is stored on your device for it. Your IP address reaches our hosting providers the way it does for any web request; it is used only to deliver the count and is not stored with it.
On your first visit a banner lets you accept all cookies or keep only the necessary ones. Analytics cookies are set only after you consent. If you decline or later withdraw consent, those cookies are removed where technically possible. Signing in sets a cookie that keeps you signed in, which is necessary for the app to work. Your browser's local storage keeps your cookie choice, the demo, and whether the demo has already asked if you would like to use Burnbase. You can change your choice at any time: