Cookie Policy
Last updated: 17 March 2026
1. About this policy
This cookie policy explains how Get Dizzy AI LTD ("Get Dizzy", "we", "us", "our") uses cookies and similar technologies on our platform at getdizzy.ai (the "Platform").
This policy should be read alongside our Consumer Privacy Policy, which explains how we collect, use, and protect your personal data more broadly.
2. What are cookies and similar technologies?
Cookies are small text files placed on your device by websites you visit. They are widely used to make websites work, remember your preferences, and provide information to website operators.
Local storage (also called localStorage) works similarly to cookies but allows websites to store larger amounts of data in your browser. This data stays on your device until you clear it manually or through your browser settings.
Session storage (also called sessionStorage) is similar to local storage but is automatically cleared when you close your browser tab.
Under the Privacy and Electronic Communications (EC Directive) Regulations 2003 (SI 2003/2426), as amended ("PECR"), we are required to tell you about any cookies and similar technologies we use, what they do, and where consent is required, to obtain that consent before they are set.
3. What we use
Our Platform uses very few cookies and storage technologies compared to most online services. We do not use advertising cookies, tracking pixels, retargeting tools, or third-party profiling services of any kind.
3.1 Third-party cookies
The main third-party cookies we are aware of on our Platform come from Google Maps, which we use to display the interactive map. We regularly review our cookie usage and are not aware of any other third-party cookies being set.
| Cookie | Set by | Purpose | Duration | Consent required? |
|---|---|---|---|---|
| NID | google.com | Stores preferences and information used to customise Google web pages, including Maps content | Up to 6 months | Yes |
| 1P_JAR | google.com | Used by Google to gather website statistics and track conversion rates on Google properties | 1 month | Yes |
| CONSENT | google.com | Records your cookie consent state for Google services | Up to 2 years | Yes |
| APISID / SAPISID / HSID / SID / SSID | google.com | Used by Google for security purposes and to authenticate your Google account if you are signed in | Up to 2 years | Yes |
These cookies are set by Google, not by Get Dizzy. Google acts as an independent data controller for some of the data it collects through these cookies, meaning Google determines its own purposes for processing that data (such as security and abuse prevention). For more information on Google's role as an independent controller, see Section 8 of our Consumer Privacy Policy. For details on how Google uses this data, see Google's privacy policy at policies.google.com/privacy.
Google may change the cookies it sets through Google Maps at any time. The cookies listed above are those we have identified at the time of writing. For the most current information about Google's cookies, see Google's cookie policy at policies.google.com/technologies/cookies.
How we handle consent: Google Maps is only loaded after you opt in. Until then, you can use all non-map features of the Platform including list browsing, AI search, and manual location search. If you do not consent, the map feature will not be available but all other features will work normally. You can withdraw your consent at any time using the cookie settings option in the Platform footer or in your account settings. When you withdraw consent, we will stop loading Google Maps on your device unless you opt in again.
3.2 Browser local storage
We use your browser's local storage to support core functionality and your preferences. None of this data is sent to our servers or linked to your account unless specifically noted.
Strictly necessary items (no consent required under PECR):
These are essential for the Platform to function as you have requested.
| Item | What it stores | Why it is strictly necessary |
|---|---|---|
| Supabase auth token | Your encrypted authentication session | Required to keep you logged in. Without this, you would need to sign in on every page load. |
| Onboarding flag | Whether you have completed the new user walkthrough | Required to prevent the walkthrough from repeating on every visit, which would make the Platform unusable. |
Functional items (support your experience):
These items are not strictly necessary for the Platform to function, but they are closely related to the service you have requested and would be reasonably expected by users of a location-based venue discovery platform. We believe this storage falls within the PECR exemption on that basis. You can clear these items at any time by clearing site data in your browser settings.
| Item | What it stores | Why we use it |
|---|---|---|
| Cached location | Your approximate latitude and longitude | Allows the map and location-based features to load with a relevant area when precise GPS data is unavailable (for example, before you grant location permission or if your device cannot determine your position). Without this, every map load would require a fresh GPS request, which may fail or be slow on some devices. Stored on your device only and not sent to our servers or linked to your account. |
| Filter preferences | Your selected venue type, distance, and dietary filter selections | Remembers your filter choices between sessions so you do not have to set them each time. Stored on your device only and not sent to our servers or linked to your account. |
3.3 Browser session storage
Session storage is automatically cleared when you close your browser tab. We use it for the following purposes:
Strictly necessary items (no consent required):
| Item | What it stores | Why it is strictly necessary |
|---|---|---|
| CSRF token | A security token that protects against cross-site request forgery attacks | Required to protect the security of your session. |
| Splash screen flag | Whether the loading screen has been shown in this session | Prevents the loading screen from displaying repeatedly during a single session. |
Items requiring consent:
| Item | What it stores | Why we use it |
|---|---|---|
| UTM attribution data | Marketing campaign parameters (source, medium, campaign name) if you arrived via a marketing link | Used to understand which marketing channels are effective. This data is written to your account record if you sign up (see Section 4 of our Consumer Privacy Policy for the legal basis). This item is included in our consent mechanism alongside Google Maps cookies. |
3.4 What we do not use
For clarity, our Platform does not use any of the following:
- Google Analytics or Google Tag Manager
- Facebook Pixel or Meta tracking
- Hotjar, FullStory, or similar session recording tools
- Any advertising, retargeting, or cross-site tracking cookies
- Any third-party analytics cookies (our analytics provider, Vercel Analytics, is entirely cookieless and does not store raw IP addresses)
- Fingerprinting technologies
4. How to manage cookies and storage
Our consent controls
When you first visit the Platform, we will ask for your consent before loading Google Maps cookies and non-essential session storage (UTM attribution). You can change your choices at any time using the cookie settings option in the Platform footer or in your account settings. Withdrawing consent is as straightforward as giving it.
Browser-level controls
Most browsers also allow you to control cookies and site data through their own settings. Common options include:
- Blocking all third-party cookies: This will prevent Google Maps cookies from being set (and will disable the map feature) but will not affect local storage or session storage.
- Clearing site data for getdizzy.ai: This will remove all cookies, local storage, and session storage associated with our Platform. You will be logged out and your preferences will be reset.
- Clearing cookies only: In most browsers you can selectively delete cookies without clearing local storage.
Each browser handles these settings differently. You can find instructions for managing cookies in your browser's help documentation or at https://www.aboutcookies.org.
What happens if you block or delete everything
If you clear all site data for getdizzy.ai:
- You will be logged out and need to sign in again
- Your filter preferences will be reset to defaults
- The new user walkthrough may appear again
- Your cached location will be cleared (the Platform will ask for GPS permission again or fall back to manual location search)
- Your cookie consent choices will be reset and you will be asked again on your next visit
5. Changes to this policy
We may update this cookie policy if we add new technologies or change how we use existing ones. Where changes are significant, we will notify you through the Platform.
The "last updated" date at the top of this page tells you when this policy was most recently revised.
6. Contact us
If you have any questions about this cookie policy, please contact us:
- Email: legal@getdizzy.ai
- Post: Get Dizzy AI LTD, 340 The Crescent, Colchester, England, CO4 9AD
If you are unhappy with how we handle cookies on our Platform, you also have the right to lodge a complaint with the Information Commissioner's Office. See our Consumer Privacy Policy for ICO contact details.