Understand the storage technologies we use and stay in control of non-essential cookies.
Last updated 8 October 2026PECR & UK GDPR
UK cookie notice
This Cookie Policy explains how Dropdsh uses cookies, local storage, software development kits and similar storage or access technologies on its website and web applications. It should be read with our Privacy Policy.
We use strictly necessary technologies without consent where they are essential to provide a service you request. We ask before using non-essential analytics, advertising or preference technologies where UK law requires consent.
Your choices
Accept all permits the non-essential categories described in the consent panel.
Reject all keeps non-essential technologies off while necessary security and service functions remain available.
You can change or withdraw a choice at any time using the cookie controls when available or by clearing the Dropdsh site data in your browser.
Refusing non-essential technologies does not prevent ordinary booking or account use, although optional features may be less personalised.
1. What cookies and similar technologies are
A cookie is a small text file stored on a browser or device. Similar technologies include local storage, session storage, pixels, tags and mobile SDK storage. They can remember a session, protect a form, preserve preferences, support payments or help measure service performance.
Some technologies last only for the browser session. Others remain until their stated expiry or until you remove them. First-party technologies are set by Dropdsh; third-party technologies are set or read by another provider whose feature you use.
2. How Dropdsh uses them
We use storage and access technologies to authenticate users, prevent fraud, protect forms, remember consent and interface choices, support checkout, load maps and addresses, provide social sign-in where enabled, enable live service features and understand technical performance.
We do not treat a technology as “strictly necessary” merely because it is convenient. Where a feature is optional or primarily benefits analytics or marketing, we require the appropriate choice before activating it.
3. Categories we may use
Category
Purpose
Consent position
Strictly necessary
Login sessions, account security, load balancing, fraud controls, form protection, checkout continuity and recording your cookie choice.
Used where essential to provide the requested service; consent is not normally required, but information is still provided.
Preferences
Remembering optional display, language, navigation or interface choices.
Used with consent unless the preference is essential to a feature you specifically request.
Analytics and performance
Understanding visits, errors, feature use and performance so we can improve Dropdsh.
Used only after valid consent where required.
Marketing
Measuring campaigns or personalising advertising across services.
Used only after valid consent; rejecting it must be as easy as accepting it.
4. Technologies and services used by the platform
Technology or provider
Why it may be used
Typical category
Dropdsh / Laravel session and security tokens
Keeping you signed in, protecting requests, remembering booking progress and maintaining security.
Strictly necessary
Dropdsh local or session storage
Remembering cookie choice, theme, dashboard navigation and short-lived interface state.
Necessary or preference, depending on purpose
Stripe
Secure card, wallet, Direct Debit, top-up and subscription checkout; fraud prevention and payment authentication.
Strictly necessary when you choose a payment feature
Google Maps Platform
Address search, map display, routing, geocoding and location-based booking features.
Necessary for the map feature requested; any separate analytics use requires consent
Firebase / Google or Apple sign-in
Optional social authentication, push notifications, order chat or live-location functionality where enabled.
Necessary for the optional feature requested; unrelated analytics requires consent
Operational communications and real-time services
Delivering notifications, chat, order status and live service updates.
Strictly necessary for the requested live service
Analytics or marketing tools
Only if configured and listed in the consent controls.
Analytics or marketing
Exact names and lifetimes can change when providers update their technology. The browser’s storage panel and any in-product preference centre show the technologies active on your device. Provider technologies are also governed by the provider’s own notice.
5. Consent, rejecting and withdrawing
Where consent is required, it must be a clear positive choice. Silence, continuing to browse and pre-ticked controls are not consent. “Accept all” and “Reject all” should be presented with equal prominence, and no non-essential technology should be activated before a choice.
You can withdraw consent without affecting processing that occurred lawfully before withdrawal. Clearing site data can reset your choice, so the consent panel may appear again. We may also ask again after a material change or a reasonable period.
Need to reset your choice? Clear cookies and site data for the Dropdsh domain in your browser, then reload the site. Where a “Cookie settings” control is displayed, you can use it instead.
6. Browser and device controls
Browsers generally allow you to inspect, block and remove cookies or site data. Blocking all storage may prevent login, checkout, security and booking features from working. Mobile operating systems also provide controls for app tracking, notifications, location and advertising identifiers.
Do-not-track signals are not implemented consistently across browsers. We honour the consent choice made through our own controls and any legally recognised signal we are required to support.
7. Updates and contact
We update this policy when providers, purposes or legal requirements change. The “Last updated” date on this page identifies the current version.