Cookies policy

Two levels of statistics

Detailed activity and session analytics run only with your analytics consent. Separately, we aggregate requests to public pages from existing server logs. These counters create no cookies or visitor identifiers; the summary contains no IP addresses, individual histories or full referring URLs. They count requests, not unique people.

The underlying technical logs may contain IP addresses and other technical data; their processing is described in the Privacy Policy.

1. What are cookies

Cookies and similar technologies are small files and local browser records that help the site remember settings, keep sessions, and understand how users interact with the service.

2. Technologies used on the site

• technical cookies for authorization and localStorage for user settings and interface state;
• functional data for saving user settings and preferences;
• analytics identifiers to assess visits, traffic sources, and on-page behavior.
• marketing and referral identifiers when the site runs ad campaigns, remarketing, or affiliate links;
• server logs, pixels, SDKs, and similar technologies that help understand service performance and areas for improvement.

Aggregate statistics without transmitting identifiers

Regardless of analytics cookie choices, the site maintains hourly counters of public page openings and cookie decisions. These counters do not retain IP addresses, visitor identifiers, accounts, URL parameters or browsing histories. Pages with user interaction are counted separately as a signal of a probable human, not proof of identity. To count visits, the browser stores a random temporary identifier, last activity time and interaction flag only in the current tab’s sessionStorage. These values are never sent to the server; the server receives only events for hourly counters. After 30 minutes of inactivity, the next page opening or action starts a new visit. Refreshes and navigation continue the visit; separate tabs are normally counted separately. When duplicating a tab or opening one from another tab, the browser may copy sessionStorage and continue the existing visit. If sessionStorage is unavailable, page memory is used, so refreshing may start a new visit. Visits with interaction are counted separately and must not be added to total visits. Repeated openings and decisions may be counted again; unique people are not calculated. Data is retained for up to 35 days. Ordinary technical server logs are processed separately for security and diagnostics.

3. Why they are needed

• for account sign-in and proper account area operation;
• for preserving selected learning and interface settings;
• for measuring ad, content, and signup funnel effectiveness;
• for abuse prevention and technical diagnostics.
• to remember user consents, selected language, form states, and other interface elements;
• to build aggregated statistics, estimate load, and improve site performance.

4. Cookie categories by retention period

• session cookies deleted after closing the browser;
• persistent cookies stored for a fixed period to recognize the device on return visits;
• local storage entries kept until deleted by the user, browser, or website.

4. Managing cookies

Users can restrict cookies in browser settings. In that case, some site features, including authorization and personal settings, may work incorrectly.

Users may also delete saved cookies, use private mode, restrict third-party cookies, and opt out of specific analytics or advertising tools where such options are available in browser settings or from the provider.

5. Relation to personal data

If cookies and related identifiers can directly or indirectly identify a user, they are processed according to the Personal Data Policy and other site documents.

A combination of technical identifiers, activity data, device data, and session data may be treated as personal data when it allows direct or indirect user identification.

6. Third-party cookies

The site may use technologies of external providers, including analytics, advertising, authorization, bot-protection, and content delivery services. Such providers may use their own cookies and identifiers under their own data policies.

7. Changes to this cookies policy

The operator may update this policy when technologies, analytics tools, legal requirements, or website logic change. The updated version applies from publication unless stated otherwise.

8. Contacts

For questions about cookies and analytics: info@vastny.com.