Privacy

This website collects nothing about you unless you type it in or buy a ticket. There is no analytics, no tracking pixel, no advertising, and no cookie banner because there are no cookies to consent to. There are exactly five things you can type in. One is a volunteer application, which comes to us. One is the form on /buy, which asks for a loyalty code if you have one, your name, email address, mobile number and addresses, an emergency contact’s name and phone number, which wristband you want, which camping zone, your shirt size if you choose Root Access, and any access needs you choose to write; the mobile number you give there also joins our drop texts. The third is the on-sale alerts box on the home page, on /texts, and on /buy while tickets are not on sale, which is a window onto our alerts provider's site rather than a form of ours — what you type there goes to them and never reaches this website. The fourth is our own text-alert form, on the home page and on /buy while tickets are not on sale, which saves your name and mobile number to our registration list in our database and texts them to us. The fifth is the page that opens your own order, from the private link in your order emails, where you can change some of what you told us at checkout. All five are covered below. If you buy a ticket, you pay on Stripe’s checkout page, not here, and Stripe tells us about the order afterwards — section 04 lists exactly what it sends.

Two things stay in your own browser. Neither is a cookie, and neither is sent to us on its own:

• bb-pack-checked — which items you have ticked on the packing list. That is a localStorage entry. It stays until you clear your browser data, and nothing is lost but your ticks.
• bb-checkout — the wristband, the pitch, the code and the shirt size you chose on /buy, so a checkout that did not go through can be tried again without a blank form. That is a sessionStorage entry. It lasts for this tab, it is cleared when the order goes through, and closing the tab removes it. The code and the shirt size reach us only when you submit the form. Your emergency contact and anything you wrote about access are not kept there.
• Nothing else. No analytics id, no visitor id, no counter.

One more, but never on your phone: the festival’s own gate phones keep the year’s guest list in bb-gate (section 04), and the gate page keeps a copy of itself so it opens with no signal.

The private link to your order (section 04) carries its key after the # in the address. Browsers never send that part of an address to any server; the order page reads it and sends it to us itself, to open your order. Like any address you visit, it is in your browser history, and nowhere else in your browser.

There used to be another entry, bb-reduce-motion, holding a reduce-motion preference; the control that set it has been removed and so has the key. Motion now follows your operating system’s own reduce-motion setting, which this site never stores or reads beyond honouring it.

The form on /volunteer asks for a fair amount, because staffing a weekend needs it:

• Your name, so we know who is on a shift.
• Your email address, to confirm your role and your call time.
• Your phone number. There is almost no signal on the land, so this is for reaching you before you drive up — a call time change, a gate change, weather.
• Your Discord username, if you choose to give it, so we can find you there.
• An emergency contact’s name and phone number, for someone off the land we can call if something happens to you while you are working.
• What you can help with and what you can commit to, your skills and experience, whether you could use your own car for runs, whether you already have a wristband, your shirt size, plus anything else you choose to tell us. Of these, only what you can commit to and the wristband question are required.

That form posts to this website, which emails your application to the festival inbox — where the organisers read it and reply — and sends you a confirmation. This website keeps no copy: it is not saved to our database or to any file, its logs record only whether an application went through, never what was in it, and no part of it is written to your browser. The confirmation says your first name and the roles you ticked, and nothing else you typed. Our email provider carries both messages. We use your application to staff the festival and for nothing else — not marketing, and not added to any list.

If you join the on-sale alerts list, you give your phone number or your email address to our alerts provider, not to us. The box you type it into looks like part of this page, and it is worth being exact about what it actually is: it is a frame showing our provider’s own signup, served from their site, running their code. What you type is theirs from the first keystroke. This website has no form that could take it, receives no copy of it, and could not read it out of that frame if it tried — browsers do not let one site read another’s.

Two things follow from it being their frame rather than our form. Loading any page that shows it tells them you were there — your IP address and browser, as with anything else you load from the internet — and inside that frame they run their own anti-spam check and their own analytics, which we do not control and cannot see. It appears on three pages only: the home page, /texts, and /buy while tickets are not on sale. Nothing else on this site loads anything from anywhere else unless you ask it to — the one thing that can is the playlist on the lineup page, described in section 07.

The other way onto that list is buying a ticket: we send the mobile number you give at checkout to the same provider, as section 04 describes. Reply STOP to any message and your number is removed immediately. How that list works.

Our provider keeps the record of when you signed up for as long as we are sending to that list, because carrier rules require us to be able to show that you asked. It goes when the list does.

If you use our own text-alert form, it works differently from that box: it is a form of ours, and it asks for two things: your name and your mobile number. It does not ask for an email address. Both are saved to our registration list, in the same database as the returning-attendee list described below, and that list is how we know to tell you when tickets go on sale. If your number is already on it, we keep the name we already hold — nobody can rename you by typing your number into this form — and the form says the same thing whether you were already on the list or not.

We also hand your details to our text-message provider, Twilio, which sends two texts: one to the festival organiser’s phone with your name and number in it, and one to you confirming the signup. The confirmation does not include your name. We do not email you from this form. This website does not write your details to its logs. Twilio keeps a record of the messages it sends.Reply STOP to any of those texts and we will not text you again; email us and we will remove you from the list and delete the organiser’s copy.

We delete volunteer applications from the inbox after the festival. If you want yours removed before then, email us and we will do it and confirm.

On /buy, one screen at a time, you type a loyalty code if you have one; give us your name, email address and mobile number; your billing address, and a shipping address if it is different; an emergency contact’s name and phone number; choose a wristband and a camping zone; give your shirt size if you chose Root Access; and — only if you choose to — write any access needs. A code is checked with Stripe as soon as you type it, so the page can show whether your order is free; nothing is kept from that check. The rest goes to this website’s server when you submit, which checks the code again and that there is a place left on the wristband and in the zone, and opens a Stripe checkout for that order with the code applied and your answers attached. The server keeps none of it at that step: your answers reach our records only if you then finish buying, below. Your name, address and emergency contact are never stored in your browser. The thank-you page greets you by your first name: it is passed in the part of the page’s address that never leaves your browser, and the page removes it from the address as soon as it has read it.

Checkout itself runs on Stripe, our payment processor, on Stripe’s own page. It shows the email address you gave us and asks only for your card details — and, if your card needs one, its postal code. When your code makes the order free, it asks for nothing but a click. Your card number goes to Stripe and never to us.

The mobile number you give at checkout also joins our drop texts. The checkout page says so under the box where you type it, with exactly what they are, and the same words are quoted on /texts. Once your order is recorded, our server sends that number to our alerts provider, Laylo, which adds it to the same alerts list as the signup box in section 03; from then on that list works as described there. The first message is Laylo’s welcome text. Reply STOP to it, or to any message after it, and you are off the list; that has no effect on your ticket. We send US numbers only, so a number from anywhere else is not sent. Orders placed before this notice was on the checkout page are not sent at all. After you pay, one more page on this site asks whether you have tickets for the two shows in Phoenix that a wristband does not cover — for each, that you have one or that you are not going — and saves your answers with your order.

When the payment goes through, Stripe sends a message to this website’s server, and that is when the order is written down. We keep, in our registration list:

• Your name and email address
• Your mobile number
• The street lines of your billing address, your city, state, and postal code, and your country
• The name on your shipping address, its street lines, city, state, postal code and country, which is where we post your wristband
• Your shirt size, if you chose Root Access (or gave one before 10 October)
• Your emergency contact’s name and phone number (and their email address, if you bought before 12 October, when we stopped asking for it)
• What you wrote about access, if you wrote anything
• The amount you paid
• The discount code you typed, if any
• Stripe’s reference numbers for the order
• When the order went through
• Which wristband and which camping zone your order included
• For each of the two Phoenix shows, whether you told us you have a ticket or are not going
• Which wording of the drop-texts notice your order was placed under
• Which year’s festival the order is for, and whether it was one of our own test orders

If you are already on that list — as a returning attendee, or through our own text-alert form — the order is added to your existing entry rather than a new one. We find it by the loyalty code you used, otherwise by your email address, otherwise by your mobile number. The name and mobile number you give at checkout replace the ones on that entry, unless another entry already has that number; the entry keeps its email address, and the one you gave at checkout is kept beside it.

When you finish the last step after paying — your answers about the two Phoenix shows — we email a confirmation to the address you gave at checkout. It is the record of the order: what you bought, what you paid, and what you told us about the shows. If you leave before that step, we send it anyway, from the same run as the reminders below, once the order is half an hour old, and it asks the questions you skipped. We note that we sent it, and when, so it does not go twice. That message goes through our email provider. It does not include your card number.

Changing your order. The confirmation email carries a private link to a page on this site that opens your order, and only yours. There you can change your billing and shipping addresses, your emergency contact, your shirt size, your access needs and your answers about the two Phoenix shows — and, when your order was free with a code that also covers the other wristband or camping zone and there is room in it, switch to that. Your name, email address and mobile number are shown there but not changed there; a person does that, through the Discord. The link works for whoever has it until the evening of the festival’s last day, so please do not forward the email. We do not store the link itself: we store a fingerprint of it that cannot be turned back into the link, when it was made, and when it was last used. When you save a change, your entry in the registration list is updated and we email you a note of what changed. The note names the wristband, zone, shirt size or show answer you chose, and does not repeat an address or your emergency contact. This website’s logs record that an entry changed and which kinds of answer, never what you typed.

We may email you about your order a few more times, each at most once. If an hour after buying you have not told us about the two Phoenix shows, and your confirmation did not already ask, we send a reminder with the link to your order page. If your order was placed before the order page existed, we send you its link. And in the week of the festival we send every buyer the arrival details this website does not publish — where the land is and how to get in. We note that we sent each, and when, so none goes twice. From then on, the button on your order page sends that arrival email again, to the address on your order and nowhere else; the page itself never shows the location.

Your gate pass. The arrival email, and your order page, carry a QR code: your gate pass. It is worked out from your order when it is shown, not stored, and it is a link to this site’s gate page with the pass after the #, so no server sees it. At the gate, the crew scan it, check your photo ID and check you in; we record when, on your order (checked in), and use it to give everyone who came a code for next year (section 06). Undoing a check-in made by mistake clears it. The scan is read on the gate phone: no picture is taken or kept. Because there is little or no signal on the land, each gate phone keeps the year’s guest list — each buyer’s name, wristband, pitch, shirt size for Root Access, whether they are checked in, and a fingerprint of their pass that cannot be turned back into it, and never an email address, phone number, address or emergency contact — in the browser’s storage, for a month after it was last loaded or until the crew clear it. Check-ins made with no signal wait on the phone until it has some. The gate page is opened only with a key that changes every year, and this website’s logs record how many check-ins arrived, never a name.

Your emergency contact is there so we can reach someone if something happens to you at the festival. Only the festival organisers see it, and we delete it a week after each event. We do not ask for a medical note or anything about your vehicle. The access field holds only what you write — the accessible camping area, a companion, a service animal — and you can say the same thing privately in the Discord instead. Stripe keeps its own record of the payment, including the addresses and the answers above, under Stripe’s privacy policy.

Order records are kept as long as tax and accounting rules require. Emergency contacts are deleted a week after each event. Volunteer applications are deleted after the festival.

If you are on the returning-attendee list we hold your name, your email address, your phone number if we have one, which years you came, the presale code we issued you, and when you pre-registered. We use it to send you that code, to tell you when the presale opens, to tell you when loyalty registration is open, and to remind you once, a week before sales close, if you have not used it. We also note which of those emails we have sent you and when, so that nobody gets the same one twice. When you buy with it, the order details from section 04 are added to the same entry rather than a new one, including each part of both addresses, the shirt size, the emergency contact, any access request and your answers about the two Phoenix shows, and which wristband you bought (the entry’s ticket type). Next year. At the end of each festival, everyone who came is added to next year’s returning-attendee list — everyone checked in at the gate (section 04), or, in a year whose gate checked nobody in, everyone who bought a ticket. Someone checked in up to a week later, on a gate phone that only then found signal, is added then. You get a new entry with your name, the email address you bought with and your mobile number, and a new loyalty code for next year, which we email you with next year’s dates. From then until next year’s sales close we may email you about that code — a week before the presale, when it opens, when general sale opens and a week before sales close — and stop as soon as you have used it. This year’s entry, and the order on it, stay as they are. Signups from our own text-alert form (§03) join the same list. That list, and the registration list in section 04, are the same database, run by our database host. One page of this site reads from it: the order page in section 04, which opens only the one order its private link belongs to and cannot look anyone up. See the loyalty page, which also explains why there is deliberately no form on this site that will tell anyone whether a given email is on that list.

Stripe, our payment processor; our email provider; our alerts provider, Laylo, which gets from us the mobile number you give at checkout; our text-message provider; the host of the database that holds the registration list; and the two services our code runs on — Vercel, which hosts this site, passes your order to Stripe and sends the order emails and the yearly ones in sections 04 and 06 and the volunteer emails in section 03, and GitHub, whose servers run the scripts that email the loyalty list, and the order emails when we send them by hand — each only what they need to do their job. Nobody else. We do not use advertising networks, we run no analytics of our own, and we have not embedded a map that phones home. There is exactly one third party whose code loads on this site on its own: the alerts signup described above, on the pages section 03 names. Everything else on every page is served from this site itself. If we ever add analytics it will be a privacy-respecting, self-hosted one, and this page will say so before it goes live.

The one exception you choose: the lineup page has our playlist on Spotify. Until you press Listen here it is drawn by this site and nothing loads from Spotify. Press it and Spotify’s own player loads in its place, from Spotify’s site, running Spotify’s code: Spotify then sees your IP address and browser, as with anything you load from them, and if you are signed in to Spotify in that browser they know it is you. What happens inside that player is under Spotify’s privacy policy, not ours, and we see none of it. Open in Spotify beside it is a plain link to the same playlist.

Email hello@beatsandbranches.com and ask for a copy of what we hold about you, a correction, or deletion. We will do it, and we will not make you explain why. If you ask us to delete an order we still have to keep the accounting record, and we will tell you exactly what is left.

This is an all-ages event and under-16s attend on a free ticket in an adult's order. We do not knowingly collect anything from a child directly, and a child's details reach us only as part of the responsible adult's booking.

If we change what we collect, we change this page in the same release — not afterwards. The date at the top is the last time that happened.