Privacy
Your songs are yours
Your songs are yours. The charts, lyrics, setlists and notes you keep in BandBinder are never sold, shared, scraped, or used to train AI models, ours or anyone else's. Only the members of your band can read what you share with them, and nobody else can read what you keep to yourself.
The full plain-language answer, including where your data lives and who can see it, is on the Your data page.
BandBinder is operated by Diligent Design and Consulting Incorporated, a British Columbia, Canada company, which is responsible for the data described on this page.
This page covers what BandBinder collects through the website, the app, and payments. This policy is kept up to date as the product grows.
The app
Notification access on Android is optional, is used only to control Spotify playback, and no notification content is read, stored or sent.
Windows, macOS, Linux and Android are available now, with iOS in early access. The app collects the following when you use it:
- Sign-in identity. BandBinder offers three sign-in methods, and we collect an email address plus a Firebase Auth user ID (uid) from whichever one you use. Signing in with Google gives us your Google account's email address. Signing in with Apple gives us the email address Apple provides, which is a private relay address ending in
@privaterelay.appleid.comif you choose Apple's Hide My Email, not your real one. Signing in with email (a one-time code) uses the email address you enter directly. This is used solely to authenticate you and to associate your library with your account. - Library backup and band sync. The songs, setlists, and other content you create in the app are stored in our cloud database so you can restore your library across devices and share it with band members. Only the data you explicitly create in the app is stored, along with minimal backup metadata (a per-device identifier, device name, and backup timestamp) needed to restore your library - no per-action usage telemetry (see "Operational usage signal" below for the one minimal exception).
- Optional reference links (Spotify and YouTube). If you attach a Spotify or YouTube link to a song, the app fetches that item's public title, artist, and artwork from Spotify or YouTube, and playing a YouTube reference loads YouTube's player. Those requests go directly from your device to Spotify or Google - so, as with visiting their websites, they see your IP address and the item requested, under their own privacy policies. This happens only for links you choose to add. We don't send them anything about you, and no Spotify or Google account is required by us or accessed by us.
- Terms acceptance. When you sign in or join a band, we record the version (effective date) of the Terms you agreed to and the time, on your account, or on your device only if you join as a guest.
- Marketing opt-in. If you check "Email me BandBinder news and offers" at sign-in or in Band Hub, we record that preference, the wording you agreed to and the timestamp. We then send you occasional emails with BandBinder news and offers. One offer is a discount code for a band plan: if you manage a band and none of your bands has a plan, that email arrives shortly after you opt in, or 10 minutes after you create a band while opted in, with one reminder a week later. It stops once one of your bands has a plan (at once when a band you manage buys a plan, within a day otherwise), and is never repeated after that. If you opted in when the box said product news only, we send you news only, never offers, unless you opt in again. Your address is held in Resend (our email provider) solely to send those emails, and is removed when you withdraw consent. You can withdraw at any time, and it takes effect within a day: in the app (open Band Hub, choose Manage (the … menu on smaller screens), then Email preferences; the same option is in the app menu, F2) or with the unsubscribe link in any of these emails. Contact support only if you can no longer sign in.
- Operational usage signal. When a signed-in app connects to our servers, it reports its platform (e.g. Windows or Android) and app version. We record the connection time and infer the approximate country from the request IP, then discard the IP. These fields are linked to your account so we can see which accounts are active, from which platforms and countries, and troubleshoot service issues. We record at most one connection every 15 minutes, not every action in the app. The most recent connection details remain while your account exists; the connection history expires after 90 days and is removed when you delete your account. We do not store a city, precise location, or raw IP address in this signal, or share it with third parties. This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com.
- Automatic usage analytics (Android, iOS, and macOS). On Android, iOS, and macOS, the app uses Firebase Analytics to automatically record a small set of Firebase's standard events - such as app opens (
first_open), session starts (session_start), how long the app stays in the foreground, and app or OS updates - together with the standard properties Firebase attaches to them: device model, OS version, app version, language, and an approximate location (country and city level) Firebase derives from your IP address. Firebase publishes the full list of automatic events and properties in its privacy and security disclosure. Everything is tied to a pseudonymous identifier Firebase generates for the install, not to your account, email, or any content you create, and we've turned off Android advertising ID collection. On iOS, BandBinder never asks for permission to track you, so iOS never gives it your device's advertising identifier. We don't define any custom events, and no event ever carries app content (band names, song titles, lyrics) or personal information. Firebase Analytics has no Windows or Linux implementation, so those two platforms use the separate desktop usage ping described next instead. - Crash reports (Android, iOS, and macOS). On Android, iOS, and macOS, the app uses Firebase Crashlytics to report crashes. A report carries the crash's stack trace plus the standard diagnostics Crashlytics collects automatically about the device and its state at the moment of the crash - things like the device model, OS version, app version, CPU architecture, free memory and disk space, screen orientation, whether the app was in the background, and whether the device is rooted or jailbroken. Firebase publishes the full list in its privacy and security disclosure. Reports are tied to pseudonymous identifiers Firebase generates for the install and the session, never to your account or email. We add exactly two fields of our own: which build you're running (staging or production) and a yes/no for whether you were signed in when it crashed. We never send band names, song titles, lyrics, your email, or any content you create: the error description the app hands to Crashlytics is reduced to the error's type (and, for Firebase and platform errors, a short error code), with the stack trace giving the location; the error's own message text is never sent, because that text could quote a chart line, a song title, or an email address. Reports go directly to our own Firebase project, which we control; we don't share them with third parties.
- Crash and error reports (Windows and Linux). Crashlytics isn't available on Windows or Linux, so there the app reports its own errors, automatically and on by default. When something goes wrong, the app waits 30 seconds and then sends at most one small report for that session directly to our own server: the type of each error (for example "StateError", plus a short error code for Firebase and platform errors), the places in the app's own code where it happened (file and line, such as
package:bandbinder/src/ui/song_view.dart:120), how many times each error happened, the app version, your platform and OS version, whether you were signed in, and the same random install id as the desktop usage ping. A report never contains songs, lyrics, chart text, band names, your account or email, file names or paths on your computer, or the error's own message text. Our server doesn't keep the reports themselves: it adds each one to counts per kind of error and then discards it. Those counts are deleted 90 days after that error was last seen. If you're offline, the report waits on your device and is sent the next time the app finds a connection, up to 30 days later. The Settings switch below turns these reports off too. - Turning analytics and crash reports off. Anonymous usage and crash reports are on by default. Turn off Share anonymous usage and crash reports in Settings, Privacy to stop reporting on this device. This includes the desktop usage ping below and the Windows and Linux crash and error reports above; queued reports are discarded. You can turn reporting on again at any time. Sign-in, sync and purchases continue to work.
- Desktop usage ping (Windows and Linux). Since Firebase Analytics isn't available there, on Windows and Linux the app instead sends a minimal ping directly to our own server when it opens: a random install id generated on your device (never derived from your hardware, and not tied to your account), your platform, a coarse OS version (e.g. "Windows 11", or on Linux the distribution name and version such as "Ubuntu 24.04", plus which desktop environment and display session type you use, such as GNOME on Wayland), the app version, and the time. It's throttled to at most once every 15 minutes, and if you're offline - Performance Mode is built to work fully offline, including through a whole rehearsal or gig - it's queued locally and sent the next time the app finds a connection, up to 30 days back. Our server looks up only the approximate country your request came from (never a city, address, or precise location, and never a location permission prompt) and then discards the IP address immediately - it is never stored or logged anywhere. We keep daily counts grouped by platform, country, and app version, never a record tied to one install or request.
App data is stored in Google Firestore and Firebase Cloud Storage, both in accounts we control directly. We don't share it with third parties; on Android, iOS, and macOS, the automatic analytics events and crash reports above go directly to our own Firebase project; on Windows and Linux, the usage ping and the crash and error reports above go directly to our own join-api backend (a service we operate, also in Google Cloud). Your device also connects directly to a few other services, each of which sees your IP address under its own privacy policy: the optional Spotify and YouTube requests described above; Google's Firebase Authentication whenever you sign in, plus Google or Apple if you sign in with them; our own release feed at download.bandbinder.app, which tells the app about updates and feature settings; and, when you search for or import a chart from an online source, that source, which receives the search text you type. You can request deletion at any time (see below).
Payments
Subscription payments are processed by Stripe. Your card details go directly to Stripe and never touch BandBinder's servers. What we store is your subscription status and Stripe customer/subscription identifiers tied to your account, used solely to operate your subscription. See Stripe's privacy policy for how Stripe handles your payment data.
On iOS, subscriptions can instead be bought in the app through Apple's in-app purchase, which Apple processes under Apple's privacy policy; your Apple payment details never reach BandBinder. What we store is your purchase history for that subscription - which plan you bought, when it renews, whether it will renew, and Apple's transaction identifiers - tied to your account and used solely to grant and maintain your subscription. We keep this record for as long as your account exists; nothing expires it on a timer. When you delete your account we remove its link to you, and only Apple's transaction identifiers remain, tied to no account, so a later renewal notice from Apple about that subscription is refused rather than re-applied. The transaction itself stays with Apple under Apple's retention.
Analytics
Cloudflare, which serves this website, provides a cookieless page-view beacon; we don't run Google Analytics, ad pixels, or cross-site trackers. When you arrive from a link in one of our product-news emails, our own server keeps one record per arrival with the date and time, page, and email and link labels, with no visitor identifier or IP address. Each record is deleted after 90 days; reports only ever show daily counts. To stop one source flooding the site's forms and endpoints, our server keeps a short-lived count of requests per IP address. That counter is used only for abuse prevention and expires after a few minutes. This is separate from the app's own usage analytics described above under "The app" (Firebase Analytics on Android/iOS/macOS, our own server-side ping on Windows/Linux).
Where this lives
The site is served by Cloudflare, which processes standard server logs to deliver it. App data is stored in Google Firestore and Firebase Cloud Storage, in accounts we control directly.
The service providers that process data on our behalf - Google (Firebase and Google Cloud), Cloudflare, Stripe, and Resend - do so only to provide their services to us, under data-processing terms that require them to protect it to at least the standard this page describes. The GeoLite2 country lookup runs on our own servers; no personal data is sent to MaxMind.
Manage or delete your data
Use the in-app account deletion flow to delete your account data. Support is for withdrawing marketing consent, or for people who no longer have app access. Before deleting your account, you can sign in to manage billing to review or cancel subscriptions you pay for. See the account deletion page for full deletion details. See the Your data page for what we keep and who can see it.
| Data area | Retention |
|---|---|
| Firestore point-in-time recovery | 7 days |
| Daily database backups | 14 days |
| Storage soft delete | 7 days |
| Login events | 90 days |
| Windows and Linux error counts | 90 days after that error was last seen |
| Stripe financial records | per Stripe's retention |
| Apple in-app purchase records | while your account exists, then unlinked from you; the transaction itself stays with Apple under Apple's retention (see Payments) |