Your music stays private.
Bandroom’s optional analytics help us understand how people discover the app and which features help bands work together. You choose whether to participate. Opt-in is required in every region, and Bandroom works without analytics.
What analytics collect
After you accept, Bandroom sends explicit events to PostHog, hosted in the EU. These describe permitted public page visits, named sign-up buttons, guided demo progress and actions such as opening a workspace, viewing a feature, saving a record or starting recording playback. Guided demo events contain a fixed tour version and, for a viewed step, a number from 1 to 8. Reaching the end of the tour is not counted as using the product.
Campaign tags and external referrer hostnames can tell us how a public visit arrived. Private workspace, sign-in and invitation URLs are excluded. Random visitor identifiers and pseudonymous account and room keys connect related actions; analytics do not receive the underlying account or room IDs.
We do not send songs, lyrics, notes, email addresses, file names, audio or invitation tokens. We do not use session replay, automatic click tracking or form capture.
The public guided demo
Supademo loads only after you choose to explore the guided demo. It serves public, synthetic content about a fictional band. Supademo’s provider tracking is disabled for this demo. Loading the tour connects your browser to Supademo to deliver that content; it does not accept Bandroom analytics for you.
You can explore the tour without accepting optional Bandroom analytics, or use the locally hosted captioned video and transcripts. Bandroom sends demo progress events only while your analytics consent is accepted. Provider message titles, URLs and timestamps are excluded from those events.
Your choice and withdrawal
Use Analytics preferences at the bottom of any page to accept, decline or withdraw consent. Before acceptance, we do not store analytics visitor identifiers, campaign history or engagement state. A preference cookie remembers your choice.
Withdrawal stops future analytics collection and clears browser analytics context. It does not delete events already collected. If the server cannot confirm withdrawal, the preferences controls show a retry so you can finish that step.
To request deletion of past analytics, email benbooth493+bandroom@gmail.com. You do not need to include private music, notes or invitation links.
Retention and incomplete counts
Consented visitor attribution lasts 30 days. Bounded engagement guards last for the browser tab’s session, expire after 30 minutes of inactivity and reset with consent withdrawal or logout. Provider events are retained for one year; internal analytics metadata lasts no longer than the one-year reporting period.
Reports describe observed activity. Declined consent, blockers, service failures and missing campaign tags create gaps, so analytics cannot provide complete customer or rehearsal counts.