Skip to main content
Sign in Start free trial

Last updated 2026-05-21

LEGAL

Cookies on DineRoute.

Last updated 2026-05-21. Every cookie we set, what it does, how long it lasts, and what you can do about it.

What cookies are

A cookie is a small text file that a website stores in your browser. Cookies do not run code on your computer. They cannot read other files on your device. They are used to remember things between page loads — that you are logged in, that you accepted a banner, that you arrived from a particular ad campaign. Some cookies are first-party (set by the site you are visiting); some are third-party (set by another domain, usually for advertising or analytics).

DineRoute uses a small number of first-party cookies. We try not to set anything we cannot justify. Below is the full list, separated by where you encounter it.

Cookies we set on dineroute.com (the marketing site)

On the public marketing site at dineroute.com, we use these cookies to understand how visitors find us and what content actually helps restaurants. We try to keep the list short and we do not run ad-targeting cookies on dineroute.com itself.

CookiePurposeTTLProvider
_ga Google Analytics 4 — assigns a random ID so GA4 can count unique visitors to dineroute.com. 2 years Google
_ga_* Google Analytics 4 — per-property session state for dineroute.com. 2 years Google
_clck Microsoft Clarity — anonymous session recording and heatmaps so we can see where visitors get stuck on dineroute.com. 1 year Microsoft
_clsk Microsoft Clarity — per-session ID used to stitch a single visit's events together. 1 day Microsoft
li_fat_id LinkedIn Insight Tag — used to measure conversions from our own LinkedIn ads about DineRoute. 30 days LinkedIn
dr_ref First-party cookie storing the inbound referrer and UTM tags so we can attribute signups to the right channel. 30 days DineRoute
dr_consent First-party cookie remembering whether you have dismissed our cookie banner (once we ship one). 365 days DineRoute

Cookies we set on restaurant smart-link pages

On the restaurant-branded smart-link pages we host (for example malai.dineroute.com/southlake or a restaurant's own custom domain pointed at DineRoute), we set only the cookies needed to route a diner to the right ordering platform and to dedupe attribution events. We do not set third-party advertising cookies on smart-link pages by default. The restaurant operator's installed pixels — Meta Pixel, Google Ads tag, GA4, TikTok Pixel — will set their own cookies when they fire, and those cookies belong to the restaurant's ad accounts, governed by the platform's policy.

CookiePurposeTTLProvider
dr_attrib First-party. Stores UTM tags and ad-platform click IDs (fbclid, gclid, ttclid) for the visit so a conversion fired later can be tied back to the campaign. 30 days DineRoute
dr_vid First-party. A random visitor ID we use to dedupe events across a single session. Not linked to a name, email, or any external identifier. 365 days DineRoute
dr_admin_session First-party. Authenticated session cookie set only inside the admin dashboard at /admin. HttpOnly, Secure, SameSite=Lax. Session DineRoute
dr_csrf First-party. CSRF protection token paired with dr_admin_session inside the admin dashboard. Session DineRoute

If a restaurant operator installs Meta Pixel, Google Ads tag, GA4, or TikTok Pixel through DineRoute, those platforms set their own cookies (_fbp, _gcl_au, _ga, _ttp, etc.) when their tags fire. Those cookies belong to the restaurant's ad accounts, not to DineRoute. The restaurant is responsible for any consent banner required on its smart-link page.

Your choices

You have several ways to manage cookies:

  • Browser controls. Every modern browser lets you block cookies, delete cookies on close, or open a private window that does not persist cookies. Chrome, Safari, Firefox, and Edge all expose this in Settings → Privacy.
  • Do Not Track. If your browser sends a Do Not Track header to dineroute.com, we honor it by disabling LinkedIn Insight Tag and Microsoft Clarity for your session. GA4 still records aggregate visit counts.
  • Opt out of GA4. Install the official Google Analytics opt-out browser add-on to block GA4 globally.
  • Opt out per platform. Most ad platforms expose a personal opt-out: Meta ad preferences, Google ad settings, TikTok privacy controls, and LinkedIn ad settings.
  • Industry opt-out tools. The Digital Advertising Alliance's WebChoices and the Network Advertising Initiative's opt-out page cover most participating networks in one place.

Manage cookie preferences

Manage cookie preferences

We do not yet ship an in-page cookie consent banner with per-vendor toggles. A full consent banner is coming with our EU launch in Q3 2026, when we deploy a Supabase EU project and add per-region cookie controls.

Until then, the most reliable way to control cookies on dineroute.com is through your browser:

  1. Chrome: Settings → Privacy and security → Cookies and other site data → "Block third-party cookies" or "See all cookies and site data" → search dineroute.com → Remove.
  2. Safari: Settings → Privacy → Manage Website Data → search dineroute.com → Remove.
  3. Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data, or Manage Data → search dineroute.com.
  4. Edge: Settings → Cookies and site permissions → Manage and delete cookies and site data → See all cookies and site data → search dineroute.com.

If you have a specific request — for example, a request that we stop collecting any analytics data tied to your visit — email privacy@dineroute.com and we will honor it within five business days.

Updates to this policy

We update this page whenever we add or remove a cookie, change a TTL, or change the categories of vendors we use. Material changes are announced in our changelog at /changelog and, for active customers, by email.

QUESTIONS

A real person reads privacy@.

Email us with a cookie question, an opt-out request, or a 'why does this cookie exist' question. We answer them all.

Email privacy team Read the privacy policy

Anderson Collaborative LLC · Florida LLC · EIN 84-3628405