Cookie Policy

Cookies are small text files stored on your device when you visit a website. We also use similar technologies such as local storage. We group them into two kinds: strictly necessary (essential) and non-essential (analytics).

These keep the site working and secure. They do not require consent because the service cannot function without them.

• dm_session — keeps you signed in to your Desk Hero account.
• admin_token — keeps admins signed in to the dashboard.
• deskmatch-cookie-consent — remembers your cookie choice so we don’t ask again.
• Short-lived security and sign-in challenge cookies used during login.

With your okay, we use privacy-respecting product analytics (PostHog) to understand which features are useful and where people get stuck. These are only set if you choose “Accept” on our cookie banner, and never if your browser sends a “Do Not Track” signal.

• deskmatch-growth-attribution — keeps privacy-safe first- and last-touch campaign details (such as source, campaign, keyword and Area) for up to 90 days so we can understand which activity leads to genuine DeskMatches. It never contains names, email addresses or form answers.
• deskmatch-funnel-id — a random browser-session identifier for consented product analytics. It contains no contact details and is replaced after you withdraw and later accept again.

You can change your mind at any time. Cookie preferences re-opens the banner so you can choose again — your new choice overwrites the saved deskmatch-cookie-consent cookie. Rejecting non-essential cookies disables browser analytics immediately and removes the saved growth-attribution cookie.

Consented enquiry analytics may be queued on our server for up to 24 hours, with limited retries if delivery fails. When you withdraw, we ask the server to cancel pending delivery for that browser session. Once the server acknowledges withdrawal, it will not start further delivery attempts. Requests already sent cannot be recalled.

If you are offline, the server cannot receive your withdrawal until you reconnect. Essential local storage keeps the pending withdrawal request so we can retry while the site is open or on your next visit; it is removed after acknowledgement and is never used for tracking. Clearing or blocking that storage can prevent the retry. This does not withdraw a separate browser or device's consent.

Some essential features rely on trusted providers (for example Stripe for payments and Google for optional sign-in), which may set their own cookies when you use those features. See our Privacy Policy for how we handle personal data.