Information we may collect
We may collect information you submit through forms, such as business listing details, contact information, editorial enquiries, event submissions, and partnership messages. If you consent to analytics, we may also collect limited usage information such as pages visited, sanitised search terms, search filters, result counts, result selections, broad content categories, and approximate technical and performance information.
How we use information
We use information to operate the website, review and publish business listings and events, respond to enquiries, improve content, prevent abuse, process payments through our secure payment provider, and understand how visitors use the site when analytics consent has been given.
Personalised reading and reader feedback
If you follow counties, topics, or editorial series on the For You page, those choices are saved only in local storage on your device. They are not used to create an account or public profile and can be reset from the page. If you choose to join the newsletter, you may explicitly submit those preferences with your subscription so we can tailor future editions.
Article and guide reactions are stored as anonymous aggregate counts using a salted, content-specific identifier to reduce repeat submissions. Reader tips are private editorial submissions: they are reviewed by the editorial team and never publish automatically. Optional contact details supplied with a tip are used only to follow up about that submission.
Analytics
With consent, we use Google Tag Manager, direct Google Analytics and Amplitude Analytics for explicitly selected public-site usage events. Session replay and automatic interaction capture are disabled. Private forms, business dashboards, account and trip pages, editorial previews and token-bearing URLs are excluded from third-party measurement. Page URLs and referrers have query strings and fragments removed before analytics collection. Search terms are normalised and common emails, URLs, phone numbers, postcodes, payment-like numbers, and long identifiers are redacted before analytics collection. High-risk personal disclosures are omitted. Ephemeral search identifiers are not retained across visits and are not used to build personal profiles.
Query-level analytics and search journeys are retained for up to 90 days. Non-identifying weekly aggregates may be retained for up to 25 months to understand seasonal demand and whether published content meets repeated visitor needs. Routine reports show individual query clusters only after at least three searches in a rolling 28-day period.
Advertising
We display direct-sold advertising and sponsorship based on the page being viewed, such as its county, category, topic, event type, or business type. We do not use this contextual selection to build behavioural advertising profiles. With separate advertising measurement consent, Meta Pixel and Meta Conversions API may process limited page, content, search, lead, contact, and checkout events. Matching browser and server events share a random event identifier to prevent duplicate counting. We do not send personal form details or search terms to Meta.
Payments
Business listing and commercial event listing payments are handled by a secure payment provider. We do not store full card details on this website. The payment provider may process payment and billing information according to its own privacy policy.
Sharing information
We may share information with service providers that help operate the website, process payments, host content, deliver email, measure analytics, or keep the site secure. We do not sell personal information.
We use Sentry to detect application errors. Error reports contain the application version, error type and deployed code locations. We exclude error message contents, form submissions, account details, payment information, cookies, request headers and page URLs from these reports. We do not enable Sentry session replay or performance tracing. Sentry processes reports in its EU region; its servers receive the connection IP when a browser sends a report, although our application does not attach an IP or user identity to the report.
Your choices
You can request correction or removal of personal information where legally applicable. You can also manage cookie preferences as described in our Cookie Policy.