Cookie Policy

Last updated: September 24, 2026

This policy lists the cookies salalem.com sets, what each one is for, and how long it lasts. It covers this website. The Salalem platform and apps are covered by the Privacy Policy, and the sign-in cookies described below are shared between them.

The cookie that records your answer

The banner on your first visit writes one cookie, salalem_consent, recording whether you accepted or declined. It lasts a year, is limited to this site, and is the only cookie set before you answer. Without it the banner could not tell that you had already replied, and would ask again on every page.

What accepting turns on

Accepting loads Google Tag Manager, which is how we measure which pages and calls to action people use. Until then nothing is requested from Google at all: declining does not load the tag and switch it off, it means the file is never fetched. Once loaded, the tags configured in the container set Google's own analytics cookies, which distinguish one visit from another and expire on Google's schedule rather than ours. We use what they report in aggregate — page views, referrers, which buttons get clicked — and never to identify you by name. Accepting also sets one cookie of our own, salalem_lead_source, kept for 30 days. It holds the campaign name and the page a visit started on, so a demo request sent later in the same visit can be tied to that campaign. Declining means we record a campaign only when it is still in the address of the page the form is on.

The cookies that keep you signed in

Signing in to Salalem sets cookies that carry your session: a token cookie holding your access token, which expires an hour after sign-in; a session cookie; and a CSRF token that lets the platform tell your own form submissions from a forged one. They are issued across salalem.com and its subdomains so that one sign-in works across the website, the learner app, and the admin console. These are not optional. There is no version of a signed-in session that works without them, so the banner does not offer to decline them — signing out or clearing them ends the session.

How this site knows you are already signed in

If you are already signed in, this site offers a link straight back to your learning rather than the sign-in page. It works by forwarding your cookies to the Salalem backend and asking one question: is this visitor signed in. A yes or no comes back and nothing else — the cookies are not read, parsed, or logged by this website, and no new cookie is set to remember the answer.

Changing your answer

Your answer is stored for a year. To change it, clear cookies for salalem.com in your browser and the banner will ask again on your next visit. Every browser also lets you block or delete cookies for a site outright, and browser settings override anything on this page. Declining, or blocking cookies entirely, costs you the measurement and nothing else: every page, document, and form on this site works the same way.

Other Salalem addresses

A certificate verification page at salalem.com/verify sets no cookies and needs no sign-in, so a credential can be checked by anyone holding the link. Signing in happens at id.salalem.com, which sets the session cookies in the third section above. The learner and admin applications set cookies of their own once you are inside them; what they hold and how long they are kept is covered by the Privacy Policy rather than here.