Cookie Policy

Last updated:

Short version: this website sets analytics cookies — visitors from the EEA, the UK and Switzerland are asked first, everyone can turn them off — the CRM sets exactly one — to keep you signed in — and the widget on our customers’ websites sets none at all. Below is everything we store in your browser, where and why.

Cookies and browser storage

Cookies are small files a website saves in your browser and that the browser sends back with every request to that website. Local storage and session storage are similar places in the browser where a page can keep data; they are not sent to the server automatically. Session storage is cleared when you close the tab, local storage stays until it is deleted. The law treats all of them the same way, so this policy lists both.

We sort what we store into three types:

  • Strictly necessary — the service does not work without it (for example, staying signed in).
  • Preferences — remembers choices you made, such as the theme or language.
  • Analytics — helps count visits and sources of traffic.

This website

This website (the home page, articles, documentation, legal pages and the contact form) uses no advertising or tracking across other sites. It sets analytics cookies — if you are in the European Economic Area, the United Kingdom or Switzerland, only with your consent given in the cookie banner — and keeps a few preferences in local storage:

NameStoragePurposeTypeLifetime
site_localeLocal storageRemembers that you picked a language, so we stop suggesting another onePreferencesUntil you clear it
__ph_opt_in_out_…Local storageYour choice about analytics: accepted, declined, or switched on by default outside the EEA, the UK and SwitzerlandStrictly necessaryUntil you clear it
ph_…_posthog, ph_…_posthog_cpmCookie and local storageA random visitor ID and the current session for PostHog analytics and session recordings — not set if you declineAnalytics1 year
_ga, _ga_…CookieA random visitor ID and the current session for Google Analytics — set only together with PostHog analytics and on the same choiceAnalytics2 years

Analytics: PostHog

To understand which pages and sources bring visitors and where the site gets in their way, we use PostHog in its EU cloud (Frankfurt).

  • Who is asked. If your browser’s time zone is in the European Economic Area, the United Kingdom or Switzerland — or we cannot tell — we show the cookie banner, and until you answer, PostHog stores nothing and sends nothing. Everywhere else analytics is on from the first visit, and you can turn it off at any time.
  • With analytics on, PostHog records page views, clicks and the source of your visit, and may record your session on this website (what you scroll and click). All form fields are masked and never recorded. Once you register, we link these events to your account ID so we can see which pages led to sign-ups. We do not send your name or email to PostHog.
  • If you decline or turn it off, PostHog only counts the visit anonymously, without cookies or browser storage: a hash of your IP address and browser is calculated on PostHog’s servers with a key that changes every day, and nothing is recorded.

You can change your choice at any time: . The same link is at the bottom of every page.

Analytics: Google Analytics

Alongside PostHog we use Google Analytics 4 (Google Ireland Ltd. and Google LLC) to see where visitors come from, including Google Search.

  • Same choice. Google Analytics follows the same cookie banner and the same “Cookie settings” link as PostHog. Until analytics is on — in the EEA, the UK and Switzerland that means until you agree — its script is not even loaded.
  • What it records: page views, the source of your visit, device, browser and approximate location. We do not send form data, your name or your email to Google Analytics. Advertising features (Google Signals, remarketing, data sharing with Google Ads) are off.
  • If you decline or turn analytics off, the Google Analytics script is not loaded, and any _ga cookies already set are deleted.
  • Where the data is processed. Google processes it, including in the United States; the transfer relies on the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses. See the Google Privacy Policy.

The home page also checks whether the CRM has saved a sign-in token (token, see below) and, if so, takes you straight to your dashboard. It only reads it and never sends it anywhere.

When you press “Try the demo” (and, where enabled, when you send the contact form), the page loads Cloudflare Turnstile, which checks that you are a person. Turnstile runs in its own frame from Cloudflare’s domain under Cloudflare’s privacy policy.

The Sitecog CRM

The CRM uses one cookie and a few entries in browser storage:

NameStoragePurposeTypeLifetime
refresh_tokenCookie (HttpOnly, Secure)Keeps you signed in and renews your sessionStrictly necessary7 days
tokenLocal storageShort-lived access token for requests to the serverStrictly necessaryUntil you sign out
selected_domainLocal storageWhich of your websites is open in the CRMPreferencesUntil you clear it
crm_themeLocal storageLight or dark themePreferencesUntil you clear it
i18nextLngLocal storageInterface languagePreferencesUntil you clear it
Interface stateLocal storageOpen pages and folders, dismissed noticesPreferencesUntil you clear it
demo_untilLocal storageWhen the demo sandbox ends (demo only)Strictly necessaryUntil the demo ends
invite_tokenSession storageKeeps a team invitation while you sign in or registerStrictly necessaryUntil the tab is closed

When you pay for a plan by card, you are taken to a checkout page hosted by Creem, our Merchant of Record, on its own domain. Sitecog sets no cookies for payments; whatever that page stores in your browser belongs to Creem and is governed by Creem’s own policies.

The widget on our customers’ websites

Websites built with Sitecog load our widget (widget.js). It sets no cookies. It keeps the following in the local storage of the website you are visiting; the website owner decides which features are on and is responsible for informing you and asking for consent where needed.

NamePurposeTypeLifetime
crm_vidRandom visitor ID, to tell new visitors from returning onesAnalyticsUntil cleared
crm_sidCurrent visit (session) IDAnalyticsNew session after 30 minutes of inactivity
crm_satTime of the last activity, to know when a session has endedAnalyticsUntil cleared
crm_consentYour answer to the analytics consent request (consent mode only)Strictly necessaryUntil cleared
crm_chat_tokenLets you return to your chat conversationStrictly necessary (chat)Up to 180 days
crm_chat_seq, crm_chat_readWhich chat messages you have already received and readStrictly necessary (chat)Until cleared
crm_chat_cfgCached chat settings of the websiteStrictly necessary (chat)10 minutes
crm_site_access, crm_site_access_atYour sign-in to the website’s user account, if the website offers oneStrictly necessary (sign-in)15 minutes, renewed while you are signed in
crm_site_refreshRenews that sign-inStrictly necessary (sign-in)30 days
crm_site_userBasic details of the signed-in user (such as email) to show in the pageStrictly necessary (sign-in)Until you sign out
crm_site_cfgCached sign-in settings of the websiteStrictly necessary (sign-in)10 minutes
crm_site_lockStops several open tabs from renewing the sign-in at the same timeStrictly necessary (sign-in)A few seconds

Advertising cookies the widget reads

To show the website owner which ads brought a visitor, the widget reads — but never sets or changes — advertising cookies that are already present on that website because of other tools: _ga, _ga_*, _gcl_aw, _gcl_dc, _gcl_gb, _ym_uid, _fbp and _fbc.

A website owner can turn on consent mode by adding data-consent="required" to the widget’s script tag and connecting it to their cookie banner. Until you agree, the widget then sends no analytics, reads no advertising cookies and does not create crm_vid, crm_sid or crm_sat; if you refuse or withdraw consent, these entries are deleted. Forms and chat, which you start yourself, keep working without analytics identifiers.

If your browser sends a Global Privacy Control signal, the widget never reads advertising cookies — in any mode and regardless of consent.

How to control cookies and storage

  • Browser settings. Every modern browser lets you view and delete cookies and site data, block them for some or all websites, and use private mode. Look for “Cookies and site data” or “Privacy” in your browser’s settings.
  • Clearing local storage. Deleting a site’s data in the browser settings also clears its local storage. Deleting the CRM’s data signs you out; deleting our widget’s data on a website makes it treat you as a new visitor.
  • Global Privacy Control. Turn it on in your browser or a privacy extension to stop the widget from reading advertising cookies everywhere.
  • Consent banners. On websites that use consent mode, you can change your choice through that website’s cookie banner or settings.

If you block strictly necessary storage, signing in to the CRM and the chat on websites may not work.

More information

How we handle personal data in general is described in the Privacy Policy. Questions about cookies? Write to us through our contact form or by email at support@sitecog.com.