Last updated: 28 September 2026
Terrivo uses very few cookies. Most of what we store sits in your browser’s own local/session storage, not in cookies. Below is every category we actually use, with the real names.
session_token: the HttpOnly cookie that keeps you signed in. terrivo_session_hint: a small non-secret flag so the app knows a session exists and does not have to ask the server for every anonymous visitor. terrivo_cookie_consent / _ts / _version (local storage): your own privacy choice and when you made it — without it we could not respect your decision. Checkout continuity: while you pay, Stripe keeps you on its own checkout session.
Your interface language, the Discovery starting point and travel mode you chose (session storage), and terrivo_privacy_prompt_shown, which only records that the privacy panel was already displayed. These are never used for analytics or profiling.
terrivo.visitor.v1 (local storage): a random, opaque visitor ID, created only after you press Accept. terrivo.pwaInstallTracked.v1: makes sure an app installation is counted once. With no choice, or after Decline, no analytics identifier is created and no analytics request is sent.
Our hosting platform sets two technical cookies on terrivo.app before any choice is made: __emg_vid (up to 12 months) and __emg_sid (30 minutes). They let the platform distinguish requests and sessions at infrastructure level. Terrivo does not read them, does not use them for analytics, profiling or advertising and does not link them to your account.
Terrivo shows no third-party advertising anywhere in the app, so nothing here is used to serve you ads. What we do measure is whether our own advertising works, and only if you choose "Accept all". Meta Pixel (Facebook/Instagram, pixel 2091297654518738) from connect.facebook.net: it measures page views on terrivo.app and sets Meta cookies (_fbp) on your device. We send no form content, e-mail addresses, phone numbers or flyer content, and no Purchase or Lead events; Advanced Matching and automatic event detection are switched off. Google tag / Google Ads (tag GT-MRLRR9JH, Google Ads account AW-18478727100) from googletagmanager.com: it is used for conversion measurement of our own Google Ads campaigns — essentially, whether an ad click ended in a LocalSite purchase. After you accept, Google may store conversion-linker values (cookie and local-storage names beginning with _gcl) on terrivo.app; we do not add any extra Google product and we do not use Google Analytics. Neither tool is loaded on a customer LocalSite or Local Guide page, on admin/account/payment pages, or on links that carry a token.
The Google tag is only present on terrivo.app and it starts in the "denied" state: ad_storage, ad_user_data, ad_personalization and analytics_storage are all denied before you make any choice, together with Google’s ads-data redaction. In that state no advertising cookie is written or read. Your choice in the privacy panel is what switches it: "Accept all" grants advertising and analytics, "Analytics only" keeps advertising denied, "Decline" keeps everything denied, and withdrawing later returns it to denied. If your browser sends Do-Not-Track or Global Privacy Control, the Google tag is not loaded at all.
When you open Stripe Checkout, Stripe sets its own cookies on its domain. When you sign in with Google, Google does the same on its domain. A customer LocalSite or Local Guide runs on Terrivo infrastructure and follows this same policy.
You can change or withdraw your choice at any time, without clearing your browser data: use the privacy shield in the bottom corner of every page, or “Cookie settings” in the footer. Choosing Decline there switches advertising measurement back to denied and stops analytics. Refusing analytics removes no feature: favorites, Discovery, Scan, LocalSite and Local Guide all keep working.
Questions about cookies or storage: marissa@terrivo.app.
Privacy-friendly analytics
Anonymous in-house analytics. Advertising measurement (Meta, Google Ads) only if you accept. Read more