Cookies

This is an information translation. The binding text is the Russian one at pominutam.ru/cookie; where the two differ, the Russian text prevails.

Text revision: 2026-10-08.

Cookies are short records a site stores in the browser. Below is every cookie “Po minutam” sets, and what happens if you forbid them. The list describes the behaviour of the running code, not intentions.

What the service sets itself

File	What for	Lifetime	Without it
`pm.session_token`	The organiser's sign-in to the cabinet	30 days	You cannot sign in to the cabinet
`pm.state`	Sign-in with Yandex ID: ties Yandex's answer to the sign-in started on the site. Set only when a person chooses to sign in with Yandex ID	5 minutes	Sign-in with Yandex ID cannot finish
`pm_board_<event id>`	The board sign-in: participation and role	30 days	The PIN has to be typed on every visit
`pm_lang`	The language of the cabinet, the board and the sign-in screens — the one chosen in the profile or named in the sign-in address	One year	The cabinet, the board and the sign-in screens open in the browser's language
`pm_analytics`	A mark that the visit-counter notice has been read (“OK”), or the decision about the counter taken on this page	One year	The notice appears again

The first three are technical: without them signing in does not work at all, and they cannot be declined while using the cabinet or the board. The other two hold a choice and say nothing about the person who made it; neither of them is analytics — pm_lang exists so that a page opens in the right language.

The public pages neither set nor read any language file: there the language is named by the address itself — pominutam.ru/pricing is Russian, pominutam.ru/en/pricing is English, and the switch in the header simply takes you to the neighbouring address.

The service sets no advertising cookies of its own, plugs in no ad network and hands visitor data to no one except the Yandex.Metrica counter named below. The promise stops there, and here is why: Yandex runs an ad network of its own, and what it does with its own files and the statistics it has gathered is its decision, not the service's. What exactly goes to Yandex is listed in the Privacy Policy; Yandex's own rules are behind the link at the end of the next section.

The Yandex.Metrica counter sets files of its own too — the list is below, in a table of its own.

The visit counter

The public pages of the site — the home page, pricing, help and the legal documents — run the Yandex.Metrica visit counter (YANDEX LLC). It shows anonymised statistics: how many people came, which pages they opened, at which step they left.

On pominutam.ru the counter runs from the first visit, and a notice at the bottom of the page says so. It has a single button, “OK”: it removes the notice and changes nothing else.

Three conditions, and the code enforces all of them:

A refusal is respected. After a refusal — with the “Visit counter” block on this page — the counter's code is not on the pages at all, not “loaded but quiet”, and none of its new cookies appear in the browser.
Neither the cabinet nor the board carries the counter. It runs on the public pages only.
Outside the .ru zone — only with consent. If the service opens at such an address, the banner there asks, and the counter is loaded only after “Accept”; until then the counter's code is not on the page.

Webvisor (the recording of mouse movement and typing), the click map and the tracking of clicks on outbound links are switched off explicitly: the service collects attendance, not behaviour.

Yandex privacy policy: https://yandex.com/legal/confidential/

What the counter sets

These files are set by Yandex.Metrica rather than by the service, and only while the counter is loaded. Their purpose and lifetimes are Yandex's: the service can leave the counter out, but cannot change its files.

For the same reason the table below is a list as of the revision date, not a promise: the set of the counter's files is Yandex's to decide, and it may change without a single edit in the service. The current list is in the Metrica documentation: https://yandex.com/support/metrica/general/cookie-usage.html

File	Where	What for	Lifetime
`_ym_uid`	`pominutam.ru`	An anonymised browser number: telling a repeat visit from a new one	One year
`_ym_d`	`pominutam.ru`	The date of the first visit	One year
`_ym_isad`	`pominutam.ru`	Whether the visitor runs an ad blocker	2 days
`bh`	`.yandex.ru`, third-party	Browser and device details the counter collects itself	13 months

After a refusal none of these files is set anew: the counter's code is not on the page at all.

A refusal takes effect from the very next render of the page: the counter's code does not get into it and no new files appear. Two things it cannot do, and promising them would be untrue: it does not delete the files the counter has already set (that is done with the browser's own tools, see below), and a script that managed to start in an open tab before the refusal is played out by that tab — no one can unload running page code from a browser. Reloading the page closes that remainder too.

How to decline

On this page — the “Visit counter” block under the text: it shows the current decision and changes it both ways, including after the banner is gone.
In the banner — where the site asks for consent (addresses outside the .ru zone), press “Necessary only”. The decision is stored in pm_analytics and the counter is not loaded.
In the browser — delete or forbid cookies in its settings: Google Chrome, Mozilla Firefox, Safari, Yandex Browser.
From Metrica specifically — with the official opt-out add-on.

Declining analytics does not affect the service: events are created, boards open, reports are assembled. Forbidding technical cookies in the browser closes the way into the cabinet and the board — that is how signing in is built, not a restriction.

Where the data is described

What exactly the service stores, what for and for how long is in the Privacy Policy. The terms of access are in the offer.

Questions: support@pominutam.ru