Privacy notice

Last updated: 19 November 2026.

1. Who we are

PartyDen is a curated online directory of children’s party venues, Function Suites and suppliers, covering the North West of England, Cheshire, Lancashire, Wirral and Merseyside, and the High Peak / Derbyshire edge.

The controller of personal data processed for PartyDen is:

James Greaves, trading as PartyDen (sole trader)
Email: [email protected]
Website: https://partyden.co.uk
A postal address is available on request by email.

If you have a privacy question, a request to correct or remove a listing, an objection to being contacted, or a data protection complaint, email [email protected], or use the claim and opt-out pages on the website.


2. What this notice covers

This notice explains how we handle personal data when we:

  • research and publish directory listings;
  • keep an internal listings and outreach tracker;
  • operate the public website; and
  • (later, and only once our internal prerequisites are met) send a limited email to confirmed limited companies, LLPs and other corporate subscribers about their listing.

It does not describe services we have not built. In particular, PartyDen does not:

  • take bookings or payments;
  • run a customer account or login;
  • operate a mailing list or newsletter signup;
  • run a review form;
  • automatically enrol anyone in a paid “Featured Partner” service.

If those features are launched later, this notice must be updated *before* they go live.

We use Google Analytics 4 only if you accept optional analytics cookies. That tool is not loaded, and no analytics cookies are set, unless you click Accept. See sections 8 and 12.


3. When the UK GDPR applies

The UK GDPR applies to personal data: information that relates to an identified or identifiable living person.

A lot of what PartyDen publishes is information about companies and organisations, not about individuals. A limited company’s name, its official website, a generic mailbox such as info@ or bookings@, a venue landline, and the address of a hall, leisure centre, shop or other trading premises are usually not personal data.

Personal data is involved when, for example:

  • the listing is of a sole trader or an ordinary partnership, or otherwise identifies a living person;
  • we hold a person’s name, a personal email address, or a personal telephone number;
  • we hold a residential address;
  • someone writes to us to claim, correct or remove a listing, or to opt out;
  • a visitor’s IP address or similar online identifier is processed when they use the site (including by some of the suppliers described in section 8).

We treat unclear cases with the same care as personal data. See the ICO’s guide to what is personal information.


4. Personal data we process, and where it comes from

4.1 Businesses and people connected with listings

We collect and hold information about venues and suppliers so we can list them, keep the directory accurate, and (later, if approved) contact the right sort of business about their listing.

This typically includes:

  • business or trading name;
  • official website and the official page we checked;
  • area, and, where it is a trading or venue address published on the official site, the address and postcode;
  • published organisational telephone numbers and, where appropriate, organisational email addresses;
  • other details taken from the official site, such as prices, hire information, facilities, and accessibility statements the business has already published;
  • our own notes, such as the date we checked the official site, the listing category, legal entity type (where we have recorded it), and whether a listing is live, parked, or suppressed.

We obtain this information from the business’s own official website, not from Google Maps, other directories, or competing sites. We do not ask other people to send us their friends’ details.

We do not intend to publish:

  • residential or home addresses, or a map pin on a home;
  • personal-name or clearly personal email addresses;
  • personal mobile numbers.

If those details appear on an official site, we may keep them in an internal tracker only, so we can maintain or remove the record, and we will not put them on the public page. As of 19 November 2026, personal or consumer-domain emails, UK 07 mobiles, and five home or possible-home addresses have been removed from public listings. A UK mobile is published only if the business later asks us to show it, through a claim or update request, with a recorded opt-in. Some listings still use a trading name that identifies a person; those names stay on the public page until we have given Article 14 privacy information or a documented decision is made to exclude the listing.

4.1.1 Tags, badges and how to request a correction

The capability tags and badges on a listing, such as SEN sessions, Changing Places, ear defenders or SEN-aware, are taken only from that business’s own public website. We do not infer tags from other directories, reviews or assumptions, and we do not use tags that would reveal health information about a living person or their family.

If a tag, badge or other detail is wrong or out of date, or you would like a listing removed, email [email protected], use the “Request a correction” link on the listing page, or use the opt-out page. Please name the listing. We will aim to acknowledge a clear, authorised request within 2 working days and to act on it within 5 working days, as described in section 7. We will use your email only to handle the request and to keep a record of what we changed.

4.2 People who contact us

Once a monitored inbox is published, if you email us to claim a listing, correct information, opt out, ask us to publish a mobile number, or ask a question, we will process the name, email address, and anything you send us, so we can reply and keep a record of what we did, including any consent to publish a mobile number.

4.3 Visitors to the website

We do not set a PartyDen login cookie. When you visit the site, our hosting and content suppliers automatically receive the technical information that any website request produces, typically including your IP address, the page requested, the date and time, and browser or device information. Some of that information is personal data. See section 8.

If you accept optional analytics cookies on partyden.co.uk, your browser will also load Google Analytics 4, which receives further technical and usage data as described in sections 8 and 12. If you reject, or until you choose, those scripts are not loaded. A first-party cookie or local-storage value may be used only to remember your Accept or Reject choice.

If you choose to load a map, your browser also requests map images or map software from Mapbox. The map on a venue page is not loaded until you click to show it. The /map/ page loads Mapbox’s map software in your browser when you use that page.

Every page currently loads fonts from Google Fonts. Your browser therefore requests those files from Google, which receives your IP address and related request data. See section 8. A change to self-host the same typefaces has been prepared as a patch and has not been deployed. If that patch is later deployed, this paragraph and section 8.3 must be updated at the same time.


5. Why we use personal data, and the lawful basis

Under the UK GDPR, we need a lawful basis whenever we process personal data.

PurposeLawful basis
Researching, publishing and updating directory listings that contain personal data, and keeping an internal tracker so we can correct or remove themLegitimate interests (Article 6(1)(f)): operating an accurate, useful local directory of already-public business information, with the safeguards in our legitimate interests assessments
Responding to a claim, correction, opt-out or listing-removal requestLegitimate interests (Article 6(1)(f)). This is not the contractual basis in Article 6(1)(b): that basis applies only where processing is necessary to perform a contract with the person, or to take steps at their request before entering into a contract with them. A listing correction or removal request is not, by itself, that kind of contract.
Optional website analytics (Google Analytics 4), only after you acceptConsent (Article 6(1)(a)), and PECR consent for non-essential cookies. If you reject or do nothing, we do not load that tool.
Responding to a formal UK GDPR rights request (for example a subject access request)Compliance with a legal obligation (Article 6(1)(c))
Keeping a suppression or “do not contact / do not publish” record so we honour an objection and do not contact or republish in errorLegitimate interests (Article 6(1)(f)): retaining the minimum information needed to respect the objection and prevent future marketing or republication. Direct marketing objections are absolute. We do not rely on a second, unresolved basis for this record.
Operating and securing the website (hosting, security logs)Legitimate interests: providing and protecting the site
Later, sending a limited marketing email to a confirmed corporate subscriber about its listing and, if the product exists, an optional paid upgradeFor PECR, prior consent is not required for a genuine corporate subscriber, but we will still identify ourselves, offer an opt-out, and honour it. A company’s legal form does not automatically make every email address it uses a corporate subscriber address. Where the email is personal data, the UK GDPR lawful basis is legitimate interests. We will not start this until our internal prerequisites are met. We will not send marketing email to sole traders or ordinary partnerships without consent or another PECR permission.

A fuller record of the legitimate interests assessments is held internally. The interests we rely on, and the main safeguards, are described in this notice.

We do not use consent as the general basis for publishing already-public business listings. If we ever rely on consent for a specific optional service, we will say so and you will be able to withdraw it.


6. If we did not collect your data from you (Article 14)

We usually do not collect listing information from the person it relates to. Where a listing includes personal data, we obtain it from a publicly accessible source: the official website of the venue or supplier. The categories are those described in section 4.1 (for example a sole trader’s trading name, or an unpublished official contact held only in our internal tracker).

The UK GDPR still requires us to give you privacy information, generally within one month of obtaining the personal data, or earlier if we first use it to communicate with you or disclose it.

This notice, which we publish on the website and link from the site footer and from pages about claiming or correcting a listing, is how we make that information available. A page on our website does not, by itself, guarantee that you have seen it. For that reason we also:

  • keep public listings business-focused, and we do not intend to publish residential addresses, personal emails, personal mobiles, or unnecessary named contacts;
  • if we later email you, include or clearly link to this notice in that first email; and
  • if we cannot meet the Article 14 requirements for a particular personal detail, minimise or omit that detail unless a properly assessed exception applies. The internal process is in our Privacy & Data Protection Operating Standard.

If you are listed, or you are the person whose contact details we hold in connection with a listing, you can ask us to correct or remove personal data, or to take a listing down, using the contact details in section 1 or the claim and opt-out pages.


7. How long we keep personal data

We do not keep personal data for longer than we need it. The periods below are the periods we have chosen and documented. They are not periods set by the UK GDPR itself.

Type of recordHow long we keep it
Personal data on a live public listingWhile the listing remains relevant, and we check listings periodically against the official site. If you ask us to remove personal data, we will take it off the public site within 5 working days of a valid request (and we will aim to acknowledge the request within 2 working days),
Personal contact details in our internal trackerReviewed at least annually, and removed when no longer needed for maintenance, a permitted contact, or suppression
Limited record of a removed listingPersonal data comes off the public site; a limited internal record is usually deleted or anonymised within 12 months, unless we still need it to deal with a dispute or to stop the same data being published again
Enquiry, claim, correction and complaint emails2 years after the matter is resolved, or longer if a dispute is still ongoing, except for any suppression record
Suppression / opt-out / “do not publish” recordsThe minimum needed to honour the objection and prevent future marketing or republication
Official entity-check evidence (for example a Companies House record used to classify a business)Only as long as needed to demonstrate that classification and any related campaign decision: while the record is live, and for 12 months after it is closed, unless a complaint or dispute is outstanding
Removal, rights-request and complaint logs6 years from closure, then deletion
Technical logs held by our hosting supplierAccording to Cloudflare’s own retention period, which we do not fully control
Google Analytics 4 user- and event-level data (only if you accepted analytics cookies)The period set in the GA4 property. Google’s standard options are 2 months (the default) or 14 months. We will record the chosen period here once it is confirmed. Aggregated standard reports may be kept for longer under Google’s own systems. First-party _ga cookies default to 2 years unless we shorten them. Official source: GA4 data retention and GA4 cookie usage (checked 19 November 2026).
Your Accept or Reject choiceUntil it expires or you change it (the consent record itself is a strictly necessary preference).

The 5-working-day and 2-working-day service levels described above apply to valid requests sent to [email protected].


8. Who we share personal data with (suppliers and processors)

We do not sell personal data. We do not share it with other directories for their marketing.

We use suppliers to host the site and to provide maps, fonts, and an internal tracker. It matters how the data flows:

  • some providers receive data directly from your browser (for example Google Fonts on every page, and Mapbox if you load a map);
  • some process data on our behalf as processors (Cloudflare for hosting the site; Notion for the internal tracker; Mapbox for maps, under its customer DPA);
  • some act as an independent controller for what they receive (in particular Google, for the public Fonts API, under Google’s own privacy policy);
  • a restricted international transfer is a separate question. The fact that a provider is part of a US-based group does not, by itself, mean that every interaction is a restricted transfer to the United States. We set out below what each provider’s own terms actually say, and where a transfer mechanism is documented.

8.1 Cloudflare (website hosting and content delivery)

The public site is hosted on Cloudflare Pages and served through Cloudflare’s network. The contracting entity for the Self-Serve Subscription Agreement (last updated 12 September 2025, fetched 19 November 2026) is Cloudflare, Inc., 101 Townsend St., San Francisco, California 94107, as stated in section 20 of that agreement. Cloudflare, Inc. is a processor for this hosting under the Cloudflare Customer Data Processing Addendum (version 6.4, effective 3 April 2026, fetched 19 November 2026). The DPA names Cloudflare, Inc. at the same San Francisco address as the data importer.

What this means in practice:

  • the published site, including any personal data that appears in a listing, is stored and served as static site files;
  • when you visit, Cloudflare processes request metadata. Cloudflare’s public GDPR information states that, for its core application services, metadata about traffic (most often IP addresses) is processed on behalf of customers in data centres in the United States and Europe, for a limited period. See Cloudflare GDPR FAQs.
  • Cloudflare also operates a global edge network, so a request may be handled at a data centre near the visitor.

We have not purchased Cloudflare’s Data Localization Suite or a Customer Metadata Boundary that would keep logs only in one region.

8.2 Mapbox (maps, only if you use a map)

If you click “Show map” on a venue page, or you use the /map/ page, your browser requests map tiles, a static map image, or the Mapbox GL JavaScript library from Mapbox.

Mapbox, Inc. offers a Data Processing Addendum. Mapbox’s published privacy and security FAQ states that it processes personal data in AWS in the United States, that it cannot limit processing to Europe or another single region, and that content may be cached on AWS’s content delivery network in various regions for performance. On 19 November 2026 we checked the official Data Privacy Framework list record for Mapbox, Inc.. Mapbox, Inc. is listed for the EU–US Data Privacy Framework, the UK Extension to that Framework, and the Swiss–US Data Privacy Framework, in each case as Active – Re-certification under Review, covering non-HR data. The UK Extension original certification date is 5 December 2023, with the next certification due date 10 November 2027. The linked Notice of certification is dated 28 October 2026 and excludes private-preview, beta or trial products. “Re-certification under Review” means the listing is still shown as active on the official list, but it should be re-checked if the status changes before this notice is published or if Mapbox’s role expands. Where needed, Mapbox also refers to Standard Contractual Clauses. See also the Mapbox Data Privacy & Security FAQ.

Mapbox may process technical data such as IP address and the map request itself. PartyDen does not use Mapbox to geocode addresses in the visitor’s browser; venue coordinates are prepared in advance.

8.3 Google Fonts (typefaces loaded on every page)

Every page currently loads fonts from the Google Fonts Web API (fonts.googleapis.com and fonts.gstatic.com). A change to self-host the same typefaces has been prepared as a patch and has not been deployed. If that patch is later deployed, this section and section 4.3 must be updated at the same time, because Google would then no longer receive font requests from visitors.

Google’s official Fonts privacy FAQ states that:

  • the Fonts API is unauthenticated and does not set or log cookies;
  • when a visitor’s browser requests a font, Google receives the visitor’s IP address, the requested URL, and HTTP headers including user-agent and referrer;
  • Google processes the IP address to respond to the request and for security;
  • Google says it does not use information collected by Google Fonts to create profiles of end users or for targeted advertising.

See Google Fonts — Privacy.

We have not identified a Google Data Processing Addendum that covers the public Google Fonts CSS API in the way Cloudflare’s and Mapbox’s customer DPAs cover those products. In practice, the visitor’s browser talks to Google directly, and Google’s own privacy policy applies to what Google receives. Google is therefore better described as an independent controller for that Fonts API request, not as our processor. PartyDen causes the request by embedding the Fonts API; we should not describe it as a closed processor appointment, and we should not make a blanket claim about a restricted transfer mechanism we do not have with Google for this product. Google also describes self-hosting as a way for a site operator to avoid sending that end-user data to Google.

8.4 Notion (internal tracker only)

We use Notion as an internal listings and outreach tracker. It is not shown to site visitors and it is not a public comments or booking tool.

Notion Labs, Inc. states that it is a processor of personal data that a customer uploads to the Notion service, under a Data Processing Addendum incorporated from Notion’s GDPR page. That page, fetched on 19 November 2026, linked to a Data Processing Addendum at https://www.notion.so/Data-Processing-Addendum-361b540101274b1fa7e16b90402b0d99. The same document was labelled “Deprecated 14 August 2026” on Notion’s site, and we could not find a clearly dated replacement text from that page alone. Notion’s help pages also say its DPA incorporates EU and UK Standard Contractual Clauses.

Data location: Notion’s data residency help page, fetched on 19 November 2026, states that by default workspace data remains hosted in the United States (AWS; the default region listed is US-West-2, Oregon, with backups in US-East-2). EU residency (Frankfurt, with backups in Ireland) is available free of charge to eligible Enterprise plan workspaces only after a confirmed migration. PartyDen has not enabled Enterprise EU residency, so the tracker should be treated as US-hosted. Account information, usage data, and subprocessor processing may still occur outside a chosen residency region.

8.5 Google Analytics 4 (only if you accept analytics cookies)

If you click Accept on the cookie banner, your browser loads Google Analytics 4 so we can see aggregated information about how the site is used (for example which pages are visited). We do not use GA4 to show personalised ads, and we will not link the property to Google Ads unless this notice is updated first.

Google acts as our processor for this measurement under the Google Ads Data Processing Terms, which Google says are incorporated for customers established in the UK.

Typical data includes a client identifier in first-party cookies (_ga and _ga_<container>, default lifetime 2 years), IP address and device or browser information, pages viewed, and approximate location derived by Google. We will not enable Google Signals unless this notice is updated first.

Google processes Analytics data on servers that may be in the United States and other countries. Restricted transfers are addressed in Google’s Ads Data Processing Terms, including Standard Contractual Clauses, and, where applicable, Google LLC’s certification under the Data Privacy Framework. Check the official list if we rely on the Framework.

8.6 Email (Gmail)

The published contact address is [email protected]. If you email us, Google processes that message in order to provide the Gmail service. Google’s own terms and privacy policy apply to that email service. We use the inbox only to handle your request (for example a claim, a correction, an opt-out, a mobile-number consent, or a privacy question) and not to add you to a marketing list.

8.7 Other tools

We may use ordinary business tools (for example a domain registrar, Cloudflare Email Routing, or a business-address service) once those accounts exist. We will name each provider here when it is actually in use, and we will not list a supplier we do not use.

We use publicly available official-site sources, and we may look up a UK company number on Companies House, when we classify a legal entity. Companies House is a public authority register, not our processor.


9. International transfers

We do not assume that every use of a US-based provider is a restricted transfer of personal data to the United States. The contracting entity, the actual data flow, and any documented transfer mechanism have to be looked at for each service.

On the materials we have checked:

  • Cloudflare: the contracting entity on the Self-Serve Subscription Agreement is Cloudflare, Inc. (see section 8.1). Cloudflare’s public GDPR information says traffic metadata is processed on behalf of customers in data centres in the United States and Europe, and requests may also be handled on its global edge network. That is not, by itself, a finding that every visitor request is a restricted transfer to the United States. Where a restricted transfer occurs, we rely on the Customer DPA (version 6.4), including the Standard Contractual Clauses in that DPA. We have not identified a UK Extension Data Privacy Framework certification for Cloudflare, Inc. on the official list as part of this check, so we do not rely on the DPF for Cloudflare.
  • Mapbox: its own FAQ states that personal data is processed in AWS in the United States, with worldwide caching. On 19 November 2026, the official Data Privacy Framework list showed Mapbox, Inc. as Active – Re-certification under Review under the UK Extension, covering non-HR data (see section 8.2). The DPA also refers to Standard Contractual Clauses where needed.
  • Google Analytics 4: only after consent. Google is a processor under the Ads Data Processing Terms, which include transfer mechanisms (Standard Contractual Clauses and, where applicable, the Data Privacy Framework for Google LLC). Data may be processed in the United States and other countries.
  • Gmail: correspondence sent to [email protected] is processed by Google to provide the email service, which may involve processing in the United States and other countries, under Google’s terms.
  • Google Fonts: the visitor’s browser requests files from Google. We have not identified a PartyDen-to-Google transfer mechanism for the public Fonts API. The practical way to avoid that third-party request is to self-host the fonts. A self-host patch has been prepared and has not been deployed.
  • Notion: default hosting of workspace content is in the United States. PartyDen has not enabled Enterprise EU residency. Notion’s GDPR page, fetched on 19 November 2026, incorporates a Data Processing Addendum and refers to Standard Contractual Clauses. The DPA document linked from that page was still labelled “Deprecated 14 August 2026”. Until Notion publishes a clearly dated replacement, we treat the tracker as US-hosted under Notion’s current customer terms and SCCs, and we should accept or download the in-product DPA when convenient so the current text is on file.

Where a supplier is acting as our processor, we rely on that supplier’s DPA and the transfer mechanism it documents, once those documents have been confirmed. Where your browser requests a resource directly from a third party (in particular Google Fonts), that party’s own terms and privacy policy also apply.


10. Your rights

Where we process your personal data, you have rights under the UK GDPR. These include the right to be informed, the right of access, the right to rectification, the right to erasure (in certain circumstances), the right to restrict processing, the right to object to processing that is based on legitimate interests (including an absolute right to object to direct marketing), and the right not to be subject to a decision based solely on automated processing that has legal or similarly significant effects. We do not make automated decisions of that kind.

To exercise these rights, email [email protected], or use the claim or opt-out pages. A postal address is available on request by email.

You can also make a data protection complaint to us, in the same way, if you think we have infringed the UK GDPR in connection with your personal data. We must acknowledge that complaint within 30 days, look into it without undue delay, keep you informed, and tell you the outcome. This is a legal duty under section 164A of the Data Protection Act 2018, as inserted by the Data (Use and Access) Act 2025 and in force from 19 June 2026. See the ICO’s guidance on handling data protection complaints.

You also have the right to complain to the UK Information Commissioner’s Office (ICO): https://ico.org.uk/make-a-complaint/.

If you are a business that has been listed and you want the listing corrected or removed, we will also deal with that as an operational request, including where some of the information is company information rather than personal data.


11. Direct marketing and PECR

We do not currently send marketing emails, texts or social-media direct messages.

If we later email a limited company, LLP or other corporate subscriber about its listing, that email is marketing if it also promotes an optional paid upgrade, even if it includes a claim or correction invitation. We will identify ourselves, include a postal address, offer a simple opt-out, and honour that opt-out. A company’s legal form does not automatically make every email address it uses a corporate subscriber address. We will not send marketing emails to sole traders or ordinary partnerships unless we have a PECR permission (specific consent, or the “soft opt-in” for our own existing customers, which we do not have today).

A request to claim or correct a listing is not treated as consent to marketing.


12. Cookies and similar technologies

We show a cookie banner with Accept and Reject choices of equal prominence. Google Analytics 4 is not loaded, and Google Consent Mode v2 is set to denied by default (analytics_storage, ad_storage, ad_user_data and ad_personalization), until you click Accept. If you click Reject, or if you do nothing, that tool stays off. You can change your mind later using Cookie settings in the footer. Cloudflare, Mapbox or Google Fonts may still set or read their own cookies when your browser talks to them. The Google Fonts API, according to Google, does not set or log cookies.

Cookie or similarWhoPurposeDurationType
A first-party consent record (cookie or local storage)PartyDenRemembers whether you clicked Accept or Reject, so we do not ask on every page loadUntil it expires or you change itStrictly necessary
_ga, _ga_<container-id>Google Analytics 4 (set only after Accept)Distinguish visitors and persist session stateDefault 2 years, unless we shorten this in the GA4 tag settingsOptional analytics, consent required

PECR requires consent for non-essential cookies. UK GDPR lawful basis for the related analytics processing is consent (Article 6(1)(a)). Mapbox still loads only if you use a map, as described earlier, and is a feature of the directory rather than an advertising cookie. If we add further non-essential cookies, we will update this notice and the banner first.


13. Children

PartyDen is a directory for parents and for businesses that serve children’s parties. That does not make it a service directed at children in the data-protection sense. We do not knowingly collect children’s personal data, we do not offer child accounts, we do not market to children, and we do not request or publish photographs of children.

It is still possible that a child’s personal data could be sent to us accidentally, for example in an email. If that happens, we will not use it for a listing, and we will delete it unless we have to keep a minimal record of the correspondence (for example to close a complaint).


14. Changes

We will update this notice if our processing changes. The date at the top of the published page will be the date of the current version.


Browse listings