
Draft — pending review.
When you book, the form asks for your name and email address. A phone number and anything you would like the reading to focus on are optional — leave them blank and nothing is stored in their place.
Alongside that, your booking holds the reading you chose, its date and time, the amount paid, Stripe’s reference for the payment, the moment you ticked the terms box and which version of the terms you saw. If a booking is cancelled we also record whether that was you, us, or a payment that was never completed.
Your card details are never collected here. They are typed into Stripe’s own payment form and go straight to Stripe; this site only ever sees their reference for the payment.
Almost all of it is simply what a booking is: we need your details to reserve the time, take the payment, send your confirmation and the Google Meet link, and let you move or cancel the reading afterwards.
Two things sit outside that. Stripe checks payments for fraud on our behalf, and old bookings are swept clean automatically so nothing personal is kept longer than it is useful.
Stripe takes the payment and checks it for fraud. Resend delivers your confirmation and any cancellation email, so it carries your name, email and booking details. Your booking itself is stored in a hosted Postgres database, and the site runs on Vercel, which keeps server logs. Those logs strip out your name, email, phone and notes before a line is written.
The reading happens on Google Meet. Only the meeting link is stored, and it is the same link for every booking — nothing about you is kept there by us.
There is no analytics, no advertising and no tracking on this site. The home page shows thumbnails of TikTok videos, which your browser loads from TikTok’s own servers; no TikTok script runs on the page, and nothing is sent to TikTok until you choose to follow a link.
Stripe publishes its own privacy policy.
12 months after your reading has taken place, your name, email, phone and notes are overwritten automatically and cannot be recovered.
The booking itself is not deleted — it is also the record of a real payment, so the amount, the Stripe reference, the status, the times and the reason for any cancellation stay. None of what remains identifies you.
Browsing this site and making a booking sets no cookies of our own. Two exist but will not reach you: one signs the owner into the admin dashboard, and one remembers a visitor who has been let past the holding page while the site is not yet public.
While you are on the payment step, your browser tab remembers which booking it is holding, so that reloading the page does not lock you out of the slot you just chose. It is cleared when you close the tab and never leaves your browser.
Stripe sets its own cookies inside the payment form to guard against fraud. Those are Stripe’s, described in their privacy policy above.
You can ask what we hold about you, ask us to correct it, or ask us to erase it. The “Manage my booking” link in your confirmation email lets you reschedule or cancel yourself; anything else is handled by hand, so please reply to any booking email and it will reach us.
If you are unhappy with how we handle your information, you can complain to the Information Commissioner’s Office.
If this notice changes, the date below changes with it. Last updated 10 September 2026.
Our booking terms are set out separately, on the terms page.