Public offer

This is an information translation. The agreement is concluded under the law of the Russian Federation, and the binding text is the Russian one at pominutam.ru/offer. Where the two differ, the Russian text prevails.

Sole proprietor Mikhail Andreevich Nikishin (OGRNIP 324420500016611), hereinafter the “Provider”, publishes this Public Offer for granting access to the Po minutam service (pominutam.ru, hereinafter the “Service”).

Text revision: 2026-10-08. This date is the version of the offer: it is written into the account together with the consent given at sign-up or on the consent screen at the first sign-in, so it is always clear which revision a person accepted. When the text changes, the date changes.

1. General provisions

1.1. This document is an official proposal (a public offer) of the Provider and contains all the essential terms on which the service is supplied.

1.2. Under clause 2 of article 437 of the Civil Code of the Russian Federation, a natural or legal person who accepts the terms below becomes the Customer. Under clause 3 of article 438 of the Civil Code, acceptance of the offer is equivalent to concluding an agreement on the terms set out here.

1.3. Acceptance is either of two acts: signing up for the Service (including the first sign-in by an email link or with Yandex ID) while ticking the box that accepts this Offer and the Privacy Policy, or paying for any of the plans.

1.4. The Provider applies the automated simplified taxation regime (AUSN). VAT is not charged, and no VAT invoice is issued.

2. Definitions

Event — a meeting of the Customer (a meetup, a conference, a webinar, a lesson and the like) broken down in the Service into stages with planned durations.

Board — a page of the Service that shows the running stage of an Event, the time left and the drift from the plan. It opens by a link the Customer hands out.

Organiser (Customer) — the person who created an account, created an Event and entered its programme.

Participant — a person whom the Customer added to an Event (a speaker, a host, a member of the audience) or who opened the Board by a link. Participants need no account.

AI assistance action — the processing of text entered by the Customer by an AI model of a third-party supplier: building the Event programme from text or formatting the Event script. The Customer first sees the result of a build and then applies it to the Event themselves; the result of formatting replaces the script text, and the Customer can restore the previous text right after the replacement.

3. Subject of the agreement

3.1. The Provider grants the Customer access to the Service for preparing and running Events, and the Customer undertakes to pay for that access at the rate set by the plan chosen.

3.2. Every paid plan includes: the Event programme and stage scripts, the host Board and the hall screen, the list of people and preparation checklists, the timing report and its CSV export, and AI assistance actions — as many as clause 4.1 states for the plan.

3.3. The service supplied is access to software. The Provider does not organise, host or moderate the Customer's Events and does not take part in them.

3.4. The number of Participants in a single Event is not limited by the Service under any plan.

4. Plans and prices

4.1. The price of access:

The Unlimited plan is access for a term: the month or the year paid for. The Single meeting plan has no term — it is a right to open one Event that does not expire: it has no shelf life, and the Customer uses it whenever they see fit.

The term of access under the Unlimited plan is set when the access is opened and stored in the account; the Customer sees it on the “Plan and payment” screen in their cabinet. Access opened by the Provider by hand (clause 5.6) with no term is marked on that same cabinet screen as having no end date.

The Service does not limit the number of Events under the Unlimited plan. Under the Single meeting plan the limit is a direct one: the right bought is spent on the first Event opened under it (clause 6.4), and a second Event cannot be opened under it — that takes a new purchase. This does not stand in the way of creating Events and entering or editing their programmes: the right is spent at the moment of opening and not before.

4.2. The AI power plan is announced as forthcoming: access under it is not granted, no price is set for it, and it is not a subject of this agreement. Its contents and price will be published separately, and until that publication the Provider carries no obligation in respect of it.

4.3. AI assistance actions. The number of actions included in a plan is stated in clause 4.1. Under the Unlimited plan it is counted per billing month, which coincides with the month paid for: the first billing month starts at the moment of payment, every billing month ends at the end (23:59:59 Moscow time) of the day of the month on which the term of access ends, and the next one starts at 00:00 Moscow time on the following day — from that moment the number of actions is renewed. Where a month has no such day, the billing month ends on its last day. Extending access before the term ends does not move the boundaries. For access opened by the Provider with no term (clause 5.6) the billing month is the calendar month. The Customer sees the date of the next renewal on the “Plan and payment” screen in their cabinet. Under the Single meeting plan two actions come with each meeting bought, and a new month does not renew them. An action is spent at the moment the model is called, not when its result is applied: the call to the supplier is paid for by the Provider whether or not the Customer likes the answer. A failed action is not spent: if the model did not answer, the answer arrived incomplete, the Service could not read it or the Customer cancelled the script formatting before it finished, the number of actions left does not go down. Running out of actions does not end the rest of the access under the plan and is not a ground for a refund. The Provider is not answerable for what the model returns: the Customer sees the result and decides on their own whether to use it. The text the Customer enters for an AI assistance action is passed to a third-party model supplier; what exactly is passed and on what terms it is processed is set out in the Privacy Policy.

4.4. Prices are stated in roubles of the Russian Federation. The current price list is published on the plans page and is shown before any money is taken.

4.5. A change of prices does not affect access already paid for: neither the paid term of the Unlimited plan nor a Single meeting right that has been bought and not yet spent.

5. Payment

5.1. Payment is made in roubles of the Russian Federation by bank card.

5.2. Payments are accepted through the YooKassa payment service (YooMoney NBCO LLC). The Customer's card details are neither passed to the Provider nor stored by it.

5.3. After payment the Customer receives an electronic cash receipt at the email address held in the account, as required by Federal Law No. 54-FZ of 22 May 2003.

5.4. The Customer's payment obligation is discharged when the funds reach the Provider.

5.5. There is no automatic renewal and no recurring charge. The Unlimited plan is access for a paid period, not a subscription that charges itself: when the period ends, access ends, and it is renewed by a new payment the Customer makes deliberately. The Provider keeps no payment credentials for repeat charges.

5.6. Besides payment on the site, access under the plans may be opened by the Provider by hand upon a request to the support address — including when card payment on the site is unavailable. The terms of this section apply to such access so far as they do not contradict the settlement procedure agreed by the parties.

6. The Meeting Right and when the service counts as supplied

6.1. Under the Single meeting plan the Provider grants the Customer the right to hold one meeting using the functionality of the Service (the “Meeting Right”). The subject of the agreement is the granting of the Meeting Right; the subject of the agreement is not the holding of a particular meeting on a date and at a time agreed between the parties.

6.2. The Meeting Right is granted to the Customer at the moment it is credited to the Customer's personal ledger in the Service cabinet, which happens automatically immediately after the payment arrives. From that moment the Provider's obligation under this plan is performed in full and the service counts as supplied. The crediting is evidenced by the entry in the Customer's cabinet and by the Service's own data; the parties draw up no separate act of acceptance.

6.3. The Meeting Right is perpetual: it has no term and is not extinguished by going unused. The Provider keeps the Service ready to perform on the Customer's demand for as long as the Customer's account exists. Under clause 2 of article 429.4 of the Civil Code of the Russian Federation, payment under this plan is made for the granting of the Meeting Right and is not recalculated according to whether the Customer has made use of that right.

6.4. The Meeting Right counts as used when the Customer opens a meeting in the Service — that is, when the Customer moves the Event into the “open” state and the Board links start working; at that moment the Meeting Right is written off the Customer's personal ledger. Using the Right is not the moment at which the service is supplied and gives rise to no further obligation of the Provider towards the Customer under this plan.

6.5. Unlimited plan: the service is supplied continuously throughout the paid period and counts as supplied when the period ends. The number of Events run within the period does not affect the price.

6.6. No act of acceptance is drawn up. The Service's own records serve as proof: under the Single meeting plan — the entry recording the Meeting Right credited to the personal ledger with its date and time (clause 6.2); under the Unlimited plan — the account's access period. Use of the Meeting Right (clause 6.4) is evidenced by the mark of the first opening of the Event with its date and time and the matching entry in the Event action log. The opening mark is set once and is never removed — including when the Event is later moved back to a draft.

7. Refunds

7.1. The Customer may claim a refund if the Board did not work at the Event for reasons attributable to the Provider.

7.2. A non-working Board, for the purposes of this agreement, means both of the following at once:

• during the announced time of the Event the Board did not open by the links issued, or opened but did not show stages changing, and this happened for all Participants rather than on one device;
• the cause lies with the Provider — the Service being unavailable, an error in the Service, or loss of the data entered.

7.3. The following are not a non-working Board and are no ground for a refund: absence or quality of the connection of the Customer and Participants, their device and browser settings, blocking of the Service address inside the Customer's network, mistakes in the Event programme itself, and the Event having run off its plan.

7.4. A refund request is sent to support@pominutam.ru no later than 10 (ten) calendar days from the date of the Event and states the name and date of the Event, the account email address, and a description of what happened on the Board. After that period the claim is not considered.

7.5. The Provider considers the request within 10 (ten) calendar days and, where the claim is justified, returns the money by the same means by which it was paid.

7.6. Under the Unlimited plan a refund is made in proportion to the number of days the Service was unavailable. That number is established from the Customer's request and the Service's own records: the Provider keeps no separate uptime measurement and does not rely on one. Instead of refunding, the Provider may extend the paid period by the same number of days if the Customer agrees.

7.7. Voluntarily, beyond what the law requires and in addition to the service supplied under clause 6.2, the Provider offers the Customer the option to give up an unused Meeting Right and have the amount paid for it returned. The return is made upon the Customer's application, provided the Meeting Right has not been used in the manner of clause 6.4. A return under this clause is a buy-back by the Provider of a Right it previously granted, and does not mean that the service under clause 6.2 was not supplied or was supplied improperly.

8. Processing of Participants' personal data

8.1. By entering Participants' data into an Event — a name, a short name, a role caption, a photo — the Customer passes the Provider personal data of third parties.

8.2. In respect of that data the Customer is the data controller and the Provider is a person processing personal data on the controller's instruction (part 3 of article 6 of Federal Law No. 152-FZ of 27 July 2006). This section is the Customer's instruction to the Provider to carry out that processing.

8.3. The list of operations: collection (receipt from the Customer), recording, systematisation, accumulation, storage, updating, retrieval, use, blocking, deletion and destruction. Processing is automated.

8.4. Purpose: showing the Board and the hall screen to the Participants of the Event, keeping the Customer's list of people, and producing the timing report.

8.5. Period: for as long as the Event or the Customer's account exists. The retention periods and the deletion procedure are described in the Privacy Policy.

8.6. The Provider undertakes to keep that data confidential, to apply the protection measures required by article 19 of Law No. 152-FZ, and not to process it for its own purposes.

8.7. The Customer undertakes to have a lawful ground for passing Participants' data to the Provider and to inform the Participants about the processing. Consent from Participants is obtained by the Customer; the Provider enters into no relationship with Participants.

8.8. The Customer is informed and accepts that photos in the Service are served by a direct link with no access check, and that the stage script is visible to everyone holding a Board link. Board links are handed out by the Customer, and the decision on what to record about Participants is likewise the Customer's.

9. Rights and obligations

9.1. The Provider undertakes to keep the Service running, to grant the paid access, and to answer the Customer's requests at support@pominutam.ru.

9.2. The Customer undertakes:

9.2.1. To state a valid email address: cash receipts and service letters are sent to it.

9.2.2. Not to place in programmes, stage scripts and notes anything whose distribution is prohibited by the law of the Russian Federation.

9.2.3. To observe the Terms of Use.

9.3. The Provider may limit the rate of requests to the Service and suspend access where actions create excessive load or break the law, having notified the Customer at the account address.

10. Liability

10.1. The Service is provided “as is”. The Provider does not warrant uninterrupted operation and is not answerable for how the Customer's Event went.

10.2. The Participant and host PINs, and the hall screen key, are not a means of protecting information. They guard against wandering in by accident, not against guessing: anyone holding a link or a PIN will see the Board. The Customer takes this into account when deciding what to put into a programme and whom to give links to.

10.3. The Provider's aggregate liability under this agreement, on any claim, is limited to the amount actually paid by the Customer for the access in connection with which the ground for the claim arose.

10.4. The Provider is not answerable for an inability to use the Service caused by failures of the internet connection, equipment or software on the side of the Customer or the Participants.

10.5. The Customer is answerable for the contents of programmes, stage scripts and notes, and for the lawfulness of entering Participants' data.

11. Intellectual property

11.1. The Service and its source code are results of the Provider's intellectual activity, and the exclusive rights to them belong to the Provider. This agreement transfers no rights in them to the Customer beyond the right to use the Service for its purpose within the access paid for.

11.2. Rights to the Event programme, stage scripts and other content entered by the Customer remain with the Customer. The Provider uses them solely to run the Service.

12. The Customer's personal data

12.1. The Customer's personal data is processed in accordance with the Privacy Policy.

12.2. By accepting this Offer the Customer confirms consent to the processing of their personal data on the terms of that Policy.

13. Term and amendment

13.1. The agreement takes effect upon acceptance and runs until the parties have performed their obligations in full.

13.2. The Provider may amend the Offer. Amendments take effect when the new revision is published on the Service's site and do not apply to access paid for before publication. The exception is amendments that only improve the Customer's terms (for example, a larger number of AI assistance actions): they also apply to access paid for before publication.

13.3. The revision in force at the moment of acceptance is fixed by the date stored in the Customer's account (see the top of this document).

14. Disputes

14.1. The parties settle disputes by negotiation. A claim is answered within 10 (ten) business days of receipt.

14.2. Failing agreement, the dispute goes to court under the law of the Russian Federation.

15. Provider's details

Sole proprietor Mikhail Andreevich Nikishin