Privacy policy
Last updated 13 November 2026.
Who we are
Luneday is run by Willie Tech Ltd, company number 15837598, registered at 18 Gold Tops, Casnewydd (Newport), United Kingdom, NP20 5WJ. We are registered with the Information Commissioner's Office. Write to us about privacy at hello@luneday.com.
Our two roles
If you sign up to Luneday to run bookings, we are the controller of your account data. If you book through an organisation's Luneday page, that organisation is the controller of your booking data and we process it on their behalf. Their own privacy policy, linked from their page, is the first place to look. We help them answer any request you make.
Data we process
- Host accounts: name, email address, time zone, sign-in credentials (passkeys and two-factor secrets), session records, and the plan you chose when you signed up, if you chose one.
- Organisations: name, address on the web, custom domain, plan and billing status, business category, and the telephone number and price range a host chooses to show. The category, the telephone number and price range, and the words, address and areas a host publishes on their site, also appear on their public pages in a form search engines read.
- Bookings, on the organisation's behalf: the booker's name, email address, phone number, answers to the organisation's intake form, notes the organisation writes, attendance and payment status.
- Connected calendars: an encrypted token for each Google or Microsoft calendar a host connects, the busy times we read from it, and the events we write to it.
- Payments: subscription and transaction identifiers from Paddle for Luneday plans and text credit packs, and payment identifiers from Mollie for organisations' paid bookings. Card details never reach Luneday.
- AI briefs: when an organisation on a paid plan turns them on, a booker's intake answers are sent to Mistral AI to draft a session brief.
- Question suggestions: when a host asks for suggested questions, the event's details, the business category, the questions already on the form and the host's own bio are sent to Mistral AI. No booker answers are sent.
- Site drafts: when a host on a paid plan asks Luneday to write their site, the organisation's name, its business category and description, the area it covers, its events' names and lengths, the words already on the site and what the host types in the box are sent to Mistral AI to draft the words. No booker data, contact details, addresses or prices are sent.
- Text reminders: when a booker asks for a text reminder, their mobile number and the reminder's words go to PureSMS to send it. We keep the number, the time and the delivery status of each text, never its words. If a booker stops texts from an organisation, we keep their number on that organisation's stop list.
- Credit prices: when a host opens the Texts tab, their network address goes to Paddle to show pack prices in their currency.
- Newsletter consent: a host's yes or no, synced to MailerLite.
- Visitor counts: for Solo and Teams sites, a daily count of how many times each page was opened. No cookie, address or identifier.
- Contact forms: a message a visitor sends through an organisation's site, passed by email to the organisation. We keep only the sender's network address, for a short time, to stop abuse.
- Newsletter sign-ups: an email address a visitor enters on an organisation's site, sent to that organisation's MailerLite account.
- Security logs: the network address a booking attempt came from and a one-way hash of the email address entered, magic-link sends, and the bodies of payment webhooks.
- Partners: for an account in our partner programme, its commission rate, its referral link, and the payout details it gives us (a PayPal address, or an account holder and bank details), encrypted at rest. When someone signs up through a partner's link, the partner is stored on the new account. We keep a record of each commission a partner earns and each payout we make. When a partner tells us a customer came from them, we keep the email address and note they give us, and whether we confirmed it.
Google user data
When a host connects a Google account, Luneday receives the account's email address and ID, the names of its calendars, and the start, end and busy status of its events. With the host's permission it also adds bookings to calendars the host owns and creates Google Meet links.
To check a booking for clashes, Luneday may list the events in a calendar it reads. It asks only for each event's ID, times, status, free or busy setting and the host's own reply. It never reads titles, descriptions or guest lists.
We use this data only to show a host's free times, stop double bookings, put bookings in the host's calendar and add Meet links. We do not sell it, use it for advertising, or share it with anyone else. That includes Mistral AI and any other AI service.
We do not use Google user data to develop, improve or train generalised AI or machine-learning models.
Luneday's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
How we protect your data
All traffic to and from Luneday is encrypted in transit over HTTPS. The tokens for connected Google and Microsoft calendars are encrypted at rest with AES-256-GCM.
Luneday never stores the titles, descriptions or guest lists of events in a host's calendar. Busy times are held in memory for at most one minute and are not stored.
Hosts sign in with passkeys and enforced two-factor authentication. Access to the server and the data is by named account only, and the people with access are bound to confidentiality.
The server takes security patches nightly. The database is backed up nightly, with copies kept in a second data centre, and a restore is rehearsed every month.
When a host disconnects a Google account, we delete its tokens and revoke Luneday's access at Google. We keep the ID of each calendar entry Luneday wrote with its booking. For entries written to the disconnected account, we also keep that account's ID for up to a day after the booking ends, so that connecting the same account again can update or remove those entries.
Why we process it and on what basis
- To provide the service you or the organisation signed up for: contract performance.
- To keep the service secure and to stop abuse (rate limits, sign-in protection, fraud checks on payments): our legitimate interests.
- To send the newsletter, and to set analytics cookies on an organisation's page: your consent, which you can withdraw at any time.
- To keep accounting records: our legal obligations.
Cookies
On app.luneday.com we set the cookies needed to keep you signed in and to remember your light or dark choice. They need no consent and there is no banner.
On luneday.com, this site, we set no cookies. The how-to videos on the Help page come from YouTube. Nothing loads from YouTube until you press play. When you do, YouTube's player loads from youtube-nocookie.com, and Google may store data in your browser under its own privacy policy.
On an organisation's page (a luneday.com subdomain or their own domain) we
set nothing until you answer the cookie question. Your answer is kept in luneday_consent for six months. If the organisation has connected Google
Analytics or a Meta pixel and you accept, Google sets its _ga cookies (kept up to
two years) and Meta sets _fbp (kept three months). If you decline, nothing is set.
The "Cookie choices" line at the foot of the page lets you change your answer.
Processors and sub-processors
These companies process data for us, each for one purpose:
- Hetzner Online GmbH: our server in Nuremberg and database backups in Helsinki.
- Cloudflare: DNS for luneday.com, and the Turnstile bot check on booking forms and contact forms when it is switched on.
- Lettermint: the emails we send.
- Paddle: merchant of record for Luneday subscriptions and text credits.
- Mollie: paid bookings, under the organisation's own Mollie account. We hold payment identifiers only.
- Google: sign-in for connected calendars, Google Calendar (times and busy status read, your bookings written), Google Meet links, and Google Analytics on an organisation's page when the organisation connects it.
- Microsoft: Outlook calendar for hosts who connect one. The permission Microsoft grants can see event basics; Luneday reads only times and busy status, and writes the bookings you ask it to.
- Zoom: meetings for bookings on events set to Zoom, scheduled under the organisation owner's Zoom account. Zoom receives the event name and the booking's time and length; the join link goes to the booker.
- Mistral AI (France): AI session briefs, when an organisation turns them on, question suggestions from what the host writes, and site drafts when a host asks for one.
- PureSMS, run by divergent UK Operations Ltd (United Kingdom): text reminders, sent from data centres in the EU.
- MailerLite: newsletter consent for hosts.
- Meta: the Meta pixel on an organisation's page when the organisation connects it.
Google, Microsoft, Meta and Zoom process some data in the United States under their own terms and the UK and EU transfer rules, and each is involved only when a host connects a calendar or Zoom, an organisation connects analytics, or a visitor plays a how-to video. Paddle is in the UK, with a separate US company for customers who pay from the United States. Hetzner, Lettermint, Mollie, Mistral AI and MailerLite are in the EU. PureSMS is run from the UK, and processes texts in the EU.
Retention
- The network address a booking attempt came from and the one-way hash of the email address entered: one day.
- The network address a contact-form message came from: one day.
- Daily visit counts for an organisation's site pages: 13 months.
- Payment webhook bodies: their contents are redacted after 90 days.
- Text reminders: our record of each text, and its short link, 90 days. PureSMS keeps the text up to three months.
- A stop-texts request: until the organisation erases that client or is disbanded.
- Text credit purchases: for as long as the organisation exists.
- Partner payout records: six years, for tax. A partner's payout details: deleted once their partnership has ended and the final balance is paid.
- A partner's claim on a customer: if no account uses the email address it names, deleted 90 days after the partner made it. A confirmed claim is kept with the referral it made.
- Database backups: nightly copies kept 30 days and weekly copies kept 90 days, in Helsinki.
- A booker's data: erased when the organisation asks, from their Clients page. Bookings are anonymised and nothing that could identify the booker is kept. A copy of a booking in the host's own calendar is the organisation's to remove.
- Uploaded images and files: deleted when replaced, when the organisation is disbanded, and by a weekly sweep of any file no longer in use.
- A host account: deleted when you ask, from Account settings. Organisations you own must be disbanded or handed over first, and other memberships left.
- A host account with no organisation: kept, so you can join or start one again. Its Google and Microsoft calendar connections are disconnected 30 days after it was left with no organisation. If it also has no sign-in for two years, it is deleted, with a warning email 30 days before. An account in an organisation is never deleted for inactivity.
- Google data: when a host disconnects a Google account, or deletes their Luneday account, we delete its tokens, calendar choices and stored calendar names, and revoke Luneday's access at Google. Bookings already added to the host's calendar stay there for the host to remove.
- A disconnected calendar account: when a host disconnects a Google or Microsoft account, we keep the ID of each calendar entry Luneday wrote with its booking. For entries written to the disconnected account, we also keep that account's ID for up to a day after the booking ends, so that connecting the same account again can update or remove those entries.
- Everything else: for as long as the account or organisation exists.
Your rights
You can ask for a copy of your data, have it corrected or erased, take it with you, object to our processing, and withdraw any consent you gave. Booked through an organisation? Ask them first, and we will help them answer. You can complain to the Information Commissioner's Office in the UK, or to your own data protection authority in the EU.