Security Architecture

Bandjama stores the technical details of a band's live show — musician rigs, channel assignments, per-song cues and console scene maps. This page describes how that data is handled today.

Accounts and authentication

Accounts are created with email and password or Google sign-in. Passwords are never stored by Bandjama in readable form; authentication is handled by our managed identity provider. Sessions are held in the browser and expire automatically.

Access control

Every record is protected by row-level access rules enforced in the database, not only in the app:

• Only a band's owner and invited members can create or edit that band's data.
• Invites are single-use secret tokens generated by the band owner and can be revoked.
• FOH playbooks are readable without an account by design, so a house engineer can open a band's cue sheet on show night without being onboarded.

Data in transit and at rest

All traffic to Bandjama is served over HTTPS. Application data is stored in a managed, encrypted-at-rest Postgres database operated by our infrastructure provider, with automated backups.

Exports

MIDI scene files and CSV recall sheets are generated in your browser from data you already have access to. Bandjama does not connect to, or remotely control, a venue's console.

What we do not collect

Bandjama does not process payment card details directly; if and when paid plans launch, billing is handled by a PCI-compliant payment provider. We do not sell personal data.

Reporting a vulnerability

Please report suspected security issues to info@bandjama.com with steps to reproduce. Do not publicly disclose an issue before we have had a chance to respond.