Privacy Policy

BETA VERSION: Eventable is in beta testing. This policy is an early version and will be revised as the service develops, and before it opens to everyone. If we make a change that matters we will tell you (see section 14). Last updated: 25 October 2026 This policy explains what Eventable collects, why, who sees it, how long we keep it and what you can do about it. It applies to hosts (people who make a site) and guests (everyone who visits or joins in on one). 1. Who we are Eventable is run from the United Kingdom by its founder, and is currently in beta. We are the controller of the personal data described here. Questions, or any of the requests in section 10: use the form at eventable.vip/contact or email [email protected]. When Eventable becomes a registered company we will put its name and address here. 2. What we collect from hosts - Your email address and, if you use a password, a scrambled (hashed) copy of it, so you can sign in. If you choose Google sign-in, we receive your verified email address and keep Google’s account identifier to recognise you next time. We do not receive your Google password or access your Gmail, Drive or contacts. - Whether you said yes to marketing emails (off unless you tick it), and records of agreeing to our Terms. - What you put on your site: the event's name, the guest of honour's name, the place, the dates, your wording, your cover photo and your settings. - Your orders and any promo code you used. - If you turn on phone notifications, the address your phone's push service gives us for your device. 3. What we collect from guests - A guest session cookie: a random number that lets the site recognise your browser, so your votes and reactions count once and you can take back your own photo. It is not your name. - What you post: dares, photos and their captions, advice, reactions, votes, ticks and reports, and the name you post under (or the made-up name we give you if you leave it blank). Once you have given a name on a site, it appears on everything you post there. - A record that you agreed to the Terms, which version and when. - If the guest of honour turns on notifications from the reveal link, the address their phone's push service gives us. 4. What we collect from everyone - The network (IP) address and browser type each request came from, and the time, to keep the service working and safe and to deal with abuse. We count how many things are posted from one address in a few minutes to stop automated flooding; those counts are held in memory and forgotten within minutes. - Simple visit counts. We do not use tracking or advertising cookies; visitors are counted with a code that changes every day and cannot be traced back to you. - The text of cards and dares you write. When a host saves a drink, dare or "Never have I ever" line for the party games, when a guest adds a card during a game, or when a dare is set on a site's board, we also keep a copy for ourselves. Before it is kept we replace any names in it (the guest of honour's, the players' and any other name we can spot) with a placeholder, and the copy has nothing attached that says which site or which person wrote it. We use these copies to check quality, to see what people like, and to write better starter cards. Our name-spotting is automatic and can miss an unusual name. - When you join in on a guest site, a check by Cloudflare Turnstile that you are a real person and not an automated program. It looks at signals from your browser and device; Cloudflare processes them under its own privacy policy. 5. Photos and AI Every photo uploaded to a guest site is sent to Anthropic, an AI company, which writes caption suggestions and checks the photo is safe to show. We do not send it your name. Under Anthropic's commercial terms, what we send is not used to train its models. Photos can show identifiable people: only post photos you have permission to share, and anyone in one can ask for it to be removed (section 10). 6. Why we use it, and our legal basis - To run your site and your account: performing our contract with the host. - To run a guest site for its guests, recognise your browser and show what you post: our legitimate interest in providing the service the host has set up. - To keep the service safe, check that the photo filter works, stop abuse and bots, and help prevent and detect crime: our legitimate interests, and those of the people in the photos. - To keep financial records: a legal obligation. - Marketing emails and phone notifications: your consent, which you can withdraw at any time. 7. Who can see it - Anything posted on a guest site can be seen by anyone with the link, and the link can be shared. - The host, and anyone they add to their team, can see and remove what is posted on their site. The host decides what goes on their site day to day. - Eventable, to keep the service safe: the platform owner can review uploads, including a sample of photos that passed the filter, photos the filter blocked, things that were reported and things a host deleted. This access needs a second sign-in step and every view is logged. - The companies that run parts of the service for us, only for that purpose: Hetzner (servers, in Germany), Cloudflare (network, security, the real-person check and backup storage), Anthropic (photo captions and safety checks), Resend (sending email), Zoho (our own mailbox) and Google, Apple, Microsoft or Mozilla (delivering phone notifications you turned on). Some of these are outside the UK; where they are, the transfer is protected by safeguards the law accepts, such as UK adequacy regulations or the UK's standard contract terms for international transfers. - If you choose Google sign-in, Google handles that sign-in under its own privacy policy. We exchange the information needed to verify your Google account. - The police or other authorities, when the law requires it or to protect someone from harm. If we find something that may be illegal, such as child sexual abuse imagery, we report it to the Internet Watch Foundation and the police and keep only what the law requires. We do not necessarily tell the host. 8. How long we keep it - A guest site is public until it locks (by default early the morning after the event), stays read-only for 30 days, and is then archived: the public page becomes a short "That's a wrap" page and only the host can still see and download the photos. 12 months after archiving, everything on the site is deleted. The host can archive or delete their site sooner. - Photos the safety filter blocks are kept for 30 days to check the filter is working, then deleted. - When a host deletes something from their site we keep a copy for 90 days so we can check for misuse and answer lawful requests, then delete it. We never keep anything its subject asked us to remove. - The network address, browser and time recorded with each post or report are kept for as long as the post itself. Other technical logs are kept for 30 days, warnings for 90 days and errors for 12 months, with network addresses removed after 90 days. - A draft site that is never published is deleted after about six months. - The anonymised copies of cards and dares (section 4) are deleted once nobody has written the same text for a year. Because they no longer say whose they were, deleting a site or an account does not remove them. - Backups of the database are kept for up to 30 days. - Records of agreeing to the Terms, and orders, are kept as long as the law requires (orders for at least six years). 9. Cookies and storage on your device We only use what the site needs to work: a sign-in cookie for hosts, the guest session cookie, and cookies Cloudflare sets to protect the site from attacks. Your browser also remembers a few things for convenience, such as the name you post under, that you have seen the welcome, and a party game in progress (cleared when you close the game). None of these are used for advertising. 10. Your rights You can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, and to move it. To have a photo of you removed, use the report button on the photo and choose "I'm in it": it is hidden straight away and the host decides whether it stays down. If the host puts it back, or you would rather deal with us, contact us and we will treat it as a privacy request. Hosts can delete their account at any time from My events: every site they own is deleted with it, and only payment records are kept, with the name and email taken off. Guests have no account; to have your posts removed, use the report button or contact us. We answer within one month. 11. Children Eventable is for adults. Do not use it if you are under 18. 12. Complaints If you are unhappy with how we handle your data, please contact us first. You can also complain to the Information Commissioner's Office (ico.org.uk). 13. The beta Eventable is in beta, so this policy is an early version and will be revised as the service develops and before it opens to everyone. During the beta we look more closely at how the service is used, and at errors, so we can find and fix problems, and we may email hosts with questions about their site or to ask for feedback. Those are service messages, not marketing. Sites and data created during the beta may be reset or deleted (the Terms explain), and we will try to tell hosts first. 14. Changes If we change this policy we will update it here and show the date it changed. When a change matters to you, for example if we start to use your data in a new way, we will tell hosts by email.