Cookie Policy
Reviewed: 7 November 2026 (second pass)
Pre-launch working policy — the live-site storage audit, analytics and affiliate arrangements, and any necessary consent or objection controls must be completed before publication.
1. About this policy
Golf Done Better (“GDB”, “we”, “us” and “our”) helps visitors research golf courses, compare options and plan golf rounds and trips. This Cookie Policy describes the cookies and similar technologies used by the current website, and how you can control them.
It should be read alongside our Privacy Policy, which explains the processing of personal information more broadly. Cookies are only one form of technology that can store information on, or access information from, your device.
2. Cookies and browser storage
A cookie is a small file that a website or service can store in your browser. Browser local storage and session storage can also keep information on your device, but work differently from conventional cookies.
Local storage generally persists between browser sessions until it is removed. Session storage generally lasts for the current browser tab or session, although the precise duration can depend on the browser. The website may read information it previously stored so that selected features continue working.
UK rules on storage and access technologies can apply to cookies, local storage, session storage and other technologies, whether or not the information directly identifies you.
3. Storage used by the current GDB website
The Search Courses and Plan a Golf Trip pages in the current GDB test files use the following named browser-storage items. These support site functions; they are not GDB accounts or records held in a central user account database.
| Storage item | Type | Purpose |
|---|---|---|
| gdb_saved | Local storage | Remembers your saved golf courses. |
| gdb_compare | Local storage | Remembers courses selected for comparison. |
| gdb_trip_v8_fixed | Local storage | Stores the trip-planning basket and itinerary selections on the trip-planning page. |
| gdb_last_results | Local storage | Keeps a limited set of recent course results for navigation and continuity. |
| gdb_results_per_page | Local storage | Remembers the selected number of course results displayed per page. |
| gdb_results_page | Local storage | Remembers the current course-results page. |
| gdb_last_search | Session storage | Keeps details of a recent location or map search so it can be restored during the session. |
| gdb_last_course_search | Session storage | Keeps course-search result references and related search details for the session. |
| gdb_detail_item | Session storage | Passes selected course information to the course-details view. |
The website does not assign a fixed expiry time to these items. Local storage can remain until it is overwritten or deleted by you, the website or the browser. Session storage generally ends when its browser tab or session closes, although a browser may restore it. Clearing GDB site data may remove saved courses, comparison lists, recent searches and trip plans.
The reviewed HTML and JavaScript do not directly set an HTTP cookie or load an identifiable website analytics library. This does not prove that no cookies or other storage are used by the live site, embedded maps, external scripts, affiliate destinations or hosting services. Those must be tested in a browser before publication.
4. Why GDB uses this storage
Saved-course lists, comparisons and trip baskets support features that visitors deliberately use. Search-history restoration and remembered pagination settings support convenience and continuity. The purpose of each storage item—not merely whether it is first-party or labelled functional—determines whether a PECR consent exception is available.
Under the Privacy and Electronic Communications Regulations (PECR), storing information on a device or accessing information already stored there generally requires consent unless a specific exception applies. For example, storage strictly necessary for a service you request may qualify for an exception. The exception for adapting a service to your preferences has additional requirements, including a simple and free way to object. GDB must assess the storage items individually and provide the relevant controls before enabling any use that requires them.
5. Third-party maps, location services and website resources
The current site files make requests to external providers for maps and location searches, including Geoapify, OpenFreeMap, OpenStreetMap-related endpoints, Wikidata and Wikimedia Commons. Search and trip-planning pages also load software from unpkg and jsDelivr. Course Details can display an embedded Google Maps frame when coordinates are available, while other parts of GDB offer ordinary outbound Google Maps links. An embedded frame is different from a link because it may contact Google while the GDB page is being viewed.
When those services are contacted, they can receive technical request information such as your IP address and, where relevant, a place name, search term, map position or coordinates. External scripts, map tiles and embedded content may also access or store device information. The details depend on each provider and its implementation.
Before public launch we must test all five functional pages and the legal pages, including the loaded Google Maps frame, maps, location searches and affiliate click-throughs, to identify any storage or access activity. Where an activity requires consent, it must not run until the required consent has been obtained. Where an exception requires an objection mechanism, that mechanism must work. A destination opened by clicking an external map or booking link has its own cookie practices.
6. Analytics and affiliate links
No active visitor analytics package was identified in the supplied site files. GDB may add analytics at launch or later. Before it is enabled, this policy must specify the provider, purpose, storage technology and duration. Some narrowly defined website-usage statistics may qualify for the PECR statistical-purposes exception, but only if its conditions are met, including clear information and a simple, free means to object. Other analytics require consent where no exception applies.
GDB can display affiliate links to independent golf and travel providers. An outbound link may carry a referral identifier, and the destination or affiliate network may use its own tracking technologies after you click. The final affiliate networks and their on-site tracking arrangements have not yet been chosen or verified.
The current files do not establish that GDB runs advertising pixels or on-site cross-site tracking. Affiliate referral URLs do not, by themselves, show that GDB sets tracking cookies. If affiliate scripts, conversion pixels, marketing tags or cross-site tracking are added, their purposes and any consent requirements must be assessed before those technologies run.
7. Your choices and controls
You can remove GDB browser storage through your browser’s site-data controls. Deleting site data may also remove saved courses, comparisons, recent searches, selected result settings and trip-planning information. Blocking storage may prevent some features from working as expected.
If you use “near me” or other location features, you can allow or refuse the browser’s request for location access, and change that permission later in your browser or device settings. This location permission is separate from consent for cookies or other device storage.
Browser controls and device location permissions are not a substitute for website consent or objection controls where PECR requires them. Once GDB’s launch technologies are finalised, this policy will explain how to make or change those choices and link directly to the relevant controls.
8. Further information and updates
For more information about personal information, its recipients and your rights, read our Privacy Policy. For general website usage conditions, read our Terms & Conditions.
We will update this policy when the website’s storage technologies, analytics, mapping providers, affiliate arrangements or purposes change. The last-updated date will then be revised. Material changes that require renewed consent must be handled before the changed technologies are used.
GDB’s legal operator and privacy contact details will be confirmed before public launch and will be available in the Privacy Policy.