how your data is handled

every artist's data sits behind a wall enforced by the database itself, not by what the app chooses to show. one artist cannot read another artist's clients, bookings, photos or money, and that is checked by an automated test suite that has to pass before any change to the database ships.

sometimes we need to open your workspace to fix something. every one of those reads is written to a log with who looked and when. we can't look quietly.

our server logs and error reports carry record ids and error codes, not your clients' names, numbers or messages. that is enforced by an automated check that fails the build, and by a scrubber on the error reporting on both sides.

when an enquiry becomes a booking or a booking becomes money, we tell meta that it happened. contact details in those messages are hashed before they leave, and they only go where your client has consented and where you have a tracking connection switched on.

the connection uses a send-only key tied to your own meta account. it can write events and it cannot read anything back out. there is a switch to stop it, and a record of everything sent.

you sign in with a code to your email rather than a password. our own admin accounts need a second factor on top of that, on every screen that can reach a client's workspace.

there is a download-everything button. it gives you your contacts, enquiries, pieces, sessions, money records and your photos, whenever you want them. we do not sell your data or your clients' data to anyone, and we never will.

tell us and we'll fix it. email privacy@boneheaddigital.com. there is no bounty and we won't pretend there is one, but you will get a real answer from a person.

what we collect and how long we keep it is on the privacy page.