Privacy

What we collect

If you leave your address on the holding page, we store three things: the address itself, the time you sent it, and a note that it came from that page. That is the whole record.

We don’t ask for your name. While the site is this holding page there are no analytics, no advertising scripts and no third-party tracking on it at all, and we don’t build a profile of you.

Why we have it

To write to you once, when Maestro opens. That is the only use it will ever have. We will not sell it, rent it, share it with anyone else, or add you to anything you didn’t ask for.

Our lawful basis

Consent, under Article 6(1)(a) of the UK GDPR. You give it by submitting the form, and you can withdraw it whenever you like by emailing us — that costs you nothing and we won’t ask why.

A shared plan is not consent, and we won’t dress it up as one. We store it because the feature is the storage: two people cannot talk about a concert in a plan that keeps nothing. The basis is Article 6(1)(b) of the UK GDPR — processing necessary to do the thing you asked us to do — and we keep only what that takes.

So leaving a plan is not a consent you take back; it is how your part in it ends. The others stop seeing your Going and Went for that concert, and the plan is no longer yours to read. If you want what you wrote deleted, ask us.

Where it’s kept

In Amazon DynamoDB in Amazon Web Services’ London region (eu-west-2), in the United Kingdom. AWS processes it on our behalf and does nothing else with it. Access is limited to the people running Maestro.

How long we keep it

Until we open and write to you, or until you ask us to delete it — whichever comes first. If Maestro has not launched within 24 months of your signing up, we will delete the list rather than sit on addresses indefinitely.

When you share a concert

Sharing a concert with a friend opens a plan the two of you — or the few of you — can talk in. We store the plan itself: which concert it is about, which night once somebody picks one, who opened it, when it was opened and last touched, and a fingerprint of who is in it — that last one so sharing the same concert with the same people again reopens the plan you already have instead of starting a second one. For each person in it we store who invited them, when they joined, when they left if they have, and when they last read it.

And we store the messages: who wrote each one, what it says, and when it arrived. Joining, leaving, marking Going or Went and settling on a night each leave a line in the plan too — we keep those as the event and the person, not as a written sentence, so they can be read back in your own words. Messages are plain text, at most 1,000 characters. There are no attachments, and we don’t fetch anything a link in a message points at.

A plan lives in Amazon Aurora DSQL — a different database from the waiting list, in the same Amazon Web Services London region (eu-west-2), in the United Kingdom. It holds no copy of the concert: the title, the date and the programme are read from the catalogue each time, so a correction there reaches every plan about it.

Who can see a shared plan

The people in it, and nobody else. Each of them can read every message in it, and can see whether each of the others is going to that concert or went — for that concert, whatever the sharing switch on your Friends page says. That switch governs what all your friends see everywhere else; being in a plan is a separate, narrower yes. Concerts you have only saved are shown to nobody, in a plan or out of one.

Leaving a plan ends it for you: nobody in it sees your Going or Went any more, and the plan is gone from your list. The messages you already wrote stay where they are — the people still in it would be reading a conversation with lines pulled out of it.

Only people you are already friends with can be added to a plan, so nobody you haven’t accepted can reach you through one, and at most eight people can be in the same plan.

When a friendship ends

If a plan had just the two of you in it, removing each other closes it. Both of you keep the transcript and neither of you can add to it: it stays readable to both, and it accepts nothing further. That is meant — the conversation happened, and closing it is not the same as deciding it didn’t.

A plan with other people in it stays open. One friendship ending is not the group’s business, and nobody can be taken out of a plan by somebody else; if you would rather not be in it, you leave it yourself.

How long we keep a shared plan

Until somebody asks us to delete it. We have not set a retention period for plans and nothing deletes them on a timer, not even a plan about a concert that happened years ago — when we do set one, this page will say what it is before it starts.

There is also no button yet that closes your account and takes your messages with it. Until there is, email us and we will delete your account and what you wrote by hand, on the same timescale as every other request on this page.

Your rights

You can ask us for a copy of what we hold, correct it, delete it, restrict or object to how we use it, have it sent elsewhere, or withdraw the consent you gave the waiting list. Email privacy@maestroclassical.com and we’ll do it within one month, usually the same week.

If we get it wrong, you can complain to the Information Commissioner’s Office at ico.org.uk. We’d rather you told us first, but it’s your call.

Who we are

Maestro is the data controller for the waiting list and for shared plans. We’re a small team in Scotland building a calmer way into live classical music. Reach us at privacy@maestroclassical.com.