Cookie Policy
Last updated: August 31, 2026
This Cookie Policy explains how Digital Florists Ltd ("we", "us", "our") uses cookies and similar technologies on:
- https://digitalflorists.com (our "Website"); and
- our Service (including customer portals, delivery tracking links and public forms where we provide and host them).
This policy should be read with our Privacy Notice.
1. What Are Cookies?
Cookies are small text files stored on your device when you visit a website or use an online service.
2. Our Approach
We use a small number of strictly necessary cookies that keep the Website and Service working. These load by default and cannot be switched off without breaking core functionality (e.g., login, security).
We also use optional analytics cookies from Microsoft Clarity to record sessions and produce heatmaps, so we can understand how visitors use our Website and improve it for florists. These cookies only load if you click Accept all on our cookie banner. If you choose Reject all (or close the banner without choosing), Microsoft Clarity is not loaded and no analytics cookies are set.
For aggregate page-level analytics we also use Fathom Analytics, a privacy-focused service that does not use cookies, does not collect personal data, and does not track individual users. Fathom is designed to be GDPR and PECR compliant without requiring consent and is not affected by your cookie choice.
We use Google Ads conversion measurement to understand whether an advert leads to a demo request, trial enquiry or booking. The Google tag loads with advertising and analytics storage denied by default. Google may receive limited, cookieless measurement signals while consent is denied. If you click Accept all, we send Google a consent signal that allows advertising and analytics storage for conversion measurement.
We use the ChatGPT Ads Measurement Pixel to understand whether a ChatGPT advert leads to an enquiry or booked appointment. The Pixel does not load until you click Accept all. Our code sends the event type and page context, not the contact details entered in our forms.
3. Cookies We Use
3.1 Strictly necessary (always on)
| Name | Provider | Purpose | Expiry |
|---|---|---|---|
| XSRF-TOKEN | Digital Florists | Security token to prevent cross-site request forgery attacks | 2 hours |
| digital-florists-session | Digital Florists | Maintains your session state (e.g., login status) | 2 hours |
3.2 First-party browser storage
The Website uses local storage and session storage for preferences, form continuity and measurement. These are browser-storage technologies rather than cookies. Local storage remains until it expires or you clear it. Session storage normally lasts until you close the browser tab.
| Name | Type | Purpose | Expiry |
|---|---|---|---|
| df_cookie_consent | Local and session storage | Stores your cookie banner choice so we do not ask again | 12 months, with a session-only fallback |
| df_marketing_attribution | Local storage | Keeps the first landing page, referring page without its query string, and any UTM campaign labels so a later demo or trial form can include them | 90 days |
| start_flow_state | Local storage | Lets you resume the trial enquiry, including the name, contact details, business name and plan you entered | 24 hours |
| df:sticky-cta:dismissed-until | Local storage | Remembers that you dismissed a trial prompt | 7 days |
| df_fathom_success_queue | Local storage | Temporarily keeps the event name and time for a confirmed form submission until Fathom is ready to count it | Up to 7 days |
| df_demo_flow_state | Session storage | Keeps the name, email address, phone number and shop name entered during the two-step demo form | Browser-tab session |
| df_demo_lead_id | Session storage | Keeps a generated reference that joins the two demo-form steps. It does not contain contact details | Until the demo form is completed or the browser tab closes |
| demoFormPrefill | Session storage | Temporarily keeps the contact details and shop context submitted in the demo form so the calendar can be pre-filled | Until the calendar loads or the browser tab closes |
| Other form and page-session markers | Session storage | Keeps validation markers, submission-event markers and a pricing-page visit within the current tab | Browser-tab session |
3.3 Analytics - Microsoft Clarity (only if you click "Accept all")
Microsoft Clarity is provided by Microsoft Ireland Operations Limited and acts as an independent data controller for the data it collects. Information collected may be transferred to Microsoft Corporation in the United States; Microsoft relies on the EU–US Data Privacy Framework (and the UK extension) for those transfers. For more, see Microsoft's Privacy Statement and the Clarity cookie list.
| Name | Type | Purpose | Expiry |
|---|---|---|---|
| _clck | First-party | Persists the Clarity user ID and preferences across visits | 1 year |
| _clsk | First-party | Connects multiple page views into a single recorded session | 1 day |
| CLID | Third-party (clarity.ms) | Identifies the first-time Clarity saw a user across any site using Clarity | 1 year |
| MUID | Third-party (Microsoft) | Identifies unique browsers visiting Microsoft sites; used for site analytics and other operational purposes | 1 year |
| ANONCHK | Third-party (Microsoft) | Indicates whether MUID is transferred to ANID (always 0 for Clarity) | 10 minutes |
| MR | Third-party (Microsoft) | Indicates whether to refresh MUID | 7 days |
| SM | Third-party (Microsoft) | Used in synchronising the MUID across Microsoft domains | Session |
What Clarity records: page interactions including mouse movement, clicks, scrolling and form interactions; the pages you visit; your approximate location (from IP); device, browser and operating system. We configure Clarity to mask sensitive form fields. Clarity does not record content you type into masked fields, and we do not use Clarity for advertising.
Note: Fathom Analytics does not set any cookies. It uses a privacy-preserving method that does not track individuals or store personal data, and runs whether or not you accept the optional cookies.
3.4 Conversion Measurement - Google Ads
The Google tag uses Consent Mode. Advertising storage, advertising user data, ad personalisation and analytics storage are denied by default. While consent is denied, Google says its tag does not write advertising or analytics cookies, but it may send cookieless signals containing the consent state and coarse technical information.
If you click Accept all, the consent settings are granted. Google may then read or write first-party conversion cookies such as _gcl_* and use existing Google cookies to attribute an advert click to a later enquiry or booking. We use this for conversion measurement, not to show third-party adverts on the Website. See Google's Consent Mode guide and Privacy Policy.
3.5 Analytics - Google Analytics 4 (only if you click "Accept all")
The Google tag currently has two linked Google Analytics destinations. If you accept optional analytics storage, Google Analytics may set _ga, _ga_D43RRWBF8R and _ga_7TNRSYH6MK to distinguish visits and maintain session state. These first-party cookies can remain for up to two years, subject to the retention setting in the linked Google properties. We are reviewing whether both destinations are still required.
If you reject optional cookies, analytics storage remains denied. See Google's Privacy Policy.
3.6 Conversion Measurement - ChatGPT Ads (only if you click "Accept all")
The ChatGPT Ads Measurement Pixel is provided by OpenAI. When you arrive after clicking a ChatGPT advert and accept optional measurement, the Pixel captures the privacy-preserving oppref click reference and stores it in a first-party __oppref cookie. It may also set a first-party __obref browser-reference cookie. These references help match a later lead_created or appointment_scheduled event to the advert.
After you accept optional measurement, we may send the same conversion from our server through OpenAI's Conversions API. Server events can include the event type and time, page address, the OpenAI references above, and SHA-256 hashed matching values such as the email address and our internal lead reference. The browser and server copies share an event ID so OpenAI can count the conversion once. We do not send raw contact-form values to OpenAI through the Conversions API.
The Pixel also sends the current page origin, event type, consent state, timestamp and technical delivery information. Where automatic advanced matching is enabled in Ads Manager, the Pixel may detect supported customer information and hash it in the browser before sending it. OpenAI says raw customer information is not sent through automatic advanced matching. See OpenAI's Measurement Pixel documentation, Conversions API documentation and Privacy Policy.
| Name | Type | Purpose | Expiry |
|---|---|---|---|
| __oppref | First-party | Keeps the ChatGPT advert click reference so a later enquiry or booking can be attributed | Provider-controlled. You can remove it through your browser settings. |
| __obref | First-party | Provides an opaque browser reference that can help match consented browser and server conversion events | Provider-controlled. You can remove it through your browser settings. |
4. Managing Your Cookie Choice
You can change or withdraw your consent at any time by clicking Cookie settings at the bottom of any page. We will re-display the banner so you can update your choice. If you reject optional measurement, Clarity recording stops, Google storage remains denied, the ChatGPT Ads Pixel stops sending future events and we do not send ChatGPT Ads server conversion events for that enquiry or booking. You can remove existing cookies through your browser settings.
Most browsers also allow you to:
- block all cookies;
- delete existing cookies; or
- block cookies from specific sites.
Note: Blocking strictly necessary cookies may prevent the Website and Service from functioning correctly (e.g., login, form submissions, security features).
For more information about managing cookies, visit: All About Cookies.
5. Third-Party Services
We may embed content from third-party services (e.g., videos, maps) on some pages. These services may set their own cookies when you interact with their content. We recommend reviewing their privacy policies for more information.
6. Changes to This Policy
We may update this Cookie Policy from time to time. We will post updates and revise the "Last updated" date.
7. Contact
If you have questions about cookies, contact:
privacy [at] digitalflorists.com
Digital Florists Ltd (company number 15423324), 7 Booker Ave, Liverpool L18 4QY, United Kingdom