Update date: May 10, 2026 Version: 1.0
This Cookie Policy describes how moolt.site uses cookies, local identifiers, pixels, SDKs, analytics scripts and other similar technologies on the site, in your personal account, public user pages and related service interfaces.
Cookies and similar identifiers may be personal data if they directly or indirectly identify a user, device, browser, session, account, or behavior on a site. In such cases, their processing is also governed by the moolt.site Privacy Policy.
What are cookies and similar technologies
Cookies are small files or records that a site stores in the user's browser or transfers to the browser for storage and later use. They help the service recognize the session, support account login, save the interface state, ensure security and collect technical statistics.
Similar technologies include, for example, analytics pixels, SDKs, JavaScript tags, server-side events, browser storage, device/browser identifiers, IP address, user agent, URL parameters and technical request logs.
What technologies do we use
| Category | Examples | What is it used for | Obligation | Possible data | Approximate shelf life |
|---|---|---|---|---|---|
| Required cookies | `token`, `user` | Authorization, maintaining a session, access to your personal account, basic operation of the service, account protection | Required for the service to function | Session identifier or authorization token, user data in the `user` cookie, technical characteristics of the session | Usually up to 30 days; in some registration or login scenarios the period may be shorter |
| Safety and technical diagnostics | Server technical logs, error events, Sentry if `NEXT_PUBLIC_SENTRY_DSN` is present in production | Bug detection, incident investigation, abuse protection, product stability | Technical logs may be required; client-side Sentry starts after consent to functional technologies | IP address, user agent, URL, event time, technical error context, user ID or email/username if passed to the error context | According to the monitoring service settings and internal rules for storing logs |
| Internal service analytics | Events of public page views and product actions | Feature Usage Measuring, Product Improvement, Page Statistics | Not always required; depends on specific event and setting | Page URL, viewing time, device type, browser technical parameters, page or account IDs | According to internal analytics storage settings |
| Page owner analytics | Google Analytics, Yandex Metrica, other counters connected by the owner of the public page | Statistics of visits to a public page, visitor behavior, reports for the page owner | Not required for basic operation of moolt.site | Cookies and analytics identifiers, IP address, user agent, browsing pages, events, referral sources | According to the rules of the corresponding provider and the settings of the page owner |
| Maps and geocoder | Mapbox GL, Mapbox Geocoding API | Displaying maps, searching and clarifying addresses, working with geolocation cards | Required only for map and geocoding functions | Search query, coordinates, IP address, user agent, technical parameters of map and device | According to Mapbox rules and browser/provider settings |
| Functional settings | Interface settings, if they are saved in cookies or browser storage | Remembering interface state and user preferences | Not required for login, but can improve the interface | Selected settings, state of interface elements, technical identifiers | Before changing your settings, clearing your browser, or deleting your data |
Required cookies
Required cookies are required for moolt.site to function. Without them, the user will not be able to log into the account correctly, save the session, use the personal account and perform actions that require authorization.
At the current stage, frontend uses, in particular:
| Cookie | Destination | JavaScript accessibility | Deadline | Comment |
|---|---|---|---|---|
| `token` | Storing an authorization token and confirming a user session | `httpOnly`, that is, not intended to be read by client JavaScript | Usually up to 30 days; in some scenarios it can be 1 day or 7 days | Used by server actions to make API requests on behalf of the user |
| `user` | Storing user data required by interface and server actions | `httpOnly`, that is, not intended to be read by client JavaScript | Usually up to 30 days | May contain account information and is therefore considered potentially personal information |
In production, required cookies may additionally have security attributes, such as `Secure` and `SameSite=Lax`, if specified by the appropriate server script.
Analytics and page owner counters
moolt.site allows or may allow owners of public pages to connect external analytics, such as Google Analytics, Yandex Metrica or similar page-owner analytics. These tools may set their own cookies, pixels and identifiers and share data with their respective analytics providers.
If the page owner enables such counters, the processing of the data may depend on the owner's settings, the legal basis and the documents of the relevant provider. A visitor to a public page should be aware that some of the analytics may work in the interests of the owner of a specific page, and not just moolt.site.
Sentry and error monitoring
In production, moolt.site can use Sentry to monitor errors and product stability if `NEXT_PUBLIC_SENTRY_DSN` is configured in the environment, the monitoring package is available in the application and the user has consented to functional technologies.
Sentry can receive technical bug information, URL, user agent, console events, network errors, breadcrumbs, release information, environment information, and user ID, email, or username if such data is passed into the bug context. Performance monitoring and session replay with selective recording of sessions are also possible in the configuration. Such data is used for diagnostics, error correction and improving service reliability.
Mapbox
Maps and geocoding features in moolt.site can use Mapbox. When running a map or searching for an address, the browser can access Mapbox services, including `api.mapbox.com` and `events.mapbox.com`.
Mapbox can receive technical request data, IP address, user agent, map parameters, coordinates, search queries and other data necessary for map display and geocoding. If the user is not using the map or geocoding functionality, these hits may not be processed.
Consent management
moolt.site displays a cookie banner through which the user can accept all optional categories, reject them, or open settings and select categories separately.
The choice is saved in browser storage under the technical key `moolt_cookie_consent_v1`. This record is needed to remember the user's decision and is not used for advertising. Required cookies remain enabled at all times because without them the service will not be able to correctly support login, security, session, and basic account functionality.
Current selection categories:
- mandatory cookies - always enabled;
- analytics - can be used for statistics and product improvement;
- functional cookies and technologies - can be used for error diagnosis, interface stability and monitoring;
- marketing cookies and technologies - can be used for advertising and measurement integrations, if such tools are connected.
If the user has already made a choice and wants to change it, the user can clear the site data in the browser settings. We can also add a separate permanent button to reopen the cookie settings in the service interface.
How a user can restrict cookies
The user can:
- delete cookies and site data in your browser settings;
- prohibit or limit third-party cookies;
- use private browsing mode;
- configure blocking of trackers and scripts in the browser or extensions;
- log out of your moolt.site account to delete authorization cookies, if this is provided for by the current service logic;
- use settings for opting out of personalized analytics from Google, Yandex, Mapbox, Sentry and other relevant providers, if such settings are available from the provider.
Restricting essential cookies may disrupt the service. Restrictions on third-party analytics or mapping technologies may impact statistics, maps, geocoding, and some public pages.
Transfer of data to third parties
Cookies and similar technologies may result in the transfer of data to infrastructure, analytics and technical providers including, if configured appropriately, Google, Yandex, Sentry and Mapbox. Such providers may be located in other jurisdictions and process data according to their own rules and documents.
We strive to use such tools only to the extent necessary for operation, security, diagnostics, analytics and service improvement.
Policy changes
We may update this Cookie Policy if moolt.site functionality, cookies used, analytics, mapping services, monitoring providers, or legal requirements change.
The current version of the document is published in the repository and/or on the corresponding moolt.site page. If changes significantly affect user rights or the way data is processed, we may additionally notify users in a clear manner.