Privacy policy.

Introduction

DineRoute is a software service operated by Anderson Collaborative LLC ("Anderson Collaborative", "we", "us"), a Florida limited liability company with EIN 84-3628405. This policy explains what personal information we collect from restaurant operators (our customers) and from end diners who visit a DineRoute-powered smart-link page, how we use that information, and the rights you have over it.

This policy applies to the DineRoute marketing website at dineroute.com and to the restaurant-branded smart-link pages we host on behalf of our customers (typically at subdomains like malai.dineroute.com or at a restaurant's own custom domain). It does not apply to the third-party ordering platforms — DoorDash, Uber Eats, Grubhub, ChowNow, and others — that a diner is redirected to after tapping a tile. Each of those platforms has its own privacy policy that takes over from the moment a redirect happens.

Information we collect

From restaurant operators

When you sign up for DineRoute we collect the information needed to run your account:

• Account details: name, email address, password (stored as a salted hash), restaurant business name, and billing address.
• Payment information: handled by Stripe. We never see or store your card number. Stripe returns us a token and the last four digits for receipt display.
• Integration credentials: API tokens for Meta Conversions API, Google Ads, GA4, and TikTok Events API that you choose to connect. These are encrypted column-level in our database.
• Configuration data: your restaurant locations, brand assets, platform URLs, and tracking preferences.
• Usage data: pages you visit in the admin dashboard, features you use, and aggregate session metadata used to improve the product.

From end diners on smart-link pages

When someone visits a DineRoute-hosted smart-link page (for example malai.dineroute.com/southlake), we collect a deliberately narrow set of attribution data on behalf of the restaurant that owns the page:

• The URL visited and the page referrer.
• Querystring parameters present on the URL, including UTMs, fbclid (from Meta ads), gclid / gbraid / wbraid (from Google ads), ttclid (from TikTok ads), and any custom campaign tags.
• The visitor's IP address and User-Agent string.
• A first-party cookie (dr_vid) we set so we can dedupe events across a single browsing session, and a separate attribution cookie (dr_attrib) that records which ad campaign drove the visit.
• Which platform tile a visitor tapped, and the timestamp of that tap.

We do not collect the diner's name, email, phone number, mailing address, payment information, or the contents of any order they place. We never see what was ordered — the order itself happens on the platform a diner taps through to (DoorDash, the restaurant's own ordering site, etc.).

How we use it

We use the information above for the following purposes, and only for these purposes:

• To operate the service: serve the smart-link page, route the diner to the platform they chose, and surface analytics in the restaurant's admin dashboard.
• To forward server-side conversions: at the restaurant's instruction, we fire deduplicated server-to-server events to Meta Conversions API, Google Ads, GA4 Measurement Protocol, and TikTok Events API. These events appear in the restaurant's ad accounts, not ours.
• To bill and support our customers: process subscription payments, send transactional email, respond to support requests.
• To improve the product: aggregate usage analytics, debug errors, and prioritize features.
• To comply with the law: respond to lawful requests, prevent fraud, and enforce our terms.

We do not sell personal information. We do not share personal information across customers — a restaurant's data is its own and we enforce that with database-level row-level security.

Cookies and tracking

DineRoute sets a small number of first-party cookies. None of them are third-party. None of them track you across other websites.

• dr_attrib — first-party cookie on the smart-link page, TTL 30 days. Stores the campaign attribution payload (UTMs and click IDs) so that a conversion fired later can be tied back to the ad that drove the visit.
• dr_vid — first-party cookie on the smart-link page, TTL 365 days. A random visitor ID used to dedupe events across a session. Not linked to a name or email.
• dr_admin_session — first-party cookie on the admin dashboard, session-only. Standard authenticated session cookie. HttpOnly + Secure + SameSite=Lax.
• dr_csrf — first-party cookie on the admin dashboard, session-only. CSRF token paired with dr_admin_session.

On the marketing site (dineroute.com), we may also set analytics cookies — see our cookie policy for the full list and how to manage them.

Restaurant operators who install their own Meta Pixel, Google Ads tag, GA4, or TikTok Pixel through DineRoute should know that those pixels — when they fire on the smart-link page — will set the cookies that those platforms set. Those cookies are governed by the platform's policy, not ours, but they belong to the restaurant's ad account, not to DineRoute.

Sharing with third parties

We share information with the following categories of recipients, and no others:

• Ad platforms — at the restaurant operator's direction, we forward deduplicated conversion events to Meta, Google, TikTok, and the GA4 Measurement Protocol endpoint. The data sent is limited to event name, click ID, page URL, hashed IP, hashed User-Agent, and timestamp.
• Subprocessors — vendors who help us run the service: Supabase (database), Netlify (hosting), Cloudflare (DNS and edge), Resend (email), Stripe (payments). Each is bound by a data processing agreement.
• Legal authorities — when required by a valid legal process. We commit to push back on overbroad requests and to notify the affected customer where we are legally permitted to do so.
• Successor entity — if we are acquired or merged, your data may transfer to the successor, but only under terms at least as protective as this policy. We will notify customers at least 30 days in advance.

We do not share personal information with advertisers, data brokers, or any party for advertising purposes outside the explicit forward-to-your-own-ad-account flow described above.

Your rights

Depending on where you live, you may have specific rights over your personal information. We honor the following rights for every visitor, everywhere, regardless of jurisdiction:

• Access — you can ask what we have about you and we will return it within 30 days.
• Correction — you can ask us to correct inaccurate data.
• Deletion — you can ask us to delete your data. We will do so within 30 days unless we are required by law to retain it (for example billing records).
• Portability — you can request a machine-readable export of your data.
• Opt-out of sharing — restaurant operators can disable any specific ad-platform integration any time from the admin dashboard.

California residents (CCPA / CPRA). You have the right to know what categories of personal information we collect, to delete it, to correct it, and to opt out of "sales" or "sharing" of personal information (we do neither). Submit requests to privacy@dineroute.com.

EU and UK residents (GDPR / UK GDPR). You have the additional right to lodge a complaint with your local supervisory authority and to request restriction of processing. The lawful basis for our processing is contract performance (for restaurant operators) and legitimate interests in measuring ad performance (for end diners on smart-link pages). Anderson Collaborative LLC is the controller for marketing-site data and a processor for restaurant operators.

Other US states with comprehensive privacy laws (Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, and others) have rights similar to California's. We honor them on the same intake channel.

To exercise any right, email privacy@dineroute.com. We respond within 30 days and never charge a fee for a reasonable request.

Data retention

Raw event data on smart-link pages is retained for 90 days, then aggregated and deleted. Aggregates (counts and Match Quality scores, no individual identifiers) are retained indefinitely so historical dashboards stay accurate. Account-level data is retained for the life of the account plus 30 days after cancellation. Billing records are retained 7 years for tax and accounting compliance.

Children's privacy

DineRoute is not directed at children under 13. We do not knowingly collect personal information from anyone under 13. If you believe we have collected information from a child under 13, email privacy@dineroute.com and we will delete it.

International transfers

Our infrastructure is hosted in the United States (AWS us-east-1). If you are visiting a DineRoute-hosted page from outside the United States, your data is transferred to the United States for processing. For EU and UK transfers we rely on the Standard Contractual Clauses and, where applicable, the UK Addendum and the EU-US Data Privacy Framework.

Changes to this policy

We may update this policy when we add a new subprocessor, change a retention window, or expand the rights we honor. We will update the "Last updated" date at the top of the page and, for material changes, notify customers by email at least 30 days in advance.

Contact us

Anderson Collaborative LLC
Privacy team
privacy@dineroute.com

For security-specific issues, see our security page and email security@dineroute.com.