Cookie and device storage notice

Storage needed to provide the service

These technologies are used only to provide a feature you ask for or remember its presentation. Under PECR they do not require an accept-all banner, but they still have to be explained.

• sarafan_session: an HttpOnly, Secure production cookie that keeps you signed in. It lasts up to the session lifetime configured by the service and is removed when you sign out.
• sarafan.locale: remembers your interface language for one year.
• sarafan.city: remembers the city you chose for 180 days so navigation can return to it.
• sarafan.anon in localStorage: a random product key used only to preserve contact introductions made before sign-in and enforce anti-harvesting limits. It is never used for statistics. It has no fixed browser expiry; clearing site data removes it. If storage is unavailable, product requests use a random in-memory key that disappears on reload.
• sarafan.statistics-day in localStorage: a dedicated random UUID used only to deduplicate the JS-enabled browser count during the current UTC day. It is never copied into sarafan.anon, an account or a session, and is replaced when the UTC day changes. Objecting removes it locally and sends the current value once for best-effort removal of that day’s server fingerprint. If storage or secure UUID generation is unavailable, this statistic stays off.
• sarafan.analytics-opt-out in localStorage: exists only after you switch statistical analytics off. Its sole value is 1; it is not an identifier, has no fixed expiry, and is removed when you switch analytics back on or clear site data.
• sarafan.non-essential-consent in localStorage: the explicit accept, reject or granular choice for optional technologies. It stores the notice version, the exact disclosed-inventory revision, decision time and one boolean per category; it has no fixed expiry, and a stale notice or inventory grants nothing.
• sarafan.product-analytics-tab in sessionStorage: a random UUID created only after Analytics consent. It is scoped to the current tab, sent only to the fixed credentialless page-count endpoint and removed when the tab closes or consent is withdrawn. The server stores only a UTC-day-salted hash until roll-up.
• sarafan.attribution in localStorage: a separate random UUID and its expiry, created only after Registration attribution consent. It lives for no more than seven days, is sent only to the fixed attribution touch and signup boundaries, and is removed on withdrawal, expiry or stale consent. The server stores only its hash.
• Legacy sarafan.visit-day is no longer read. Opening this notice removes the obsolete value when browser storage is available; clearing site data removes it as well.
• sarafan.profile-draft:* in localStorage: an unsaved service or community listing draft. It stays only in this browser, expires after seven days, and is removed after a successful save.

First-party statistics and your objection

By default SARAFAN uses narrow first-party statistics to understand whether the catalogue works: aggregated arrivals, catalogue searches and JS-enabled browser-days. This is not person-level advertising attribution, targeted advertising, profiling or cross-site tracking. Advertising click identifiers and their values are not inspected or sent; a campaign-label candidate contributes only when it matches an active label registered by SARAFAN.

Arrival and search statistics use dedicated requests with credentials omitted and browser referrer disabled. An arrival contains only a normalized referrer hostname, a constrained campaign-label candidate, broad page kind, server-validated city and language. The server keeps only an allow-listed channel or an unnamed referral in a daily aggregate. Search text is handled as described in the Privacy notice.

Select the checkbox below to object free of charge. It stops arrival and search requests, removes the dedicated daily statistics identifier and tells the account-state request not to write the browser-day ping; any ping for its last current-day value is removed best-effort. Another open tab reads the same preference before its next request; an already in-flight request there may be removed only by a later state request from a tab that still has the value. The choice is per browser and is remembered only by the non-identifying preference key above. Essential session, city, language, contact-limit and draft storage continues to work.

Consent gate for optional technologies

The active optional technologies are Consented tab-scoped product page counts (Browser tab; server hash until next UTC-day roll-up) in the Analytics category and Consented first-touch registration attribution (7 days) in the Registration attribution category. Both are provided by SARAFAN and use no third party. The production registry is the inventory that makes this control appear. Neither can create its identifier or request before a positive choice; missing, stale, corrupt or unavailable browser storage means refusal. Accept all and Reject all have equal prominence, granular boxes start unchecked, and Cookie settings remains available so consent can be withdrawn just as easily. Withdrawal removes the relevant browser value and live server row. Rejection does not disable sign-in, the catalogue, requests, saved presentation settings or the separate legitimate-interest statistics described above.

Google and Telegram sign-in

Their scripts are not loaded merely because you opened SARAFAN. They are loaded only after you ask to see those sign-in methods. Google or Telegram may then use their own storage under their notices. Email sign-in works without loading either provider.

What we do not use

There is no advertising network, behavioural advertising, Meta Pixel, Google Analytics, session replay or cross-site profiling on SARAFAN. The consented page count and first-touch measurements are first-party, use only controlled dimensions and are not used to target a person. If this changes, the technology must stay off until this notice and the required consent controls are updated.

Your controls

Use Cookie settings to accept or withdraw optional page counts or attribution; withdrawal removes the relevant local identifier and live server row. Use the checkbox below to switch separate legitimate-interest statistics off without signing out or losing settings. You can also remove all SARAFAN cookies and site storage in browser settings; doing so signs you out, forgets your city and language, removes unsaved drafts and optional choices, removes the analytics objection, and may reset anti-abuse counters. Essential storage cannot be disabled while keeping the feature that depends on it.

Who is responsible