Last updated: 1 August 2026
This Cookie Policy explains how Ruletka ("we", "us") uses cookies and similar technologies on ruletka.sex (the "Service"). It sits alongside our Privacy Policy, which describes how we process personal data more broadly and lists your rights under the EU General Data Protection Regulation (GDPR). If you are in the EEA, the UK, or your national law applies (for example Nigeria's NDPR or South Africa's POPIA), the choices described here are available to you.
This is a working draft prepared for legal review. It is not legal advice and makes no claim of completeness or certification.
What cookies and similar technologies are
A cookie is a small text file a website asks your browser to store. "Similar technologies" include browser localStorage and the session-replay/JavaScript tags described below, which do not always use cookies but perform comparable functions. We group everything we use into two categories:
- Strictly necessary — required for the Service to work (keeping you signed in). These run without your consent because you cannot use the Service without them.
- Analytics — help us understand how the Service is used. These are off by default and load only after you opt in through the consent banner.
We do not set advertising or cross-site tracking cookies of our own. Note that our analytics provider (Yandex, see below) is itself a third party that controls its own cookies and may use the data it receives for its own purposes; if you accept analytics, review Yandex's own policies.
Our consent model — analytics is off until you accept
When you first visit, a banner appears at the bottom of the page with Accept and Decline options and a link to this policy. Until you make a choice:
- the strictly-necessary authentication cookie still runs (it is exempt from consent);
- no analytics is loaded — the Yandex.Metrika script, including its session recorder and its tracking pixel, does not run and sets no cookies.
Your choice is stored in your browser's localStorage under the key cookie-consent (value accepted or rejected) so we do not ask again on every visit. This is a technical preference stored on your device, not a tracking cookie.
- If you choose Decline, analytics never loads.
- If you choose Accept, the analytics tag described below loads and begins setting its own cookies.
We honour the default-off state in code: the analytics component returns nothing and injects no script unless your stored choice is exactly accepted. The stored choice lives only in the browser you used, so it does not follow you across devices and is lost if you clear site data.
Cookies and similar technologies we use
| Name / key | Provider | Purpose | Type | Lifetime | Consent required? |
|---|---|---|---|---|---|
rt | Ruletka (first-party) | Refresh-token cookie that keeps you signed in and lets us issue new access tokens without re-login. httpOnly, Secure in production, SameSite=None in production (Lax in development), scoped to the /api/auth path. The value is an opaque random token; only its hash is stored on our servers. | Strictly necessary | ~30 days (from JWT_REFRESH_TTL, default 2,592,000 s); cleared when you log out | No — always on |
cookie-consent | Ruletka (first-party, localStorage) | Remembers whether you accepted or declined analytics so the banner is not shown again. | Strictly necessary | Until you clear your browser storage | No — always on |
_ym_uid, _ym_d | Yandex (Yandex.Metrika, counter 110772171) | Distinguish visitors and record first-visit date for usage statistics. | Analytics | Yandex-set, typically ~1 year | Yes — only after you Accept |
_ym_isad | Yandex (Yandex.Metrika) | Ad-blocker detection used by Metrika. | Analytics | Yandex-set, short-lived (typically ~1 hour) | Yes — only after you Accept |
_ym_visorc | Yandex (Yandex.Metrika Webvisor) | Enables the Webvisor session recorder, which reconstructs your session (page DOM and interactions) for analytics. | Analytics | Yandex-set, session | Yes — only after you Accept |
Cookie names and lifetimes in the analytics rows are set and controlled by Yandex, not by us, and Yandex may add or rename cookies over time. Treat the lifetimes as indicative.
About the analytics recorder
When you accept, our Yandex.Metrika tag loads with Webvisor (session replay), clickmap, link tracking, e-commerce (dataLayer) and accurate-bounce tracking enabled. Session replay can capture how you move through pages, including on-screen content. We reduce what the recorder can see on the most sensitive screens:
- chat: the conversation area is marked so the recorder does not capture message contents, and the message input is marked so keystrokes are not recorded;
- payouts: the payout wallet-address field is masked from the recorder and its keystrokes are not recorded.
Other parts of the interface (profiles, wallet balances, navigation) are still recorded once you have accepted. The tag and its data are served by Yandex (mc.yandex.ru), which involves a transfer of data to Russia. Russia is not covered by an EU adequacy decision; see the "International transfers" section of the Privacy Policy for how this is addressed. Because analytics loads only on your explicit opt-in, that consent is the basis for this processing (GDPR Art. 6(1)(a)).
A note on third-party components
Some third-party components embedded in the Service — for example Telegram's Mini App / widget SDK — may set their own cookies or storage on their domains and see your IP and browser when their features load. We do not control those cookies. Where such a component causes a transfer of data, it is described in the Privacy Policy.
How to change or withdraw your consent
- In the Service: clear your browser's site data for ruletka.sex (this removes the stored
cookie-consentchoice), then reload — the banner reappears and you can choose again. Choosing Decline stops analytics from loading on future visits. (There is currently no in-app button to reopen the banner; see the note below.) - In your browser: you can block or delete cookies at any time through your browser settings. Blocking the strictly-necessary
rtcookie will sign you out and prevent you from using the Service. Deleting the_ym_*cookies removes existing Yandex identifiers. - Withdrawing is as easy as giving consent (GDPR Art. 7(3)). Withdrawal does not affect analytics collected while your consent was active, but stops further analytics collection going forward.
Changes to this policy
We may update this Cookie Policy as the Service or our providers change. The "Last updated" date at the top reflects the latest version.
Contact
Questions about cookies or your data: admin@ruletka.sex. Our EU representative (Art. 27), where designated, is —; our Data Protection Officer, where designated, is —. Postal address: —. You also have the right to lodge a complaint with your local data protection supervisory authority.