Cookie Policy
How cookies and similar technologies are used on RALMIX.
Effective date: September 25, 2026 · Version 2.0-20260925
Published and last updated: September 25, 2026. This expanded edition clarifies service scope, privacy, safeguarding, complaints and applicable legal rights. Publication is not your acceptance and does not retrospectively change an existing agreement. Material contractual changes apply to an existing relationship only after the required notice and valid agreement; mandatory legal rights remain unaffected.
Previous published edition. Privacy notices explain actual processing and are not requests for blanket consent. Payment and DPA frameworks apply only as described in those documents.
Table of contents
- 1. Scope and operator
- 2. Necessary and preference storage
- 3. Yandex Metrika and the scope of the controls
- 4. What your choices mean
- 5. Third-party resources
- 6. Browser controls and limitations
- 7. Children, updates and questions
1. Scope and operator
This policy concerns cookies, browser storage, analytics tags and similar website technologies used by RALMIX LLC. The Privacy Policy identifies the operator, purposes, recipients and privacy rights. A cookie stores information on a device; local storage can persist browser settings; a tag can make a network request even without storing a cookie. Refusing cookies does not necessarily prevent every external request.
2. Necessary and preference storage
Authentication/session cookies and security values support sign-in and requests associated with an Account. Browser storage may remember a selected interface language or an unfinished entry. What is necessary depends on the function requested; it is not enough to label all tools necessary for commercial convenience.
The existing privacy-choice component uses the first-party preference ralmix_privacy_v1, with a 180-day choice period in its published configuration. This preference records a browser choice, not the User's acceptance of every legal document, proof of age or verified parental authority. Different browsers/devices can require separate choices. Clearing storage may remove saved preferences and require sign-in again.
3. Yandex Metrika and the scope of the controls
RALMIX pages include Yandex Metrika counter 110195024 to measure visits and interactions. Depending on configuration, the service can receive page/referrer information, browser and device/network data, clicks and navigation events, and use identifiers such as _ym_uid, _ym_d and _ym_isad. Their actual presence and lifetime depend on provider and browser behaviour. Provider information: https://yandex.com/legal/metrica_termsofuse/.
The Legal Center uses the existing privacy-choice component: Yandex Metrika is loaded only after a valid “Allow analytics” choice. “Necessary only” does not load it. Session replay is disabled in the Legal Center, and its no-JavaScript fallback does not load an analytics image. The preference is shared with pages that integrate the same component. These controls are not a claim that every other page or third-party service has been verified to honour that preference. If another page loads optional analytics despite refusal, report its URL to support; that behaviour requires correction and this policy is not consent to it.
Interaction/session replay concerns website activity and must not be confused with a recording of an online Lesson. Sensitive fields, authenticated communications and children's activities require specific protection; a general analytics preference is not permission for unrestricted capture of them.
4. What your choices mean
Where the consent component is present, choose “Necessary only” to decline optional analytics and use “Cookie settings” to reconsider. A clear affirmative choice is required for consent-dependent tools. Continuing to browse, closing a banner, reading this policy or accepting contractual Terms is not that choice. Refusing optional analytics must not itself prevent access to an otherwise available essential service.
Use “Cookie settings” in the Legal Center footer to withdraw an analytics choice. The existing component clears accessible first-party analytics cookies and reloads a page where analytics was started, so that it does not restart without permission. It cannot delete provider-side records or cookies inaccessible to that page. Browser settings can clear or block additional storage. The controls have the scope described in section 3; contact support if your choice is not respected.
5. Third-party resources
Google-hosted fonts, Google sign-in and external services you open may receive technical requests. Embedded resources should be assessed separately from links that load only after you follow them. The relevant provider has its own privacy information; RALMIX remains responsible for its own decision to integrate a service and any required prior choice.
No active payment-provider cookie catalogue is represented here because card checkout is not currently available. This policy does not announce advertising pixels, fingerprinting, cross-site behavioural advertising or a future payment integration as existing features.
6. Browser controls and limitations
You can inspect site data, delete cookies/storage and restrict third-party cookies using your browser settings. Private browsing may reduce persistence without preventing service providers from receiving a request. A browser's “Do Not Track” signal is not the same as a consent setting; no unsupported signal-handling capability is promised. Blocking essential cookies can interfere with authentication or security.
Where laws require prior consent for non-essential device access, provider loading must follow that choice. Where another rule applies, RALMIX must still provide the required information and controls. Withdrawal must be as straightforward as giving the permission, within the requirements of applicable law.
7. Children, updates and questions
Optional tracking involving children requires the applicable age-appropriate permission and safeguards. A child's click must not be treated as adequate adult authorisation merely because the banner accepted it. See the Child Privacy Notice.
Material changes to purposes or providers require updated information and renewed choice where necessary. Technical cookie names may change, but that does not authorise undisclosed new purposes. Contact ralmix.top@gmail.com or https://ralmix.top/contact/ for cookie and privacy questions; include the page and browser, but not passwords or sensitive form contents.

