Public Offer for Provision of Zapnoty Services

This English translation is provided for informational purposes only. In case of any discrepancy or conflict between this English version and the Russian version published at zapnoty.ru/offer, the Russian version shall prevail.

1.1. Service (Zapnoty) — the Provider's software and hardware platform available at the domains zapnoty.ru, zapnoty.com, app.zapnoty.ru, app.zapnoty.com and related subdomains, providing an application programming interface (API), a personal dashboard, and messenger bots for sending notifications, one-time codes, processing form submissions, broadcasts, and exchanging messages with the Customer's End Users.

1.2. Provider — Individual Entrepreneur Antonov Aleksandr Viktorovich, INN 262517638904, OGRNIP 312265133100116. Full details are provided in Section 21.

1.3. Customer — an individual, individual entrepreneur, or legal entity that has entered into this agreement with the Provider by accepting this offer.

1.4. Dashboard — the restricted area of the Service accessible to the Customer after completing the authorization procedure.

1.5. Plan — the set of service parameters (monthly credit allowance, resource limits, data retention period, support level) published on the /pricing page of the Service.

1.6. Credit — the internal unit of account of the Service. The cost of individual operations in credits is published on the /pricing page (for example, a Telegram or Max message — 1 credit, sending an email — 2 credits).

1.7. Credit Pack — a fixed set of credits purchased by the Customer on a one-off basis.

1.8. Subscription — prepayment for the selected Plan for a calendar Subscription Period.

1.9. Subscription Period (paid period) — a calendar month, quarter, or year during which the Customer is granted access to the selected Plan.

1.10. Auto-renewal — automatic charging of the cost of the next Subscription Period to the Customer's stored bank card via the Acquirer without further action by the Customer.

1.11. Credit Balance — the recorded value reflecting the remaining credits available to the Customer. It consists of two parts: plan credits (granted under the Plan, expire at the end of the monthly cycle) and purchased credits (granted upon purchase of Credit Packs, do not expire within 12 months from the date of crediting).

1.12. Grace Period — a short-term period during which the Customer continues to use paid operations with a negative Credit Balance. Parameters — see Section 10.

1.13. API — the Service's application programming interface, described in the technical documentation at /docs and /api-reference.

1.14. Customer's End User — an individual to whom the Customer sends messages, notifications, or confirmation codes through the Service, or from whom the Customer receives submissions through the Service's forms.

1.15. Acquirer — Joint-Stock Company TBank (INN 7710140679), providing the Provider with Internet acquiring services and acting as the fiscal data operator for the Customer's payments to the Service.

1.16. Agreement — this public offer accepted by the Customer in accordance with Section 3, together with the plans and documentation published on the Service's website.

2.1. The Provider undertakes to grant the Customer access to the Service on a SaaS (software as a service) model, and the Customer undertakes to accept and pay for the services in accordance with the terms and conditions set out in this offer.

2.2. The Service comprises: the application programming interface (API), the Dashboard, messenger bots (Telegram, Max), the form submissions processing system, the broadcast system, notification routing, delivery logs, and other functionality described in the Service's technical documentation.

2.3. Services are provided remotely via the information and telecommunications network "Internet". No paper documents or physical presence of the parties are required.

2.4. The Service is provided on an "as is" basis, without warranties of uninterrupted operation or fitness for the Customer's particular purpose, except as expressly provided in this offer and applicable law.

3.1. Full and unconditional acceptance of the offer (conclusion of the agreement) is constituted by the Customer's performance of any of the following implied actions:

3.1.1. completion of registration in the Service via an OAuth provider (Yandex, VKontakte) or via email confirmation ("magic link");

3.1.2. clicking the payment button on the checkout page for a Subscription or Credit Pack purchase;

3.1.3. actual use of any functionality of the API or the Dashboard.

3.2. By performing any of the actions listed in clause 3.1, the Customer confirms that they have read this offer, the Personal Data Processing Policy, and the Cookies Notice, understand their content, and accept them in full without reservation.

3.3. The agreement is deemed concluded from the moment of acceptance. The written form is satisfied through the exchange of electronic documents in accordance with Article 434 of the Civil Code of the Russian Federation.

4.1. The current pricing schedule is published on the /pricing page of the Service. The schedule includes: monthly credit allowance, resource limits (number of projects, team composition, number of forms, webhooks, delivery log retention), support level, and the price in roubles per month, quarter, and year.

4.2. A credit is the internal unit of account of the Service. The cost of operations in credits is published on the /pricing page. Changes to the operations price list — see Section 18.

4.3. The Customer's Credit Balance is tracked separately in two buckets:

4.3.1. plan credits — automatically credited at the start of each monthly cycle in the amount specified by the Plan and expire at the end of that cycle (unused balance does not carry over to the next month);

4.3.2. purchased credits — credited upon purchase of Credit Packs and available for use within 12 (twelve) months from the date of crediting.

4.4. When a paid operation is performed, credits are first deducted from plan credits and then from purchased credits.

4.5. Credit Packs constitute a one-off purchase without recurring charges or auto-renewal.

4.6. The Enterprise plan is concluded under a separate agreement.

5.1. The Subscription is paid in advance for the selected Period (month, quarter, or year) in a single, full payment. Discounts for quarterly and annual prepayment are published on the /pricing page.

5.2. Payment is made in roubles of the Russian Federation via Internet acquiring through the Acquirer. Other payment methods may be available by agreement with the Provider for Enterprise plans.

5.3. Upon the first Subscription payment, the Customer's bank card is stored by the Acquirer as a token enabling subsequent recurring charges. The Provider does not receive or store the card number itself; only masked payment details (last four digits, expiry date, payment system) are available in the Dashboard.

5.4. Auto-renewal is enabled by default after the first successful Subscription payment. One calendar day before the end of the Subscription Period, the Acquirer, on behalf of the Provider, automatically charges the Customer's stored card for the next Subscription Period in accordance with the current Plan.

5.5. A notice of the upcoming auto-charge is sent to the Customer in advance — 72 hours before the charge date — by email and/or to the linked messenger. The notice contains the amount and date of the upcoming charge, as well as the procedure for cancelling Auto-renewal.

5.6. The Customer may at any time disable Auto-renewal in the Dashboard under "Subscription". Disabling Auto-renewal stops subsequent recurring charges; access to the Service under the paid Plan is retained until the end of the current Subscription Period.

5.7. If a recurring charge fails (Acquirer decline, insufficient funds, expired card, etc.), the Subscription switches to access based on the remaining Credit Balance until the purchased credits are exhausted, taking into account the grace period (Section 10), after which the Plan is automatically switched to the Free plan.

6.1. The Customer may at any time change the Plan or Subscription Period in the Dashboard. The cost of the transition is calculated using a single formula: "full price of the new Period plus bonus days".

6.2. The Customer pays the full price of the new Subscription Period at the new Plan in a single payment. The unused remainder of the paid prior Period is recalculated into a number of additional calendar days (bonus days) that are added to the new Period. No direct monetary refund of the unused remainder is made upon a Plan change (refund procedure on Customer's initiative — see Section 9).

6.3. Example. In the middle of a paid monthly Period (15 of 30 days remaining) on the "Standard" Plan (990 ₽/month), the Customer switches to the "Extended" Plan (1,990 ₽/month). Amount due — 1,990 ₽ (full price of the new monthly Period). The unused remainder of the prior Period is calculated as 990 × 15/30 = 495 ₽, which is equivalent to 495 × 30 / 1,990 ≈ 8 additional calendar days of the new Plan. The total length of the new Period will be 38 days from the moment of the change.

6.4. If, under the new Plan, after taking into account the credits actually spent in the current credit cycle, the Customer would exceed the new Plan's limit, the downgrade is blocked until the start of the next cycle. The Customer receives a message in the Dashboard stating the reason.

7.1. The price of a Credit Pack is fixed and published on the /pricing page.

7.2. After successful payment, the Pack's credits are instantly added to the Customer's Credit Balance in the "purchased credits" bucket and are available for use within 12 (twelve) months from the date of crediting.

7.3. The purchase of a Credit Pack does not create a Subscription and does not entail recurring charges. Auto-renewal does not apply to Packs.

8.1. The Provider uses the Acquirer's online cash register and, for each payment operation (order creation, successful charge, refund), automatically issues a fiscal receipt in accordance with Federal Law No. 54-FZ "On the Use of Cash Register Equipment".

8.2. The receipt is sent to the Customer electronically to the email address determined in the following order of priority:

8.2.1. the address specified by the Customer in the Dashboard in the "Email for receipt" (override) field for the specific operation;

8.2.2. failing the above — the Customer's primary profile email address;

8.2.3. failing both — the Provider's fallback address configured for fiscalization purposes.

8.3. The Customer may change the receipt email address in the Dashboard at any time prior to making payment.

8.4. A paper receipt is not issued for remote sales in accordance with the law. The electronic receipt sent to the specified email address is a valid settlement document.

9.1. A refund of amounts paid by the Customer is available within 30 (thirty) calendar days of the relevant payment for the actually unused remainder. The refund is calculated using a single formula applied uniformly to both Subscriptions and Credit Packs:

Refund Amount = Payment Amount × (1 − max(share of days used, share of credits used))

where "share of days used" = (number of days elapsed since the payment date) / (total number of days of the paid Period or Pack validity), "share of credits used" = (number of credits actually deducted from this payment) / (total credits in the payment). The greater of the two shares is used.

9.2. Example for a Subscription. The Customer paid 5 days ago for the monthly "Standard" Plan at 990 ₽ (1,500 credits per month) and has spent 300 credits during this time. Share of days = 5/30 ≈ 16.7%; share of credits = 300/1,500 = 20%. The maximum is 20%. Refund Amount = 990 × (1 − 0.2) = 792 ₽.

9.3. Example for a Credit Pack. The Customer paid 5 days ago for the "Large" Pack at 6,900 ₽ (10,000 credits) and has spent 4,000 credits. Share of days (out of the 30-day refund window) = 5/30 ≈ 16.7%; share of credits = 4,000/10,000 = 40%. The maximum is 40%. Refund Amount = 6,900 × (1 − 0.4) = 4,140 ₽.

9.4. After the 30-day period, refunds on the Customer's initiative are not made. For Credit Packs, no refund is available after this period; the Customer uses the remaining purchased credits in the Service within the Pack's validity period.

9.5. Refunds are made beyond the 30-day period in the following cases:

9.5.1. technical unavailability of the Service caused by the Provider lasting more than 24 hours in a row — pro rata to the unavailability or in the form of an equivalent extension of the Subscription Period;

9.5.2. an erroneous double payment — refund of the full overpaid amount.

9.6. The refund request is sent by the Customer to support@zapnoty.ru specifying the account email or the payment identifier. The Provider reviews the request and, upon deciding to refund, issues the corresponding instruction to the Acquirer. The Acquirer's processing time is up to 10 (ten) business days from the instruction; the actual crediting time depends on the Customer's card-issuing bank.

9.7. After a Subscription refund is executed, the paid Subscription Period is closed, the remaining plan credits expire; purchased credits are retained. After a Credit Pack refund is executed, the number of credits in the "purchased credits" bucket is reduced by the refunded amount of credits.

10.1. Upon exhaustion of the Credit Balance, the Provider may, at its discretion, grant the Customer a limited grace period during which paid operations continue and the Credit Balance is allowed to go into negative territory. The specific parameters of the grace period (duration and maximum overspend) are set by the Provider and may be changed unilaterally without separate notice to the Customer.

10.2. At the end of the grace period, all paid API operations are automatically blocked with the return of HTTP 402 (Payment Required) status and a corresponding machine-readable error code. Access to the Dashboard, viewing statistics, authorization, and bot interaction remain available.

10.3. The block is lifted automatically when the Credit Balance is replenished to a non-negative value by purchasing a Credit Pack or renewing (changing) the Plan.

10.4. The Provider sends notices regarding low balance, the start of the grace period, and the onset of the block by email and/or to the linked messenger. The absence of a notice does not relieve the Customer of the obligation to monitor the state of their Credit Balance independently.

11.1. Quantitative and qualitative restrictions of the Plan (number of projects, team composition, number of forms and webhooks, delivery log retention period, support level) are determined at the time the services are provided in accordance with the price list published on the /pricing page.

11.2. The message delivery log (delivery_log) is retained for the period set by the Plan (180 or 365 calendar days; for the Enterprise plan — by agreement). At the end of the period, records are automatically deleted.

11.3. The billing operations log (recording all credit accruals, deductions, purchases, and refunds) is retained indefinitely as primary financial documentation in accordance with the requirements of the tax and accounting legislation of the Russian Federation.

11.4. Retention periods for other categories of personal data and user data are set out in the Personal Data Processing Policy (/privacy).

12.1. The Customer uses the Service in good faith and undertakes not to use it for:

12.1.1. sending messages to persons who have not consented to receive them (spam), including mass commercial, political, religious, and other broadcasts without the explicit consent of the recipients;

12.1.2. sending messages containing deception, phishing, forged financial alerts, brand impersonation, and other social engineering techniques aimed at misleading the recipient;

12.1.3. sending or storing messages, or promoting goods and services related to activities unlawful under the legislation of the Russian Federation, including (but not limited to): illegal trafficking in narcotic drugs and psychotropic substances, unlicensed gambling and online casinos, illegal trafficking in weapons and ammunition, human trafficking, materials exploiting minors, financial pyramids, counterfeit products, extremist and terrorist activity, propaganda of violence, and degradation of human dignity;

12.1.4. circumventing the quantitative limits of the Plan, using multiple accounts to bypass a single quota, automated mass registration;

12.1.5. reverse engineering of the Service, attempts to breach its security, gaining access to other Customers' resources;

12.1.6. resale of access to third parties, providing the Service's functionality to third parties on a white-label basis without a separate written agreement with the Provider;

12.1.7. use of the Service in critical infrastructure, life-support systems, as a component of medical devices, emergency notification systems, nuclear energy systems, air traffic control, and other areas where a failure of the Service could result in harm to life, health, or significant property damage.

12.2. The Customer warrants that they have the legal grounds to process the personal data of End Users transmitted by them to the Service, including for sending them messages and confirmation codes.

12.3. Breach by the Customer of the provisions of this section constitutes grounds for suspending the provision of services and/or terminating the agreement in accordance with Section 19 without refund of paid amounts.

13.1. The Provider applies automated and manual measures aimed at protecting the Service from abuse, automated registrations, spam, phishing, and other unlawful actions. The specific criteria and trigger thresholds for these measures are not disclosed by the Provider.

13.2. The Provider may, at its discretion, without prior notice and without giving reasons:

13.2.1. restrict the Customer's access to certain features of the Service or to the API as a whole;

13.2.2. temporarily suspend services on the Customer's account;

13.2.3. delete the Customer's account, unilaterally terminating the agreement.

13.3. Accounts on the Free plan with prolonged Customer inactivity may be deleted by the Provider unilaterally without prior notice. Re-registration with the Service is available at any time subject to the terms of this offer.

13.4. Upon purchase of any paid Plan, the Customer is removed from the auto-deletion queue for inactive accounts until reverting to the Free plan.

14.1. Submissions received via the Customer's forms are stored in the Service for 30 (thirty) calendar days from the date of receipt and are available to the Customer in the Dashboard.

14.2. After 30 days, submissions are automatically moved to the archive, where they are retained for at least an additional 180 (one hundred eighty) calendar days. The further period and procedure for storing archived submissions are determined by the Provider at its discretion and may be changed unilaterally without separate notice to the Customer.

14.3. The Customer may at any time manually move a submission to the archive or delete it. The Customer is responsible for exporting any submissions required for further storage outside the Service.

15.1. The Service maintains logs of user actions in the Dashboard (login, project settings changes, key administrative actions) for purposes of security and incident investigation.

15.2. The retention period for audit logs is 1 (one) year, after which records are automatically deleted.

15.3. The information processed in audit logs is described in the Personal Data Processing Policy (see Section 10 of the Policy).

16.1. The Service is provided on an "as is" basis. The Provider does not warrant uninterrupted or error-free operation of the Service, its suitability for the Customer's specific commercial purposes, or the absence of delays on the part of messengers, OAuth providers, the Acquirer, or other third parties. A service level agreement (SLA) is provided only under the Enterprise plan on the basis of a separate agreement.

16.2. The Provider's aggregate liability to the Customer on any grounds related to this agreement is limited to the amount actually paid by the Customer to the Provider during the last 12 (twelve) calendar months preceding the event giving rise to the claim.

16.3. The limitation of liability under clause 16.2 does not apply in the following cases:

16.3.1. intentional misconduct by the Provider;

16.3.2. breach by the Provider of the requirements of Federal Law No. 152-FZ "On Personal Data" that caused damages to the Customer;

16.3.3. other cases expressly provided for by the legislation of the Russian Federation.

16.4. The Provider is not liable for the inability to provide services or for improper provision of services due to force majeure circumstances, including: blocking of messengers and third-party services (Telegram, Max), Acquirer outages, actions of regulatory authorities, infrastructure provider failures, and other circumstances beyond the Provider's reasonable control.

16.5. The Customer is responsible for the accuracy of information provided upon registration and payment, for the security of API keys, access tokens, passwords, and other authorization data, and for compliance with End Users' rights when sending them messages through the Service.

16.6. The Provider is not liable for the consequences of compromise of the Customer's authorization data that did not occur through the Provider's fault, including as a result of: leakage of API keys, tokens, or passwords through the fault of the Customer or its employees; unauthorized access by third parties to the Customer's account; the Customer's use of insecure devices, networks, or software; phishing or other social engineering against the Customer.

16.7. The Provider is not liable for the actions of third parties that have gained unauthorized access to the Customer's account, or for any damage caused to the Customer as a result of such actions.

16.8. The Provider applies reasonable technical and organizational measures to protect the Service (TLS encryption of the data transmission channel, encryption of secrets at rest, access controls, regular security audits, logging of significant events) but does not guarantee absolute protection of the Service from targeted attacks by third parties on its infrastructure. In the event of a security incident resulting from unlawful actions of third parties despite the protective measures applied by the Provider, the Provider is not liable for direct or indirect damages of the Customer and shall take reasonable efforts to remediate the consequences of the incident and restore normal operation of the Service.

17.1. The Customer undertakes not to disclose to third parties the API keys and other authorization data issued to them within the Service.

17.2. The content of messages, form submissions, and other user-generated content placed by the Customer in the Service remains the property of the Customer.

17.3. The Provider undertakes not to use the content of the Customer's messages and submissions for any purpose other than the provision of services, technical support upon the Customer's request, investigation of security incidents, and compliance with lawful requirements of authorized state authorities.

17.4. The transfer of personal data of the Customer and End Users to third parties is carried out in the manner and to the extent described in the Personal Data Processing Policy.

18.1. The Provider may at any time unilaterally amend this offer by publishing a new version at the /offer address of the Service stating the effective date. Notice of specific changes is not sent to each Customer by email; the Customer monitors the current version of the offer independently.

18.2. Continued use of the Service after the effective date of the new version of the offer constitutes full and unconditional acceptance of the new version.

18.3. Changes to the pricing schedule on the /pricing page, the introduction of discounts, promo codes, temporary promotions, individual terms for specific Customers, and changes to the cost of individual operations in credits do not constitute amendments to this offer and may be carried out by the Provider at any time. For a Subscription Period already paid by the Customer, the price and terms of the Plan are fixed; new prices and terms apply upon the next renewal or Plan change.

18.4. In the event of disagreement with the new version of the offer, the Customer may terminate the agreement in accordance with Section 19.

19.1. The Customer may at any time terminate the agreement by:

19.1.1. disabling Auto-renewal in the Dashboard — access to the paid Plan is retained until the end of the current Subscription Period;

19.1.2. deleting the account in the Dashboard — access is terminated immediately, and a refund is made only in accordance with Section 9.

19.2. The Provider may terminate the agreement:

19.2.1. with written notice (by email) to the Customer 10 (ten) calendar days in advance — in the event of a detected non-gross breach of this offer by the Customer;

19.2.2. without prior notice and with immediate termination of access — in the event of gross breaches by the Customer, including the use of the Service for spam, phishing messages, unlawful content, or actions threatening the operability of the Service or the security of third parties.

19.3. Upon termination of the agreement on the Provider's initiative due to breaches by the Customer, no refund of paid amounts is made.

20.1. The laws of the Russian Federation apply to the relations between the parties.

20.2. All disputes and disagreements are resolved by the parties through negotiations. A mandatory pre-trial claims procedure applies — 30 (thirty) calendar days from the date of receipt of the claim.

20.3. Claims are sent by the Customer to legal@zapnoty.ru or to the Provider's postal address specified in Section 21. Claims from the Provider are sent to the Customer's primary email address specified in the Dashboard.

20.4. If no agreement is reached in the pre-trial procedure, the dispute is resolved in the courts of the city of Rostov-on-Don in accordance with jurisdiction (Arbitrazh Court of the Rostov Region — for disputes with legal entities and individual entrepreneurs; the court of general jurisdiction of the city of Rostov-on-Don — for disputes with individuals). For Customers who are individuals and consumers within the meaning of the Russian Federation Law "On Protection of Consumer Rights", the jurisdiction rules established by that Law apply.

Individual Entrepreneur Антонов Александр Викторович
INN: 262517638904
OGRNIP: 312265133100116

Bank details:
Bank: PJSC Sberbank
BIK: 046015602
Settlement account: 40802810652090023044

Contact email addresses:
— general support: support@zapnoty.ru
— legally significant correspondence: legal@zapnoty.ru
— personal data inquiries: privacy@zapnoty.ru

22.1. The Service offers the Customer the opportunity to participate in a partner (referral) program on the terms of this Section and the program rules published at /partners. Participation is voluntary and is activated by accepting the rules in the Dashboard.

22.2. The Customer receives a personal referral link. A person who registers with the Service for the first time via this link (the "Referral") is attributed to the Customer. Only one partner is attributed to a Referral. Registration via one's own link grants no reward.

22.3. For Service operations paid by the Referral (subscriptions, renewals, credit packs), the Customer accrues a reward: 30% of the payment amount during the first year from the Referral's registration date, and 10% over the following three years; after that period, accruals cease.

22.4. Each accrual is held for 45 (forty-five) calendar days from the payment date and then becomes available for use. If the Referral's payment is refunded within the hold period, the corresponding accrual is cancelled.

22.5. The partner reward is an internal bonus accounted for in rubles, is NOT payable in money, and is not transferable to other Customers. The available balance may be used by the Customer to pay for renewing or changing their own Plan, provided it fully covers the cost.

22.6. The Provider may unilaterally change the program terms and rates, suspend or terminate it by publishing a new revision of the rules. The Provider may cancel accruals and remove the Customer from the program upon detecting abuse (fake registrations, fraud, other bad-faith actions).

23.1. The Provider may issue promo codes granting the Customer a percentage discount on Subscription payment. The terms of a specific promo code (discount amount, applicable Plan period, validity period, number of uses) are determined by the Provider.

23.2. A promo code is applied by the Customer at checkout. A single promo code may be used by a Customer no more than once. The discount reduces the amount payable; the volume of credits granted and the Subscription Period duration do not change.

23.3. A promo code is not exchangeable for money. The Provider may restrict, suspend or terminate promo codes at any time. Introducing and terminating promo codes does not constitute an amendment to this offer (Section 18).