FancyGoing? / Your information
Your privacy.
This notice explains how FancyGoing? uses information in its London events diary. You can browse events and read this notice without creating an account.
Last updated: 21 October 2026
Who to contact
For questions about this service or your personal information, contact FancyGoing? at hello@fancygoing.com.
Information we use
When you create an account, we keep your member ID, first name, email address and sign-in information. Your profile includes a username and can include your date of birth, gender and optional description, phone number, home postcode, travel preference, interests and profile photo. Valid profile edits save automatically; unsent drafts stay only in the open page.
Your date of birth stays private and is used to calculate your age accurately for adult eligibility and age-related event preferences. Existing age-only profiles stay unchanged until you supply a date of birth.
Optional discovery preferences let you show or hide LGBTQ+focused and gender-specific events, exclude confirmed age restrictions and apply your chosen travel-time limit. These are private choices about listings, not a declaration of your identity. We keep them with your profile so they work when you sign in again. You can change them in Profile → Preferences → Advanced options or temporarily pause them in Filters. We do not share these preferences with other members or use them for advertising or analytics.
We also store your event picks, hidden events, friend connections and requests, invitation settings, private and event-chat messages, read status, notifications, source suggestions and any reports you submit. We use these to show relevant events, sync your choices, help you plan with friends, deliver messages and operate and secure the service.
Personalised event ordering uses your recent saves and hidden choices to learn broad activities such as walking, games or music. It keeps only approved activity labels, event IDs, current choices and the time you made them, for up to 180 days and at most 2,000 recent events. Saves are a strong signal; hiding affects similar activities only after three different hidden events share an activity. These signals fade with a 60-day half-life. Removing a save or restoring an event reverses its effect, and hidden events take priority over saved ones. We do not reconstruct older decision dates or learn sensitive traits, dating or political preferences, demographics, places or contacts from these choices.
This activity history and its recommendation summary are private to your account and are not shared with members, used for advertising or added to visit analytics. In Profile → Preferences you can turn personalised ordering off or reset its history. Turning it off stops new learning and ignores remembered signals and your profile-interest ranking; changing an event while it is off clears any remembered signal for that event. Your explicit event filters still apply. Reset keeps your saved ideas and hidden choices. Signed-out browsing keeps its temporary learning only in the open page.
Message notifications are optional. If you enable them, we store this browser’s push subscription, a random device identifier and the chats you choose. Your browser’s push provider delivers encrypted alerts; alerts do not show names or message text. Turn off an individual chat inside that chat, or this browser from the Messages menu. Signing out disconnects this browser’s alerts. On iPhone and iPad, notifications require opening FancyGoing? from the Home Screen.
What other people can see
Your personal saved ideas are private. A friend connection does not share your saved list. Linked friends can see your chosen name and username. Email, phone, home postcode, date of birth, age, gender and other private profile fields are not shown to other members. Exact email or phone searches work only when you enable them; search results do not reveal those contact details.
Private chats are available to the connected friends. Verified signed-in members can read and post in available event chats and see the names used there; saving the event is optional. Public event information may include pick counts and, for sufficiently large groups, broad age and gender summaries.
A shared plan contains only the ideas explicitly added to it. Anyone with its invitation link can read its title and current public event facts, so avoid personal details in the title. Joining is a separate choice: it shares your chosen name, interest answers, arrangement responses and messages with current and future joined members. It does not connect you as friends, save a personal idea or confirm attendance. Invitation previews do not show member names, answers or conversations. Replacing an invitation stops new joins through the old link; existing members keep access until removed or they leave.
Connect uses your profile username, or your first name when no username has been added. If you add a profile photo, it is visible to members and appears blurred to visitors who are not signed in. Without a photo, it shows a silhouette. People suggestions use only the introduction, interests, broad area, outing preferences and availability you explicitly share. Your exact age, postcode, travel settings, saved ideas and private discovery preferences are not used to explain or rank these suggestions. You can switch off directory suggestions without losing access to Community or Messages.
Community discussions, replies and their displayed names are public and may appear in search engines. Avoid sharing private contact details or locations in public posts. Likes, followed discussions, bookmarks and read positions are stored to support your account; your bookmarks are private. Reports and held contributions are excluded from public pages and notifications. Private messages, shared-plan conversations and historical circle chats remain separate from Community. Requests to connect require relevant shared context; private conversation starts after both members agree.
New accounts are not automatically connected to the administrator. Existing friend connections remain until you remove them. The service administrator can access stored information to operate the site and address reports.
Google sign-in
If you choose Google sign-in, we verify basic identity information from Google, including your Google account ID, name, email address and its verification status. We retain the account ID connection and the name and email used for your FancyGoing? account. We use this information to create, secure and sign in to your account, and do not use Google account data for advertising or sell it.
We do not request access to Gmail, import your Google profile photo, or retain Google ID, access or refresh tokens. Choosing Google sign-in can connect or complete an existing FancyGoing? member account with the same email only when Google confirms current email ownership through Gmail or Google Workspace and there is no conflicting Google connection. Other email providers require you to sign in to FancyGoing? first and explicitly connect Google in your profile. Connecting Google preserves your existing account and saved information.
Google handles its own account sign-in and receives connection information when its sign-in service loads or is used. See the Google Privacy Policy and the Google API Services User Data Policy, including Limited Use requirements.
Location and external services
Near me asks your browser for location permission when you choose it. The diary uses those coordinates in the current page and does not save them to your account. Map tiles come from OpenStreetMap; tile requests reveal the map area viewed and normal connection details.
Near home uses your saved postcode. Your browser sends postcodes to Postcodes.io for approximate postcode-centre coordinates, and origin and venue postcodes plus the event date and time to TfL for journey estimates. If you choose Google Maps directions from home, the home postcode and destination are included in that link.
The site is hosted by IONOS. Hosting and email delivery services process information needed to serve the site and deliver account emails. External maps, Google sign-in and organiser or booking websites handle their own services and privacy practices. Any booking takes place with the organiser.
Cookies and security
To reduce repeat loading, this browser can remember up to 128 public event IDs you opened or selected. Each signed-in account and guest use have separate caches. Clear browser storage to remove these remembered IDs.
Sign-in uses WordPress session cookies. Google sign-in also uses a secure, temporary browser cookie and a one-use challenge that expires after ten minutes. Browser storage remembers hidden events while signed out, and temporarily keeps friend invitations and pending location choices. Signed-out saved ideas stay in this page’s memory for this visit, for at most 24 hours. During email verification, the selected public event, date, collection, shared-plan invitation token or up to eight idea IDs can accompany the verification request within its original 24-hour expiry, so you can return in another browser. Verification signs you in; keeping saved ideas or joining a shared plan still requires a separate choice. You can clear browser storage through your browser settings.
Connections use HTTPS. Passwords are stored as hashes; email verification and reset links contain secret, expiring tokens, so keep those links private. Messages are stored on the server and are not end-to-end encrypted. Abuse controls use hashed IP, account or email identifiers. The hosting server also receives normal request details, such as IP addresses and browser information.
Visit statistics, optional analytics and emails
Google Ads measurement is a separate, optional setting and starts off. When configured and you enable it alongside detailed analytics, Google's tag can use advertising cookies and receive a completed, verified new-account event with an opaque deduplication code. It also receives ordinary connection information, such as IP address and browser information. We do not send your name, email, profile, location or messages, use enhanced conversions, or enable advertising personalisation. Google sign-in does not enable this choice. You can withdraw it in the footer's Analytics settings; future Google measurement stops. Information already received by Google is handled under the Google Privacy Policy. Enabling measurement is never required to browse, join or make plans.
The private Growth dashboard also shows aggregate account creation and verification counts from our operational account records. These totals are separate from opted-in visit attribution and contain no contact details.
We collect basic first-party visit statistics to improve FancyGoing?. These count visits, visible browsing time and quick exits by broad source, such as search or social media. They do not use a persistent visitor or member identifier, and the statistics records do not store IP addresses, full referring URLs, contact details, profile information, locations or message contents. The admin, flagged test accounts and obvious automated browsers are excluded. We do not share these basic measurements with advertising platforms.
A short-lived visit record combines page activity until thirty minutes without activity. A secure thirty-minute cookie and a separate permission record prepare that visit before activity is recorded; they do not link it to any other visit. Turning statistics off revokes its permission so delayed requests cannot recreate it. Denied permissions are removed during bounded cleanup after outstanding cookies and proofs expire, with a short safety margin. Browsers that cannot safely coordinate visit preparation across tabs are not measured. At the next processing step after inactivity, we add the visit's counts and timing to anonymous aggregate totals and delete its activity record. Aggregates are retained for up to 90 days. You can switch visit statistics off with one click in the footer of any page; that choice applies across FancyGoing? pages in this browser. We also respect a previous refusal of analytics. Opting out has no effect on browsing, sign-in or plans. These statistics are not an exact count of every visitor: opt-outs, limited or blocked requests, repeat visits and automated traffic affect coverage.
To prevent repeated requests from inflating time, each visit keeps a bounded set of secret-key hashes for its timing messages, removed with that visit. Timing stops after 512 distinct messages, about 128 minutes at the ordinary interval, and can also be incomplete after an upgrade or damaged record. We keep the known seconds as a lower bound, identify incomplete timing in grouped counts, and exclude it from average-time and quick-exit percentages. Short-lived request budgets use secret-key hashes of the trusted network address separately from statistics records; they are not used to link visits or identify members. Expired budget records are removed by bounded, opportunistic cleanup.
More detailed analytics is a separate, optional choice and stays off until you explicitly enable it in Analytics settings. It measures event-detail views, planning and sharing actions, first plans and later returns. If enabled, secure cookies identify an anonymous browser and a visit; a signed-in member is represented by a secret-key hash. We retain a broad traffic source and allowlisted FancyGoing campaign code, never a full referring URL, private link, email address, postcode, messages or profile details in these records. The browser analytics cookie lasts up to 90 days; a visit expires after thirty minutes without activity, and measurement records are removed after 90 days through scheduled or dashboard cleanup. Turning detailed analytics off removes its cookies and associated browser records, and removes identified member measurement when you are signed in. Detailed reports describe only members and browsers that enabled it; they do not establish bookings or attendance.
A separate secure preference cookie and a hash-only preference record prevent delayed requests from turning detailed analytics back on after withdrawal. The cookie and permission expire after at most 180 days; expired server preference records are removed during cleanup after a short safety margin. They contain only the permission, its version and expiry, with no browsing activity, IP address or contact details. A previous analytics cookie alone cannot grant permission again.
You can explicitly submit optional feedback about finding an event or attending your own recent past pick. We retain the answer, type and date for up to 90 days. For thirty days after saving a pick, we keep its public title, date and times privately so we can ask about it after it leaves the rolling diary; the prompt is checked against your current saved pick and removed if you unpick. A pick alone is not evidence of attendance. An anonymous usefulness answer does not require analytics consent.
The weekly weekend digest is a separate choice. Enter an email address, tick the opt-in and use the confirmation link sent to that address before receiving digests. Creating an account or picking an event never subscribes you. We keep the subscription address privately for email delivery, the confirmation status and a delivery record to prevent duplicate sends; reports show counts only. Unsubscribe through the link in any digest. Unconfirmed requests expire, and unsubscribed addresses are retained only as a one-way suppression key so they receive no further digest unless someone explicitly subscribes and confirms again.
We may contact an organiser about a verified free listing using a publicly provided business contact where corporate marketing is permitted, or where the recipient explicitly requested contact. We record the source, reviewed eligibility and contact history privately, send at most one follow-up, and check replies before further contact. Organiser emails identify FancyGoing? and include an opt-out link and hello@fancygoing.com. Opt-out links expire after six months; the contact address is erased on opt-out and a one-way suppression key prevents further organiser messages. We do not add organisers to the newsletter or use member profile data for outreach.
Retention and your controls
You can edit your profile and discovery settings, remove your current photo, change picks or hidden choices, remove friends and replace your invitation link. Your social-data export includes your activity feedback, personalisation setting and hidden event IDs. Social-data erasure removes these records alongside your personal saved ideas. Expired activity feedback stops influencing recommendations immediately; old stored entries are removed on your next activity-history change. Removing a friend stops access to the private chat, but does not delete the stored messages.
You can clear an interest answer, leave a shared plan or circle, withdraw your member introduction, and block a member. Leaving removes membership and answers and stops access to that conversation; messages already shared with the group are not automatically withdrawn. A plan owner can remove a member, replace the invitation, archive, transfer ownership or delete the plan. Public events no longer in the approved diary are omitted from shared views.
Shared-plan and circle messages expire 90 days after sending. Limited delivery-reconciliation metadata can remain for a further 90 days to prevent duplicate messages; after that, cleanup removes its sender association and retains only anonymous message identifiers. Reports and the limited evidence needed to address them expire after 180 days. Expired message text is unavailable immediately; bounded physical cleanup runs when the service is used and can take longer. Shared-plan titles, membership, answers, read status and arrangement records remain until you leave, remove them or use the social-data controls. In Connect you can export your own social data or explicitly erase your social data. Erasure removes your directory preferences, forum contributions and associated reactions, follows, bookmarks and notices from the active service, as well as your personal saved ideas and new social records, closes shared plans you own, and removes your memberships; it does not delete your account, old friend conversations or information another member has copied.
Account records, Google connections and legacy private friend messages have no automatic expiry while your account remains active. Use Account → Delete account to remove your FancyGoing profile, photo, saved ideas, connections, Google link and your message text, and revoke sign-ins on every device. Shared plans with eligible remaining members stay, with ownership transferred to an existing verified member. Plans without an eligible remaining member are retired. A de-identified system record, other members’ contributions and necessary moderation or security evidence may remain. Account deletion is separate from the social-data controls. Legacy member reports have no automatic expiry; event-chat messages and their reports expire thirty days after the event ends, with physical cleanup when the service is used.
Choosing Find company for this activity adds you to that activity’s company list. An anonymous count appears on event cards and lists; your name and introduction are shown only to eligible members who also choose to find company for that activity. You can stop looking at any time. This does not confirm attendance or send a connection request automatically.
You can also contact hello@fancygoing.com for help with deletion or retained information. Hosting logs and backups can have separate retention; removal from the active site does not establish immediate removal from every backup.
Requests and concerns
You can contact us to ask about access to your information, corrections, deletion, restricting or objecting to use, or receiving a copy for transfer. Which rights apply depends on the circumstances. We may need to check your identity before acting on a request.
If you have an unresolved concern, you can contact the UK Information Commissioner’s Office (ICO).