Cookie Policy · SALOMON App

1. What cookies are

They are small files your browser stores when you visit a website. They keep you signed in, remember your preferences and measure how the platform is used.

This page also covers what we store using equivalent browser technologies (localStorage and sessionStorage), even though they are technically not cookies: to you it is the same thing, so we list them all the same.

2. Which cookies SALOMON uses

There are two groups: the necessary ones, always active because without them the site does not work or forgets what you chose, and the analytics ones, which are optional and stay off until you accept them.

There is no third, advertising group because we use no advertising cookies at all. See section 2.3.

2.1. Necessary (always active)

Cookie	Purpose	Lifetime
`auth_token`	Keeps your user session signed in	30 days
`admin_session`	Admin panel session (administrators only)	8 hours
`language`	Remembers which language you want the platform in (Spanish, English or Portuguese)	365 days
`salomon_app`	Remembers that you are browsing from inside the mobile app, so we show you the right version of each screen	Session
`salomon-theme`	Remembers whether you prefer the light or dark theme, across SALOMON and its products (CHAT, STUDIO, DRIVE, MONEY). It is stored for all of `salomonapp.com` so your theme follows you between them	365 days
`chat-model`, `chat-image-model`, `chat-video-model`	Remember which model you picked for chat, image and video, so we do not ask again in every conversation	365 days
`chat-product`	Remembers which SALOMON product you were talking to	365 days
`sidebar_state`	Remembers whether you left the sidebar open or collapsed	7 days
`sos_lang`	Only on the emergency pages (SOS / earthquake): remembers which language you are reading them in	365 days
`_ref` and `salomon_referral_code`	Store the referral code so we can credit whoever invited you when you sign up. They only exist if you arrive through an invitation link (`?ref=`); if you never use one, they are never created. The second one lives in `localStorage`	90 days (or until you complete your sign-up)
`salomon_cookie_consent`	Stores your own decision about the optional cookies, so we do not ask you again. It lives in your browser's `localStorage` and never travels to any server	Until you change it or clear the site data

Why the referral code is on this list. We could put a toggle on it, but the toggle would be decorative: that cookie is written the moment you open the invitation link, which is precisely when you have not decided anything about cookies yet. And if it is not written, the person who invited you does not get credited. It is first-party, we share it with nobody, it builds no profile, and it only appears if you yourself arrived through an invitation — so we declare it as what it is, necessary, instead of offering you a button that does not turn it off.

2.2. Analytics (optional)

We use our own analytics: the data goes to our own servers and to no third party. We do not use Google Analytics, Meta, TikTok, Hotjar, Mixpanel or any external measurement tool.

Exactly what we store with each event. We would rather spell it out than summarise it:

The anonymous visitor and session identifiers (_csv and _css, in the table below) and, if you are signed in, your internal user identifier — never your email address or your name.
What happened and where: the event name (for example page_view or click_register), the page address, its title, the page you arrived from and, where it applies, a numeric value — how far down you scrolled, or how many seconds you stayed — plus some context belonging to the event itself (for example, which video was played).
Your IP address and the User-Agent your browser sends, along with what we derive from it: device type (phone, tablet or computer), operating system and browser.
The utm_* campaign tags, if you arrived through a link of ours that carried them. We add those ourselves, they identify nobody across sites, and they are the only part of the address we keep: advertising click identifiers (fbclid, gclid and the like) are stripped out before anything is saved.

This tells us how many visits we get, which pages are viewed, how long sessions last and where people get stuck. The IP address specifically is what lets us tell real visits apart from automated traffic and rate-limit abuse of the site. We build no advertising profile of you out of any of it, we do not combine it with data from other companies, and it never leaves our servers.

They are off until you accept them and you can reject them without losing any feature. The cut-off sits in the function that sends the events, not in the screen that calls it: if you say no, nothing is sent — neither the automatic measurement nor the one on buttons — and the _csv cookie is never even created.

Cookie	Purpose	Lifetime
`_csv`	Unique visitor identifier (our own analytics)	365 days
`_css`	Session identifier (our own analytics). Not a cookie: it is kept in the browser's `sessionStorage` and disappears when you close the tab	30 minutes of inactivity
`_csref_tracked`	Avoids counting the same click on an invitation link twice. Also in `sessionStorage`	Until you close the tab

2.3. Advertising: none

We use no advertising cookies. There are no Meta (Facebook/Instagram), Google Ads or TikTok pixels on this site, nor any other ad network; we do not sell or share your browsing with advertisers, and we do not build advertising profiles about you. That is why the cookie banner does not offer you an advertising checkbox either: there is nothing to switch on.

What used to be here and what we did about it. Until August 2026 this site had the Meta pixel installed. It was removed, and on September 1, 2026 we also removed the last pieces still wired to it: reading its cookies (_fbp, _fbc) and forwarding the click identifier (fbclid) that Meta appends to the address when somebody arrives from an ad. That data always stayed on our own servers: it was never sent to Meta or to any advertiser. It is no longer collected at all.

The same holds inside the iOS and Android apps.We do not track you across other companies' apps or websites, and we do not share identifiers with data brokers, so we do not collect your device's advertising identifier (IDFA on iOS, AAID on Android) and we do not ask you for App Tracking Transparency permission: we do not need it, because we do not carry out that tracking.

If we ever add ad measurement, we will update this page with the new date and ask you explicitly before loading anything.

3. How to control your cookies

Change your mind whenever you want. This button forgets your decision and brings the banner back so you can choose again:

You also have these other options:

Initial banner: the first time you visit SALOMON, a banner appears where you can accept everything, reject the optional ones or customise category by category.
Clearing the site data: your decision is stored only in your browser. If you clear salomonapp.com data, the banner shows up again and you can choose anew.
From your browser: you can delete or block cookies directly:

Important: if you delete or block the necessary cookies (auth_token, admin_session), you will not be able to sign in to SALOMON. This is a technical requirement, not a commercial decision.

4. What we do not do

We do not sell or rent your browsing data to third parties.
We do not use Google Analytics, Meta Pixel, TikTok Pixel or any other third-party measurement or advertising tool.
We do not install advertising cookies.
We do not follow you across other companies' apps or websites, neither inside nor outside our mobile apps.

5. Changes to this policy

If we add new cookies or modify the existing ones, we update this page with the new date. If the changes affect non-essential cookies, we will ask for your consent again the next time you come in.

6. Contact

Questions about cookies or privacy: privacy@salomonapp.com.