Privacy policy

Who we are, and whose data this is

SingCommand is operated by Andy.Build ("we") and provides choir-management software to choral organizations ("choirs"). Two kinds of personal data flow through the service, with different responsibilities:

• Roster data — the member records a choir keeps in SingCommand (names, contact details, sections, attendance, dues, notes). The choir controls this data and decides what is collected; we process it only to provide the service to that choir.
• Account and billing data— the login accounts of people who sign in, and the choir's subscription records. We control this data.

If you are a choir member with questions about what your choir stores about you, your first stop is your choir's administrators — they control that data. We will assist them with any request.

What we collect

• Account data: name, email address, password hash (we never store passwords in the clear), or your Google account identifier if you sign in with Google.
• Roster data entered by choirs: whatever the choir records about its members — typically names, contact details, section assignments, attendance, dues, physical-copy assignments, photos, emergency contacts, and administrative notes. Choirs may record data about minors in their programs; the choir is responsible for having the appropriate consent to do so.
• Billing data: subscription status and invoices. Card details go directly to Stripe, our payment processor — they never touch our servers.
• Operational logs: standard request logs kept for security and debugging, retained briefly.

What we do NOT do

• We do not sell personal data, full stop.
• We do not run advertising or share data with ad networks.
• We do not use third-party tracking cookies. Public choir sites use cookieless, aggregate analytics; the only cookies we set are the session cookies that keep you signed in.
• We do not train machine-learning models on your choir's data.

Where data lives

The service runs on Cloudflare's global infrastructure; data is stored in Cloudflare's D1 database and R2 object storage, with encrypted backups. Payments are processed by Stripe. These are our subprocessors:

• Cloudflare, Inc. — hosting, storage, email delivery
• Stripe, Inc. — payment processing (subscriptions, dues, tickets)
• Backblaze, Inc. — encrypted off-site backups

How long we keep it

Roster data is kept for as long as the choir's workspace exists. When a choir is deleted, its data — database records and stored files — is purged permanently after a short grace window that protects against accidental deletion. A choir that stops paying is suspended, not deleted; its data remains intact and exportable.

Your rights

You can access, correct, export, or delete your personal data. Members can request erasure through their choir, which has built-in tools to honor it; account holders can contact us directly. Depending on where you live (including the EU/EEA, UK, and California), these rights may be backed by statute — we honor the requests regardless of geography.

Contact

Privacy questions and requests: hello@singcommand.com. If we change this policy materially, we will notify choir owners by email and note the change here.