1. Baila Core
  2. Manual
  3. What should you look for in a website or environment for your dance school?

What should you look for in a website or environment for your dance school?

Seven yes/no questions about the privacy and security of your website, app or environment, with what the law requires. Also useful if you don't choose Baila.

Are you choosing a website, app or environment for your dance school, or do you already use one? With these seven questions you can quickly see whether the basics are in order. Answer them with yes or no. The checklist also works if you don't choose Baila.

Do you have a data processing agreement with every supplier that stores data for you?

The answer should be yes: for every party that stores or processes student data on your behalf, you conclude a data processing agreement. Think of your registration system, your email program, your website builder and your accounting software. The GDPR requires you to record agreements with such parties about what they do with the data.

Is your data stored in the EU?

Preferably, yes: within the European Economic Area the same GDPR applies everywhere. Data may only go to a country outside it with extra safeguards, such as a decision by the European Commission that the country offers adequate protection, or standard contractual clauses. Ask your supplier where the data is stored and which safeguard applies if that is outside the EU.

Can you let someone view or delete their data when they ask?

That has to be possible, and in principle you respond within one month. A student may ask which data you hold about them, have a mistake corrected or have their data deleted. So know how to look up, export and erase one person's data in your tool.

Do you run payments through a payment service?

Do that instead of storing payment details yourself. A payment service processes the bank or card details; you only see whether payment was made. The less sensitive data you store yourself, the smaller the risk if something goes wrong.

If you post recognisable photos or videos of students, ask for consent beforehand. For children under 16, you ask their parents or guardians for that consent. Record who gave consent, so you can show it later, and remove images if someone withdraws their consent.

Is there a privacy statement on your site?

There should be one if you collect data from students or visitors. In it you explain which data you store, why, for how long and which rights people have. Write it in plain language and make sure it is easy to find.

Do you know what happens to your data when you stop using the tool?

Look this up before you start: the terms or the data processing agreement should say whether you get an export and when the supplier deletes the data. Without that agreement you run the risk of losing your member list when you switch, or of data staying for years with a party you no longer work with.

Why does Baila keep everything in one environment?

At Baila, registrations, payments, classes, tickets and communication are in one environment, with one set of agreements. That way a dance school, organiser or dancer does not have to stitch separate tools together themselves, and the risk stays as small as possible. And if you run into something, we help you out.

Want to know why these points matter? Read Do you know whether you use unsafe apps or websites in the dance scene?

Is something wrong in this article, or do you want to report something? Email us at [email protected].

All chapters · Baila Core