Privacy notice
familyeventsindex.co.uk — last updated 29 October 2026
Who is responsible for your data
Jack Wicks, who runs familyeventsindex.co.uk, is the data controller.
Contact: jack@familyeventsindex.co.uk
We answer data questions within one month, which is the time the law allows.
The short version
This site is a listing of family events. What you search for, the filters you set and the events you look at are worked out in your own browser.
Information we hold:
1. An event submission, if you choose to leave your email with it. 2. Your /swipe account, if you have one: your saved and binned events, events you added yourself, your profile and your term dates. We hold them so they follow you between devices. They are encrypted and filed against an identifier that is not your name or email.
We also count how many people saved each event. That is how we tell venues what families want, and those counts are not tied to anyone.
If you submit an event
The form at /submitevent asks about the event, and offers an optional email address so we can come back to you if something is unclear.
Lawful basis: legitimate interests — checking a listing is right before publishing it. Held in a Google Sheet. Deleted after 12 months.
If you have a /swipe account
Accounts are invitation-only during the beta.
| What we hold | Why | Basis |
|---|---|---|
| Your email address | To sign you in — there is no password, we send a link. Also to answer you if you write to us | Contract |
| Your saved and skipped events | The service itself | Contract |
| A display name you choose | So friends, family and groups can see who is who | Contract |
| Who your friends and family are, and which groups you are in | So you can match lists with people you accepted | Contract |
| Matching — the events you and a friend or family member have both saved | A core part of the service, on for every account and not optional. Worked out for one page view and never stored | Contract |
| Term dates, your home postcode, age bands | Filtering, and sorting what is on by how near it is | Contract |
| Your children's first names and ages, if you enter them | So the age filter and clash warnings work, on every device you use | Contract |
| How many people saved each event | To improve the listing, and tell venues what families want | Legitimate interests |
| Personalised suggestions | Optional recommendations | Consent — we ask when you first sign in, and you can change your mind any time |
| Telling your friends what you save | So they see it on their Feed | Consent — off unless you turn it on, on the You page under Account, and you can turn it off again whenever |
| Emails about news and upcoming events | Keeping you up to date with what is on | Consent — off unless you say yes, and you can stop them on the You page or from any one of the emails |
| Where to send a notification to a device you turned them on for | So we can tell you a friend has asked, somebody has sent you an event or accepted one, you have matched with somebody, a group you are in has news, or something in your diary is tomorrow, clashes, has moved or is still unanswered | Consent — off unless you turn it on, per device, under More |
| A note that we have already sent you a particular reminder | So a reminder about tomorrow, a clash or an event that moved is sent once rather than every morning until you deal with it. It is a one-way hash, not the reminder: nothing can be read back out of it | Consent — only exists while notifications are on |
We do not hold your real name, date of birth, precise location or payment details. Children do not have accounts.
About email. The consent card asks about news and a round-up of what is coming up, and those two are exactly what your answer governs. Both are off until you say yes, both are the same for everybody — nothing you have saved is used to decide what is in them — and saying no, or stopping them later, changes nothing else about your account.
Until 1 November 2026 that card also said "and service messages", which asked for something your answer never governed. The words have gone and everybody who answered the old ones is asked again.
A service message is sent either way, and your answer does not stop it. There are two: the link that signs you in, and a reply to a message you send us. They are the service you asked for rather than something you opted into, and if we could not send them you would have no way in and no way to reach us. So a no on that question is you declining the news, not declining your own support reply.
What we can and cannot see. Your saved list is encrypted and filed against a meaningless identifier. There is no screen, report or export that shows who saved what, and a stolen copy of the database would hold neither names nor readable events.
Telling your friends what you save. Off unless you turn it on. With it on, the friends and family you have accepted see the events you save, on their Feed — only things saved in the last fortnight, and only events they have not already saved themselves. Turn it off and they stop being told; nothing already sent is recalled, because there is nothing stored to recall — the Feed is built fresh each time it is drawn.
This is a different thing from matching, which needs no permission and is always on: matching only ever shows an event you and one of them have BOTH saved, so neither of you learns anything the other did not already know you knew.
A group never does this in either direction. A group shows what the person who runs it has put on its board, and it is told nothing about what its members save. If that ever changes we will ask you first.
Unless you send it to us. Because we cannot see your list, we cannot look into a problem with it either. The service can take a copy of your saved list, the events you added yourself, your profile including your children's names and ages, and your settings, along with a note from you about what is wrong — and send that to us so we can look at it.
There is currently no button for this anywhere in the app. The way in was removed on 29 October 2026 while that screen was rebuilt, so at the moment nothing can be sent and no copy of anyone's list can come to us by this route or any other. If it comes back, it will come back as a button you press yourself, and this notice will say so.
Whenever it is available, the rule is the same and does not change. It only ever happens because you pressed it. Nothing is sent automatically, not by an error, not by a crash, not by us asking. You get a reference you can quote, you can take it back at any time, and we delete it as soon as your problem is sorted — or within 30 days either way, whether we got to it or not. While we hold it, it is encrypted the same way the rest of your account is.
What is kept on your device
The index remembers one thing: the postcode locations it has already looked up, and only if you use the distance filter.
/swipe keeps nothing on your device. Your list, your filters and your profile live on your account. They are fetched when you open the page, held in memory while it is open, and gone from the device when you close it. The only thing left behind is the sign-in cookie.
That is why signing out needs no clean-up, and why a shared family tablet cannot show the next person what you saved.
If you turn notifications on, that device keeps two things. Your browser holds a subscription — an address at Google or Apple that points at this browser, and two keys that encrypt each message so that Google or Apple cannot read it. The browser holds it, not the page. We hold a copy, encrypted, so we have somewhere to send to. It is nothing about you and nothing you have saved; it is a way of ringing one browser.
Turning notifications off, or signing out, deletes both ends of it. So does deleting the app from your home screen, or clearing this site in your browser — and if it goes that way we find out the next time we try to reach it, and delete our copy then.
We also keep a note of which reminders you have already had. Some of what we send is a fact rather than an event — something in your diary is tomorrow, two things clash, an event has moved, nobody has answered an invitation — and a fact is still true the next morning. Without a record of having said it, we would say it again every day until you dealt with it, which is not a reminder.
That record is a one-way hash, mixed with your account's own identifier. It is not the reminder and the reminder cannot be read back out of it: it answers one question, "have we already said this exact thing to this person", and nothing else. We keep each one for 90 days, by which time the day or the event it is about has passed and it could never match again.
The app itself also caches two fonts and four small pictures, so it opens quickly. Nothing in that cache is about you, and signing out clears it.
It also means /swipe needs a connection. With no signal there is nothing to read, and a change made with no signal is not kept — it never reached your account, which is the only place it lives.
Full detail, including the single cookie, is in Cookies and storage.
Who else is involved
| Who | What for | What reaches them |
|---|---|---|
| Cloudflare | Delivering the site | Your IP address, as with any website |
| Holding the listings and the submission sheet | Any email left on a submission | |
| postcodes.io | Turning a postcode into a map position — your home postcode, and any you type into a distance filter | The postcode itself, with nothing about you attached |
| OpenStreetMap and cdnjs | Map tiles and the mapping library, when you open the map on /swipe | Your IP address |
| An email provider | None yet. Sign-in links are sent by hand from our own mailbox, and the weekly email will need a provider before it can be sent to more than a handful of people. We will name it here before it sends anything | Your email address |
We do not sell or share personal data with anyone, for any purpose.
How long we keep things
| Event submissions and any email with them | Up to 12 months |
| An account you delete | Immediately, and your email address within 24 hours — see below |
| Dormant accounts and their saved lists | 24 months without signing in |
| Sign-in links | 24 hours |
| Sign-in sessions | 90 days from your last visit. Opening the Hub restarts the clock; leave it alone for 90 days and the sign-in ends |
| A list you send us for support | 30 days, or sooner — deleted as soon as the problem is sorted |
| An event you added, or one put on a group board | 2 days after the last day it runs |
| An event you were sent by a friend | 2 days after the last day it runs |
| Where to send a notification to a device | 6 months without us successfully reaching it, or as soon as the browser tells us it has gone |
| A note that we have already sent you a particular reminder | 90 days |
| Counts of how popular an event is | Indefinitely — they identify nobody |
If you delete your account
There is a Delete my account button on the You page. Pressing it and confirming removes everything we hold about you: your saved and skipped events, the events you added, your profile, your term dates, your sessions, your friendships, any groups you made and anything you shared. That happens immediately and we check afterwards that nothing is left.
Your email address goes separately, within 24 hours. It lives in the one table that is keyed by the address itself, and the part of the service you are using has never seen an address — that is deliberate, and it is what stops your saved list and your identity being joined up in the first place. So it cannot reach that table. It leaves a note instead, carrying no address, and a scheduled job takes the last row within a day.
We do not keep a copy, an archive or a backup of a deleted account. The only thing that survives is the count of how many people saved a given event, which identifies nobody and never did.
If you would rather ask us than press the button, email us and we will do it by hand. Either way it is done well inside the month the law allows.
Your rights
You can ask for a copy of what we hold, or ask us to correct it, delete it, restrict it, or stop using it. You can withdraw consent for recommendations at any time without losing anything else. We respond within one month.
If you are unhappy with how we have handled your data, complain to the Information Commissioner's Office at ico.org.uk — though we would rather hear from you first.
Children, and automated decisions
This site is for parents and carers finding things to do with children. It is not aimed at children, children do not have accounts, and no advertising is shown to anyone.
If you enter your children's first names and ages, we hold them as part of your profile so that they follow you between devices. They are encrypted and filed against the same identifier as everything else, which is not your name or email. You can clear them on the You page whenever you like, and signing out removes them from the device.
Nothing here makes an automated decision about you. The optional recommendations suggest events; the service works fully without them, and from 23 October the answer you give is what decides. Until that date the question was asked and recorded and then not acted on, so somebody who said no was still having their saved list read to pick things out. That was a fault in our code rather than a change of position, it was found by our own audit, and it is fixed.
One other piece of wording was wrong for longer. The form for adding your own private event said "Private to this device". That was true when private events were kept in the browser and false from the day they started following you between devices, which is most of the time they have existed. It now says what actually happens: the event is private to your account, encrypted like the rest of it, and appears on every device you sign in on. Nothing about what we hold changed — the form had simply gone on describing an older version of itself.
If this notice changes in a way that affects you, we will say so on the site before the change takes effect.