Privacy and data protection
Last updated 18 September 2026.
This page covers two different things, and it says which is which throughout: this website, which is Callover's own; and a studio's deployment of Callover, which holds the bookings of the families who book with that studio.
The short version: this website sets no cookies and runs no analytics; a studio's bookings live in that studio's own database; we do not sell anybody's data; and Callover sends no marketing email to anyone at all.
Who we are, and what this covers
Callover is provided by Oleh Morshna, a sole trader trading as Callover, of 17 Alameda Place, London E3 2ZN, United Kingdom. Where this page says "we" or "us", that is who it means. The address to write to is in section 12.
The two roles
For the personal data of the families who book with a studio, the studio is the controller and we are the processor. The studio decides what is collected and why; we hold it and process it on their written instructions, which are their settings, their class information and their own wording. We do not decide anything about that data ourselves, and we do not use it for anything of our own.
For the details of the studio itself, the owner's name, the contact address, the correspondence with us and the record of what has been taken in fees, we are the controller.
For card payments, Stripe acts on its own account and not as our processor: the payment is made on the studio's own Stripe account, and Stripe holds the card details and the identity checks under its own agreement with the studio. Neither the studio nor we ever see a card number.
What we hold about you
If you are a studio using Callover: your name and the studio's, your contact address and phone number, the venue address, the settings you enter, your mail server details, the hashed password for your dashboard, and our email correspondence. We also hold the record of each fee taken from your bookings.
If you write to us from this site: your message, your address, and anything you put in the message. It is kept so that we can answer you and so that we have a record of what was agreed.
We do not hold your Stripe keys, because there are none to hold. Your deployment stores your Stripe account identifier, which is not a secret, and nothing else about Stripe.
Why we hold it, and the law we rely on: your details as a customer and our correspondence, because we need them to provide Callover under our contract with you; the record of fees, because the law on tax records requires us to keep it; and a message you send from this site, because we have a legitimate interest in answering it and keeping a record of what was agreed.
You do not have to give us any of it. Without your details we cannot set up or run a deployment for you, and without a message we have nothing to answer.
What your deployment holds
For each booking: the participant's first name and, for a children's class, their age; the payer's name, email address and, if given, a phone number; the class, what was bought and the figure quoted; the consents that were ticked, with the time each was given; any note the family typed; and where the booking came from, if the link carried that.
Then, as things happen: the waiting-list position and the times a place was offered and held; the record of a payment, whether it came from Stripe or was logged by hand; the register rows for each class date; and every letter the system sent, kept so the studio can read what a family received.
That is the lot. There is no tracking, no profiling, no advertising identifier, no analytics on a booking page, and nothing a family does is shared with anybody.
Who else touches it
Four companies are involved in running a deployment, and only the first two hold a studio's booking data on our instructions.
| Who | What they do | What they hold |
|---|---|---|
| Vercel | runs the booking page, the dashboard and the software behind them | the pages and the requests to them, including a short server log that can contain an address and a page name |
| Neon | provides the database each deployment writes to | every booking, waiting-list entry, payment record, register row and letter |
| Stripe | takes the card payments, on the studio's own Stripe account | the payment, the payer's name and email, and the card details, which nobody else sees |
| The studio's own email provider | sends the letters from the studio's own address | the letters themselves, in the studio's own mailbox, under the studio's own account with that provider |
Vercel and Neon are our processors, under their own data-processing terms. Stripe acts on its own account, as section 2 says. The email provider is the studio's own account and the studio's own contract: Callover hands the letter to it using the details the studio entered, and has no relationship with that provider at all.
We add no one else. There is no analytics company, no advertising network, no customer-support platform and no artificial-intelligence service with access to any of it. If that ever changes, this table changes first and every studio is told.
Where it is held
Each deployment's database and the software that reads it are created in the region chosen when the deployment is set up, which for a UK studio is London. The region for your own deployment is written into your handover note.
Vercel, Neon and Stripe are American companies with European operations, and their own staff and support systems may reach data from outside the United Kingdom under the safeguards their data-processing terms describe.
The safeguard each of them relies on for that, and how you can get a copy of it, is this.
Vercel applies the standard contractual clauses and, for the United Kingdom, the International Data Transfer Agreement, in Schedule 3 of its data processing addendum at vercel.com/legal/dpa.
Neon is part of Databricks and relies on the Databricks data processing addendum, which applies the standard contractual clauses together with the UK Addendum issued by the Information Commissioner, at databricks.com/legal/dpa.
Stripe relies on its Data Transfers Addendum, which provides for the Data Privacy Framework with its UK extension, the standard contractual clauses and the UK Addendum, at stripe.com/gb/legal/dta. Its data processing agreement can be downloaded at stripe.com/gb/legal/dpa.
We can send you a copy of any of them. Write to calloverapp@gmail.com.
How long it is kept
A studio decides how long its own bookings are kept, and can delete any of them at any time. We do not delete a studio's data on our own initiative while they are a customer.
Thirty days after a deployment is closed, its database is deleted, and so is the copy of it we handed over.
We keep our own record of a studio, the correspondence and what was taken in fees, for six years after they stop, because tax records have to be kept that long.
A message you send us from this site is kept while we are talking and for as long afterwards as it is useful to remember what was agreed, and then it is deleted.
How it is kept safe
Everything travels over an encrypted connection. The dashboard is behind a password, which is stored only as a hash, and the sign-in cookie is signed and lasts thirty days.
The one credential a studio gives us, the password for their mail server, is encrypted in their own database with a key that is not in that database.
Each customer has their own database. There is no shared table with two studios' bookings in it, so a mistake in one deployment cannot show another studio's data.
Callover is run by one person, not a security department, and the honest statement is this: the software is built so that the smallest number of secrets exist at all, and the ones that do exist are held by Stripe, by Vercel and by Neon rather than by us.
Getting a copy, and taking it out
A studio can ask for a copy of everything in its database at any time, and gets it as files it can open and keep. It is not a favour and it is not charged for.
The dashboard also shows every booking, payment, register row and letter on screen while the deployment is running, so nothing in it is hidden from the studio that owns it.
If a family asks a studio for a copy of what is held about them, the studio answers, and we help find it. Under the law the studio is the one who has to answer, and the month allowed for it starts when they are asked.
Rights, yours and the families'
You can ask us for a copy of what we hold about you, to correct it, to delete it, to limit what we do with it, to object to it, or to have what you gave us handed to you or to another provider in a form a computer can read. Write to the address in section 12 and we will answer within a month.
A family who booked with a studio has the same rights, and asks the studio, who is the controller of their data. We will do whatever the studio needs us to do to answer, including finding, correcting or deleting the records.
Where a right cannot be honoured in full, for example because a payment record has to be kept for tax, the answer says so and says why.
This site itself
This site sets no cookies, runs no analytics, and sends nothing you do here to anybody. There is no tracking pixel and no advertising tag on any page.
It stores one thing in your own browser: which colour scheme you chose, so the next page is in the same one. It never leaves your browser.
The pages load three things from other companies, and each of them sees your address and your browser as it serves the file: the two typefaces from Google Fonts, the motion library from cdnjs, and the smooth-scroll library from jsdelivr.
The sample booking page runs entirely in your browser on invented data. What you type into it is kept in your own browser's storage so the sample keeps working as you move around it, it is never sent anywhere, and the Reset demo button clears it.
Every name, email address, phone number and figure in the sample is fictional. No real family, child or studio appears anywhere on this site.
Complaints, and how to reach us
Write to calloverapp@gmail.com with anything at all about this page, and we will answer within a month and usually within a day.
That includes a complaint about how we use your personal data. You have the right to make one to us; we acknowledge it within 30 days, look into it, and tell you what we found and what we did.
If you are not happy with the answer you can complain to the Information Commissioner's Office, the UK regulator, at ico.org.uk, or by telephone on 0303 123 1113. You can do that without asking us first.
If your complaint is about a studio's own use of your data, the studio is the controller and is the one to ask, but we will pass a message on if you cannot reach them.