Privacy Policy
In plain language: we collect the minimum we need to run this, we tell you exactly what that is, and you can always ask us to delete it.
This is a good-faith, plain-language draft written to match how Brokehella actually works today. It is not a substitute for review by a licensed attorney in your state, and it must be reviewed before Brokehella collects government ID, health information, or any data from a jurisdiction with its own privacy law (the EU, UK, California, and others each have specific requirements this draft does not fully codify). Treat this as the honest starting point, not the finished legal instrument.
- We ask for as little about you as we can.
- Most of what you do here never leaves your own device.
- Our forms open your email app. Nothing sends until you hit send.
- We do not sell your data. Not now, not later.
- We do not run ad trackers on you.
- Want your data gone? Email us and we delete it.
- Under 13? This site is not built for you.
This list is a summary, not the rules. The full policy below is what actually binds us. If the two ever disagree, the policy wins.
The short version, with names attached, is on the Trust Center: every outside company your browser talks to, whether we use AI, what happens to a subscription when you cancel, and the things we have said we will never do.
What we actually collect today
Almost all of brokehella.com is a static site with nothing behind it.
Every form here, the Oath, the complaint intake, the Party Builder
send, the Reservoir give, the Pipeline signup, the Network signup,
composes an email and hands it to your own email client via a
mailto: link. Nothing is transmitted to us silently by any
of them.
There is one exception, and it is opt in. Signing in to the studio creates an account, held by Supabase, so your projects can follow you to another device. If you never sign in, nothing about you reaches a server we run. If you do, it holds your email address and the projects you chose to save, and nothing else. The Trust Center describes exactly what is stored, who can read it, and how to delete it.
Some things live only in your own browser, never
transmitted anywhere unless you choose to sign in and keep them, using
localStorage. This list used to say "two things" above
three of them, and it had missed more than that, so it is written out
in full here:
- Your Oath status and member serial (pledge.html)
- Your local Pledge Race ballot selections and Party Builder district picks
- Your best score in Container Stack (stack.html)
- A game of Hella Broke in progress, so a closed tab can pick up where it stopped: the board, the dice seed and what everybody has (
bh:hellabroke) - A game of Womp Womp in progress: the seats, every roll and the dice seed (
bh:womp) - Your Play record: coins, XP, your day streak and any streak save, how many times you have played and won each game and your best score, your last thirty results, the ids of recent games so one game is never counted twice, and which Kiosk looks you have unlocked and are wearing (
bh:play). Coins are not money and cannot be bought, sold or cashed out. The Game Hall has a button that clears it - For Party: on the big screen, the room it is hosting, so a refresh does not end the game: the code, the players' names, the game and the room's key (
bh:party:host); on a phone, which room it joined, its seat, the name and colour you gave and its key (bh:party:me). Both are forgotten after six hours. While you play, the room goes through a relay described in the Trust Center; nothing about it is stored there - Fits you saved in The Wardrobe: who, which pieces and what for, the last twelve (
bh:wardrobe). Nothing about them leaves this browser unless you share a link or a picture yourself - For The Culture Draft: the name you post under, the social handle you chose to show (if any), a random code this browser made for itself, whether you keep the shot clock on, the picks you have made so far in the day's crate (so a closed tab picks up where it stopped and you get one go a day), and your log of up to 200 crates you played, with the day, mode, record and picks (
bh:culture). If you post the day's crate to the leaderboard, Supabase stores your name, the social handle and platform you chose to show (if any), your five picks, their record and total, the day, the time your browser first opened that day's crate and whether the clock was on (so only timed crates count, and only within 15 minutes of opening), and a SHA-256 scramble of that random code (so one browser keeps one entry a day, and holds one name and one handle that no other browser can post under). Opening the daily crate sends that random code, the day and the clock setting, nothing else. The name, handle and crate are public on the board; the handle is shown as text, not a link, and is not checked against the platform. No email, account or location is sent. "Forget my name and log" on the page clears the device copy; email us to remove a board entry - For The Line: your best score on each beat and the timing offset you set (
bh:line) - For The Mixtape: the name you last put on the From line, so you do not type it twice (
bh:mixtape). A tape itself lives only in its link - For The Decks: the cue points you set on each track (marked by the file's name and size, or the Audius track number), what the page measured about each track so it is not read twice (its tempo, key, energy guess and mix points), three settings, the pitch range, quantize and the crossfader curve, and your keyboard shortcuts and controller mapping if you change them (
bh:decks). Your music itself is never copied or uploaded, and the crowd read and set list are not kept at all. LINE IN uses the audio input only while it is on, mixes it live and keeps nothing of it - For The Sample Maker: the sounds you save, as WAV audio with their name, length, what made them, a small outline of the wave and any tempo or key, and your kits of sixteen pads, all in this browser's IndexedDB (
bh-sampler); and which source tab and kit you last used (bh:sampler). Nothing is uploaded. The microphone is open only while RECORD is lit, and what it hears stays in the page until you save it - For Hum It: whether you last sang or beatboxed, the sound you picked, your tempo, and whether you chose a key yourself (
bh:hum). The microphone is open only while RECORD is lit; what it hears stays in the page, is turned into notes there, and is gone when you close it unless you download the file yourself. Nothing is uploaded - For The Decks, only if you bring a Spotify list: a one-time code and a random check value, for the minute you are away at Spotify saying yes (
bh:spotify, session storage). Both are deleted the moment you come back. The key Spotify then gives the page is held in the open tab and never written down; closing the tab or FORGET SPOTIFY ends it. Only track names are read - For Broke DJ: booth notes are not stored at all; they live in the share link you send. A 30 second clip is made in the page and saved only where you download or share it. Mix Match results go to your game record (
bh:play) like every game on the site - Whether you have already seen the container intro on the homepage, so it only plays once (
bh:intro) - For The Sound Map: the artists you marked WANT TO SEE (
bh:soundmap). It stays in this browser and is not counted anywhere. If you ask to be listed, the form sends what you typed to us through Netlify Forms; your contact detail is used only to confirm it is you and is never published - For The Crowd Room: nothing, on either side. A phone in the room is a random number made when the page opens; what it taps goes over a live line to the DJ's decks and is not written down anywhere. A DJ who opens a room sends the phones the titles and artists in their crate, and what is playing
- For Loophole: how many times you have visited, which of its secrets you have found, whether you have been up to Floor 4½, how many times you pressed the button in the Room of Bad Decisions, and the last four things that happened while you watched, so your next visit can say what you saw last time (
bh:loophole). It stays in this browser and is not counted anywhere - Whether you switched game sounds off (
bh:sound). The sounds themselves are made in your browser; nothing is downloaded to play them - Your DJ studio projects, patterns, theme and visual deck settings (dj.html), which also save to the browser's own IndexedDB
- Which hidden things on the site you have found (
bh:egg-state) - Where you stopped reading In The Yams, so a chapter can offer to pick up there, whether you finished it, and which characters you have followed through it (
bh:yams) - Your Brokedex: what you have collected, which pages you have visited, and your display preferences (
bh:brokedex). If you sign in on the Brokedex, what you have found is kept in your account instead, as described in the Trust Center. - The sargassum reports you log on The Wrack, by stretch of beach
- Your own picks in the cost model on the vote page
- A short log of errors this site hit on your device, at most fifty, which only you can see on Studio Health
Clearing your browser storage or using a different browser/device erases this. It is not backed up anywhere by us.
When a form is submitted and you send the resulting email, the data that reaches us is whatever you typed: name, email, phone (if you provide it), and the content of your message. We do not run analytics, tracking pixels, or third-party ad scripts on this site.
As more of the site gains a backend
Studio accounts were the first thing here to store anything about you on somebody else's computer. As other features follow, the Grants matcher, live Pledge Race voting, the Reservoir payment rails, verified Submissions, this page names the exact fields, the exact vendor and the exact retention period for each before the feature is published, not after. We will not quietly start collecting data this page does not describe.
This page previously said no such server existed. That stopped being true when studio accounts shipped and this page was not updated at the same time, which is the mistake the rule above exists to prevent. It is recorded here rather than quietly corrected, because a policy that edits its own history is not worth more than the last person to edit it.
Why we'd collect it
| Data | Purpose |
|---|---|
| Name, email | To reply to you, confirm your Oath, process a Reservoir gift, or respond to a complaint |
| Phone (optional) | Only where you choose to give it, for faster follow-up |
| Location (state/city) | Grants and civic matching only works if we know your jurisdiction, never collected beyond what you type |
| Demographic fields (age, income bracket, veteran/disability/student status) | Only ever optional, only ever to match you to real grant/scholarship eligibility criteria, never sold, never required to use the site |
| Submission evidence (photos, description) | To investigate and respond to a reported problem |
The toll for bots
Every request to brokehella.com passes a small program at the edge of the site (The Toll) that reads its user agent, the line every browser and bot sends saying what it is, to tell a person from an AI training crawler or a scraper. It keeps nothing about people. When a bot is asked to pay, or pays, Netlify's logs keep one line for a short time: the bot's name, the page, and the transaction on the Base blockchain if it paid. No IP address is logged by us. A bot's payment goes through Coinbase's x402 facilitator, which sees the payment, not you.
Who we share it with
Nobody, by default. We do not sell personal data. We do not have an ad network, a data broker relationship, or a marketing list we rent out. The only circumstances where data could leave Brokehella's hands:
- Service providers we choose e.g. a future database host (Supabase) or payment processor (Stripe) that processes data on our behalf, bound by their own security and privacy terms, never permitted to use your data for their own purposes
- Legal requirement if compelled by a valid subpoena or court order, described fully in our forthcoming Law Enforcement Request Policy
- With your explicit consent e.g. if you ask us to connect you with a referral partner in the Community Network
How long we keep it
Emails sent through this site live in our inbox until we act on them and archive or delete them, generally within 12 months. Once server-side storage exists, every table will have a stated retention period in this policy. If you ask us to delete your data, we will, within 30 days, except where we are legally required to keep a record (e.g. financial records for tax purposes).
Your rights
You can, at any time, by emailing info@brokehella.com:
- Ask what data we hold about you
- Ask us to correct anything inaccurate
- Ask us to delete it
- Ask for a copy in a portable format
- Withdraw any consent you previously gave
We will respond within 30 days. There is no fee for a reasonable request.
Security
See the Security Disclosure Policy for how to report a vulnerability. In short: HTTPS everywhere, security headers on every response, no plaintext storage of anything sensitive once a database exists, and encryption at rest for any field a person would not want printed on a receipt.
Children's privacy
Brokehella is not directed at children under 13, and we do not knowingly collect data from anyone under 13. If you believe a child has submitted information to us, email info@brokehella.com and we will delete it.
Regional notices
European users (GDPR)
If you are in the EU/UK, our legal basis for processing is your consent (for optional fields) or legitimate interest (replying to a message you sent us). You have the rights above, plus the right to lodge a complaint with your local data protection authority.
California users (CCPA/CPRA)
We do not sell or "share" personal information as those terms are defined under California law. California residents have the same access, deletion, and correction rights described above, and the right to non-discrimination for exercising them.
Contact
Brokehella · info@brokehella.com · Instagram @brokehella247