Web Hosting for Dance Studios

Consent that works when nobody is thinking about it

A consent policy that only works when the person building the gallery remembers it is not a policy. It is a hope. The version that holds up is boring and mechanical, and it takes an afternoon to set up.

1. Ask at registration, in writing, with a real no

   One question, three answers: no photographs at all, photographs but no name, photographs and first name fine. A yes or no checkbox forces families into a choice they do not want to make, and most tick yes because it feels rude not to.

2. Keep the answer where the photographs are

   The list of children who are not to be published needs to sit in the same place as the images, not in a drawer in the office. A shared document the person building the gallery has to open before they start is enough. It just has to be unavoidable.

3. Default to no names

   First names in captions are the thing families like most and the thing that carries the most risk. A photograph of a child is one piece of information. A photograph with a first name, a class time and a studio address is several, and they combine badly.

4. Publish a removal route and honour it fast

   A line on the gallery page saying who to email to have a photograph removed, and a promise to do it quickly. Then actually do it quickly. This is the single thing that keeps a mistake from becoming an argument.

5. Re-ask every year

   Families change their minds, children age, custody arrangements change. Consent collected in 2019 is not consent now, and rolling it forward silently is how studios end up publishing something a parent thought they had withdrawn.

One more thing worth saying plainly. Photographs taken from behind, from the wings, in silhouette, or of hands and feet at the barre carry almost all of the atmosphere and identify nobody. A studio that builds its public gallery that way, and keeps the identifiable recital photographs behind a login for enrolled families, has solved most of this without giving up anything visitors will miss.

The schedule page parents actually use

Parents arrive at your site with a very specific question. My daughter is seven, she has done one year of ballet, what can she take and when. They are filtering on age and level before they are filtering on anything else, and most studio schedule pages make that hard.

Things that make a schedule unusable

• The schedule is a PDF. It opens badly on a phone, it cannot be searched, and it silently shows last season because updating it means finding whoever has the original file.
• The schedule is a picture of a spreadsheet. Same problem, and a screen reader cannot read a word of it.
• Classes are named for their level only. "Ballet 3" means nothing to a family who has never enrolled anywhere. Put the age range next to it.
• The times are there but the term dates are not, so nobody knows whether the class has already started.

The version that works is unglamorous: real web text, grouped by age, with the level and the term dates written out. It costs nothing extra to host, it loads faster than the PDF did, and you can change a Tuesday class in a minute without opening design software.

If you offer a trial class or a first-class-free week, put it on the schedule page itself rather than only on a separate page. That is where the decision is being made.

Who should spend less than they are about to

If your studio teaches adults only, most of this page does not apply to you, and it is worth saying so directly rather than letting you buy protection you do not need.

An adult ballroom, salsa, tap or fitness-dance studio has no consent complexity worth speaking of. Adults can be asked once, on the spot, and they can say no for themselves. There is no gallery review process, no annual re-consent, no logged-in area for enrolled families. Your website is a schedule, a price list, a location and a contact form, and that is one of the lightest things anybody can put on a server.

• You do not need a private members area if there is nothing private to put behind it.
• You do not need extra storage. A studio site with sensibly sized photographs is measured in megabytes.
• You do not need a managed plan for a site that changes twice a year, at term boundaries.
• You probably do want backups you have actually tested, because the real risk to a small site is losing it, not being attacked.

Where spending more genuinely makes sense: you run classes for children and want a login area so identifiable recital photographs are not public at all, you run registration and payment on your own site rather than a platform, or you operate several locations from one website. Those are real reasons. Being busy in September is not one.