Back

Legal Document

Cookie Policy

Effective date: 5 August 2026

This Cookie Policy explains how Sinlege uses cookies and similar client-side technologies on sinlege.com and related customer systems. It should be read together with the Privacy Policy and the Terms of Service.

Service provider: Krzysztof Mańczak, Gumna 2a, 64-420 Kwilcz, Poland. Contact: [email protected], +48 720 370 960.

1. What Are Cookies

Cookies are small text files stored on your device when you visit a website. For the purposes of this Policy, references to "cookies" also include similar client-side storage technologies that the Service may use for the same functional purposes - in particular localStorage and sessionStorage - and, where relevant, pixels or similar identifiers used together with cookies by payment providers. This Policy uses "cookies" to cover those technologies where the context so requires, while remaining technically accurate about what is stored and where.

2. Why We Use Cookies

  1. To keep you logged in and secure your session after authentication (strictly necessary session cookies).
  2. To remember interface preferences (for example display language or theme) where the Service stores such choices locally in a cookie or similar storage.
  3. To remember optional site easter-egg unlocks in your browser (first-party preference cookie) and, when you are logged in, to allow related Quests to verify completion, as described in the Privacy Policy.
  4. To operate payments loaded through Stripe (card, BLIK, wallet top-ups including Payment Links), which may set or read its own cookies or similar identifiers under Stripe's policies.
  5. To operate first-party security verification via the SinlegePass captcha widget, which does not load third-party captcha scripts and does not set third-party cookies.
  6. To maintain basic reliability and security of the Service (for example correlating requests with an authenticated session).

3. Categories of Cookies We Use

Category Purpose Typical lifetime Legal basis
Strictly necessary Login and session security; core Service operation Session cookies expire when the browser session ends. Persistent session cookies last as a rule up to 90 days (unless ended earlier), matching the Account session period described in the Terms of Service No consent required under Polish electronic communications law where strictly necessary for a service requested by you. Where personal data are processed: Article 6(1)(b) and/or 6(1)(f) GDPR
Preferences Language/UI choices; optional easter-egg state (_ee) Typically up to about one year (e.g. language preference or _ee), unless cleared earlier Where consent is required under applicable electronic communications law for non-essential storage, consent will be obtained before setting. Where personal data arise (e.g. Quest sync): see the Privacy Policy; Article 6(1)(b) and/or 6(1)(f) GDPR as applicable
Third-party (payments) Stripe payment components at checkout / Payment Links Determined by Stripe Governed by Stripe's policies; Sinlege loads Stripe only where needed for payment

Strictly necessary

Essential for the Service to function, including session cookies tied to your login. Storing or accessing information on your terminal equipment for these cookies does not require consent under the Polish Electronic Communications Law (Prawo komunikacji elektronicznej) where it is strictly necessary to provide a service requested by you. Where such cookies involve personal data, processing is based on performance of a contract (Article 6(1)(b) GDPR) and/or Sinlege's legitimate interest in operating a secure Service (Article 6(1)(f) GDPR), without treating consent as the basis for strictly necessary cookies.

Preferences

Used to remember choices you make in the interface (such as language) and optional first-party easter-egg state. The easter-egg cookie is typically named _ee, stores a short list of unlock keys (not advertising identifiers), and may remain for up to about one year unless cleared. Where such data constitutes personal data after account sync for Quests, processing follows the Privacy Policy (Quests section). Where consent is required under applicable electronic communications law before setting non-essential cookies or similar storage, Sinlege will obtain such consent before those cookies are set.

Third-party (payments)

When you use card payments, BLIK, or wallet top-ups (including Payment Links), Stripe may place or read cookies or similar identifiers according to Stripe's own policies. Sinlege does not control Stripe's cookies. Security verification on this Service is handled by Sinlege's own first-party SinlegePass captcha widget, which does not set third-party cookies and does not load third-party captcha providers. It may use a first-party tutorial cookie and sessionStorage nonces as described above. Challenge-related data processed in connection with SinlegePass (including any transient association of an IP address with a challenge) is retained only for the duration described in the Privacy Policy (interactive puzzle about 5 minutes; response token / IP association as a rule up to 10 minutes).

Sinlege does not currently use Google Analytics, Google Ads, Meta Pixel, Microsoft Clarity, Hotjar, or similar analytics or advertising technologies as part of the standard operation of the Service, and does not use its own advertising or remarketing cookies for that purpose. Sinlege does not sell personal data collected through cookies or similar technologies.

Sinlege does not currently display a separate cookie consent banner for advertising/analytics cookies because those technologies are not used. First-party preference and functional cookies listed in this Policy (including language, easter-egg state, referral attribution, captcha tutorial state, and short-lived session helpers) may be set when you use the related feature. If Sinlege introduces additional non-essential cookies that require consent under the Polish Electronic Communications Law, it will obtain such consent before those cookies are set.

Additional first-party cookies or similar storage that may be used include: session shard cookies (__Host-sl_c0–__Host-sl_c9 / sl_c0–sl_c9) and, where applicable, an express-session cookie named sinlege.sid (typically up to about 90 days); CSRF protection (__Host-sl_csrf / sl_csrf, same lifetime as the session); language preference sinlege_lang (typically up to about one year); referral attribution sinlege_ref (typically up to about 180 days); SinlegePass tutorial sp_captcha_tutorial (typically up to about one year); optional user-assistant history cookies under the prefix sinlege_ai_hist_* (typically up to about 7 days); Discord OAuth state cookies sinlege_discord_oauth_state and sinlege_discord_oauth_flow (about 10 minutes); QR login bind cookie qr_bind (path-scoped, short-lived); and admin gate cookie agate where that feature is used (hours). localStorage / sessionStorage may store UI state (for example promo dismissal, assistant consent, post-login redirect, or captcha page nonces). No data stored in localStorage or sessionStorage is used for advertising, behavioural profiling, or cross-site tracking.

4. Managing Cookies

  1. You can delete or block cookies, and clear localStorage / sessionStorage, through your browser settings.
  2. Blocking strictly necessary cookies may prevent login, payments, or other core features from working.
  3. Clearing preference cookies (including _ee) or related local storage may reset language, theme, or easter-egg unlocks in that browser until you set them again.
  4. For third-party cookies used in connection with payments, refer also to your browser settings and to Stripe's help or privacy documentation.

5. Personal Data and Your Rights

Where cookies or similar technologies involve personal data, the rules in our Privacy Policy apply, including your rights under the GDPR, the identity and contact details of the controller, retention periods, and how to lodge a complaint with the President of the Personal Data Protection Office (UODO). This Cookie Policy does not limit those rights.

6. Changes

We may update this Cookie Policy when our practices or the law change. The effective date at the top will be revised; material changes may also be communicated through the Service where appropriate.