Fair use rules

1. What counts as normal use

The service is built for real queues and bookings: visitors, patients, customers, guests, event attendees. A rush hour, a busy season, a sale or a conference with seven hundred people is ordinary work, not a violation. We look at sustained load over weeks, not at one hectic day.

"Unlimited" in the plans means we set no artificial ceiling on queues and tickets in the normal work of a company. It is not a right to create load that your visitors do not need.

2. What is not allowed

• Artificial activity. Fake tickets, bookings and visitors; scripts and bots that hammer the service with no benefit for a real queue.
• Mass mailings. Messages to visitors are only about their visit: the call, a delay, a reminder, an answer to a question. Advertising and any messages to people who did not take a ticket in your queue are prohibited.
• Circumventing limits. Several accounts of one company to repeat trial periods or stretch limits, handing access to outsiders, attempts to bypass the plan or the protections through the API. The trial period is given once per company: a new account of the same company (with the same email, including another spelling of the same mailbox, or from the same device) does not get it.
• Resale. Offering the service under your own brand, as part of another product or for a fee to third parties without a written agreement with us. Your own name on your own display within the plan is not that.
• Harm to others. Anything that reduces availability, speed or security of the service for other companies.

The list is not exhaustive, but the test is simple: if an action is of no use to the real queue of your visitors, it most likely belongs here.

3. Automatic caps

Caps apply to the whole account, all of its queues together, and reset at midnight. Only what a company sends to visitors itself is counted: the "Message all" broadcast, personal operator messages and notices about what staff do with a ticket: moving it to another service or another queue, editing a booking, a new online meeting link and calling the same ticket again. A personal message or any such notice counts as one message, whichever channels of the ticket it goes to. A broadcast counts per recipient, and its emails also count towards the email cap: bulk emails are sent from our mail domain. Automatic notifications about the first call of a ticket, booking reminders, confirmations and rating requests are not counted, neither in messengers nor by email: they are tied to real tickets. The exceptions are triggered by staff, so they count towards the email cap: a booking confirmation sent to an email address that staff typed into the client's details while making or editing a booking, and the email about calling the same ticket again (the first call is not counted). Otherwise replacing the client in a booking, moving or editing it back and forth or calling a ticket again and again would work like a mailing. PDF report emails to the account's own address are counted separately: up to 20 a day per account.

* Emails to visitors are part of Business Pro and Corporate. The cap of 1,500 emails a day applies to accounts on the previous Business package, paid before 14 September 2026.

• A queue without an account: 100 messages per day, no emails.
• Open API: 120 requests per minute per key, beyond that the answer is 429.
• The "Message all" broadcast: at most 3 times per minute.
• Sign-in links: 3 emails per address per hour.
• Trial period: one per company. It is not given to an account with the same email as an account that has already had the trial, or to an account from the same device if a trial was used on that device in the last 90 days; if this is a mistake, write to support. The exception for email: if the account that has already had the trial never confirmed its email, and the new account confirms it by signing in with Google or an emailed link, the trial is given and we review the match ourselves. This way an account someone else opened with your address cannot take your trial away.

4. What happens when a cap is reached

• At 80% of the daily cap the account gets a warning: how much has been sent and how much is left.
• At the cap, new messages and emails do not go out until midnight. The operator sees the reason right in the response, and we get a signal and look at what is going on.
• If the load looks genuine, we write first and offer a way out: raise the cap, move to a suitable plan or agree individual terms. There is a reasonable time for that.
• When stability, security or the rights of other people are at risk, we may limit features, slow processing down or suspend access without notice. Deliberate abuse is treated the same way.

5. Large venues

A branch network, a university, a stadium, a public office with thousands of visitors a day: write to us before launch. The Corporate plan comes with its own caps, a contract and invoicing. support@minutka.app

6. Changes

The rules change together with the service. We announce significant changes in the dashboard. If they conflict with the offer, the offer prevails.