Your studio's data, said plainly
Where it lives, who can see it, how it leaves with you and how it is deleted. Only what is true today, including what is not built yet.
Where it lives
Your studio's records live in a Postgres database run by Supabase on Amazon Web Services in the United States, in Northern Virginia (us-east-1).
Every connection, from the website and from the iPhone app, is encrypted with TLS.
Stored data is encrypted at rest by Supabase's infrastructure.
danceflow.io is hosted by Netlify. The iPhone app talks to the database directly, not through the website.
No advertising or cross-site tracking cookies, and no third-party advertising or analytics kits inside the iPhone app. DanceFlow's own count of how the app is used stays in our database, and each studio and each person can turn it off.
Pages that answer without a sign-in, such as the booking page and the preview of an invitation code, are rate limited, and a studio’s email and texts have a daily ceiling.
Who sees what
One account per person, and what each person sees follows their role at your studio.
Owners and admins
Everything at their own studio, including money, pay and the activity log of who changed what.
Front desk
By default the schedule, the studio's students and their contact details, and taking payments. Reports, pay and the other money screens only when the owner gives that permission, one person at a time.
Teachers
The schedule and the studio's students, their own week and their own pay. The money screens, other teachers' pay and the activity log are for owners, admins and anyone the owner gives that permission.
Students
Their own lessons, packages and invoices. Never the notes staff keep about them.
Parents
The children in their own family, and nothing about anybody else's.
Other studios
Nothing. The database itself checks who may read each record, on every read, so one studio cannot reach another's.
Money
Card numbers never reach DanceFlow. When a studio takes cards, they are typed into Stripe's own page, and the studio, not DanceFlow, is the merchant of record.
The payment ledger cannot be edited or deleted. A wrong payment is voided with a reason, and the void stays on the record.
Owners and admins have an activity log of who changed what: roles, pay rates, packages, payments, invoices and settings.
Taking it with you
Owners and admins can download the whole studio in one Excel workbook or as JSON, from Settings › Studio: students, lessons, packages, money, what was signed, attendance, classes, leads, forms, gift cards and competitions, with a list of files.
An owner or admin can download everything the studio holds about one student, or one family, from that student’s profile.
A student, and a parent for their children, can download their own record from their profile, unless the studio has turned that off. The notes staff keep for themselves are not in it.
Message threads in a download are the downloader’s own. A private thread between a teacher and a student can be read by the two of them only, so it is not in the owner’s export either.
The student roster exports to a spreadsheet exactly as filtered on screen.
Reports export to CSV, Excel or PDF, from daily cash and liability to renewals, staff and marketing. Attendance and teacher earnings export to CSV.
Lessons follow you into Google, Apple or Outlook calendars through a private calendar feed.
Deleting
Anyone can delete their own account from inside the app. It asks you to type DELETE first, and it cannot be undone.
When a student comes off the roster, their past lessons, invoices and results keep their name, because the studio's books have to add up.
Deleting an account removes the person's details, not the studio's history: a former student is shown as “Deleted student” and their published competition results as “Withheld”. The payment ledger and signed waivers stay, because they are the studio's legal records.
Deleting an account also removes the person’s photo and the photos they sent, and takes their name, address and number out of the activity log. The log keeps the events themselves.
A studio owner cannot delete their account while they still own the studio. They hand it to another member of staff first, in Settings › Staff. Closing a studio is done by writing to us.
If DanceFlow goes down
What a studio still has while DanceFlow can't be reached, and what is not in place yet.
The iPhone app keeps each person's week on their phone: today and the next seven days, refreshed while DanceFlow answers. If DanceFlow can't be reached, the app shows that copy and the time it was saved. The front desk's copy also holds each student's phone, email and lessons left.
Lessons marked done, no-shows and notes in Lesson Mode are kept on the phone and sent when DanceFlow is back.
A calendar link puts your lessons in Apple, Google or Outlook Calendar, which keep them through an outage.
A studio can switch on a morning email of the day's lessons, so the day is in an inbox as well.
danceflow.io/status shows whether DanceFlow is answering right now, from a check DanceFlow runs on itself every five minutes.
Restorable backups of the database are not in place yet. They are being set up, and this line will change when they are. Until then, keep the whole-studio export from Settings somewhere safe.
What DanceFlow does not claim
Said here so that nobody has to ask.
A SOC 2 or ISO 27001 certification.
An uptime guarantee. The status page says whether DanceFlow is answering now, and promises nothing more.
A published backup and restore schedule. It will be written here when it is in place.
A registered company behind the service, or a signed data processing agreement. DanceFlow is run as an unincorporated business today, and the agreement on this site is a template.
NDCA sanction. DanceFlow is not NDCA-sanctioned.
Questions about your studio's data, or a request to export or delete it? Write to us, and a person answers.