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.marketplace-draft:* in localStorage: unsaved item text, price, category, condition and location, the current step and draft/account binding IDs in this browser for up to 24 hours after a write. Contacts and photos are not stored in this value. It stops restoring after expiry and is removed at the next read, after successful publication, when discarded, on sign-out or account erasure. Server drafts, contacts and uploaded files have the separate retention in the Privacy notice.
• 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_claim_intent: an HttpOnly, Secure production cookie created only after a moderator-issued ownership invitation is opened. It contains a separately random continuation, never the raw invitation; the server keeps only its hash. It lasts 30 minutes, remains after a successful transfer until that original expiry so a lost response can be recovered only by the recorded winner, and is cleared on sign-out, revoke-all or an erasure request.
• 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 independently versioned optional-technology notice, the exact disclosed-inventory revision, decision time and one boolean per category; this is separate from this document’s display revision. Adding an essential-storage disclosure does not grant or reset optional choices; 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 fixed credentialless product/article-count endpoints and removed when the tab closes or consent is withdrawn. Each published article view also receives a separate UUID held only in memory until navigation or reload; it is not browser storage. The server stores only separately UTC-day-salted hashes until roll-up.
• sarafan.attribution in localStorage: a separate random UUID and its expiry, created only after Registration source 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.request-draft:* in localStorage: the request you are writing, kept in this browser for 24 hours and removed after publication or when you clear it. It is sent to SARAFAN only when you publish. Open the sign-in email in the same browser to restore it.
• sarafan.favourite-intent:* in localStorage: a pending save-to-favourites action for up to 15 minutes, used to continue after sign-in. It is removed on return or cancellation; expired records are removed at the next save attempt.
• 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 and article reading 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 source 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. The initial panel has one Accept button for all active optional categories. Cookie settings in the footer is available before and after a decision. In settings, Accept all and Reject all have equal prominence, category switches start off, and the choice can be changed or withdrawn. 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.

Cloudflare Turnstile security check

When a human check is required, your browser connects to Cloudflare Turnstile and our server validates its single-use token with Cloudflare, including the client IP. The raw token remains in memory for the request. Our private security journal keeps only its keyed hash to prevent reuse; daily cleanup removes records older than 24 hours, within 48 hours including the schedule. This journal is excluded from backups. This is a security check, not advertising analytics. SARAFAN does not enable Turnstile pre-clearance cookies.

Google and Telegram sign-in

Their scripts are not loaded merely because you opened SARAFAN. On the login page, only pressing a provider button after accepting the Terms loads that provider’s script and connects your browser to it. Accepting the Terms alone does not load either provider. When linking a sign-in method in your account, only the provider you request is loaded. Google or Telegram may then use their own storage under their notices. Email sign-in does not require a Google or Telegram account.

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