Neogate
RUsign in ↗

Public Offer for Neogate Web Resource Protection Services

Version of 25 September 2026

Reference translation. The Russian text is the binding version; if the two differ, the Russian one prevails.

This document is a public offer (article 437 of the Civil Code of the Russian Federation) by Arseniy Pavlovich Devov (the Contractor) and contains all the essential terms of an agreement for web resource protection services under the Neogate name.

#1. Terms

1.1. Service — the Contractor's hardware and software system through which the traffic of the Customer's Resource passes and which filters that traffic.

1.2. Resource — a domain name (including subdomains) connected to the Service by the Customer.

1.3. Customer's Server (the origin) — the server that hosts the Resource and to which the Service passes the cleaned traffic.

1.4. Dashboard — the part of the Service at https://dash.neogate.systems where the Customer manages Resources, sees statistics and attack reports, and pays for the Service.

1.5. Attack — actions of third parties aimed at making a Resource unavailable by sending it a large number of requests or connections.

1.6. Plan — a set of terms of the Service (number of Resources, report retention period) and its price, published in the Dashboard.

1.7. Paid period — the term for which the Customer has paid under the Plan.

#2. Subject of the agreement

2.1. The Contractor provides the Customer with a service that protects Resources from Attacks at the application layer (HTTP and HTTPS) by passing the Resource's traffic through the Service (the Service), and the Customer pays for it.

2.2. The Service includes:

  • receiving the Resource's traffic at the network addresses of the Service and passing it to the Customer's Server;
  • filtering requests, including request rate limiting, checking the visitor's browser, and blocking the sources of an Attack;
  • caching the responses of the Customer's Server where the Resource's settings provide for it;
  • issuing and renewing the TLS certificate for the Resource;
  • traffic statistics, Attack reports and Telegram notifications in the Dashboard.

2.3. Volumetric attacks at the network and transport layers (L3/L4) are filtered, among other means, by upstream network operators. The Contractor does not guarantee to repel Attacks of any size and any kind.

2.4. During an Attack some legitimate visitors may have to pass an extra browser check or may be temporarily refused service. This is normal operation of the Service and is not a defect of the Service.

2.5. The conditions of availability of the Service and the compensation for failing to meet them are set out in the Service Level Agreement (SLA), which is part of this offer.

#3. Acceptance and conclusion of the agreement

3.1. Acceptance of the offer is payment for the Service or the start of use of the Dashboard, including during the trial period. From the moment of acceptance the agreement is concluded on the terms of this offer.

3.2. By accepting the offer, the Customer confirms that they have read the offer, the Acceptable Use Policy, the Privacy Policy and the SLA, and accept them.

3.3. The Customer confirms that they have the right to dispose of the domain names they connect to the Service and of the Customer's Server.

#4. Connecting a Resource

4.1. To connect a Resource, the Customer gives the Contractor the domain name and the address of the Customer's Server and then points the Resource's DNS records at the addresses shown in the Dashboard.

4.2. The Service for a Resource is considered provided from the moment the Resource's traffic begins to arrive in the Service.

4.3. For effective protection, the Customer restricts access to the Customer's Server so that it accepts incoming connections only from the addresses of the Service shown in the Dashboard. If the Customer's Server can be reached directly, an Attack may be aimed at it bypassing the Service, and the Contractor is not responsible for such unavailability.

4.4. The Customer promptly tells the Contractor of any change of the address of the Customer's Server.

#5. Price and payment

5.1. The price of the Service is set by the Plan. Current Plans are published in the Dashboard.

5.2. The Service is paid in advance for 1, 3, 6 or 12 months. For a term of more than a month the discount shown in the Dashboard applies.

5.3. Payment is made in rubles through a payment service, the link to which is generated in the Dashboard. The payment methods (bank card, the Faster Payments System (SBP), others) are determined by the payment service.

5.4. The payment obligation is considered fulfilled from the moment the payment service confirms the payment. The Paid period is extended automatically after confirmation.

5.5. A new Customer gets a free trial period of 3 days. After the trial period the Service is provided on condition of payment.

5.6. If the Plan is changed within the Paid period, the unused balance is recalculated into days of the new Plan in proportion to the prices of the Plans.

5.7. There is no automatic charging of funds. The Customer renews the Service themselves.

#6. End of the Paid period

6.1. If the Paid period has ended, the Contractor continues to provide the Service in full for 3 days (the grace period) and sends the Customer notifications.

6.2. When the grace period ends, the Contractor keeps passing the Resource's traffic through the Service, but restricts changing the Resources' settings in the Dashboard until payment is received.

6.3. If payment is not received within 30 days after the end of the Paid period, the Contractor may stop serving the Resources, with at least 3 days' notice to the Customer. Before that, the Customer should point the Resource's DNS records at the Customer's Server or at another provider.

#7. Rights and obligations of the parties

7.1. The Contractor undertakes to:

  • provide the Service in accordance with this offer and the SLA;
  • notify the Customer of planned work affecting the Service at least 24 hours ahead;
  • handle the Customer's requests sent in the Dashboard or by email to admin@neogate.systems.

7.2. The Contractor has the right to:

  • change the technical filtering methods, if this does not weaken the protection of the Resource;
  • temporarily restrict traffic to a Resource if this is needed to repel an Attack or to keep the Service and the Resources of other customers working;
  • suspend the Service in the cases provided for by the Acceptable Use Policy.

7.3. The Customer undertakes to:

  • follow the Acceptable Use Policy;
  • give a valid email address in the Dashboard and follow the notifications;
  • not give access to the Dashboard to third parties, other than the members of their projects added with the tools of the Dashboard;
  • keep the Customer's Server working on their own.

7.4. The Customer may at any time give up the Service by notifying the Contractor by email or through the Dashboard.

#8. Refunds

8.1. If the Customer gives up the Service, the Contractor refunds the price of the unused part of the Paid period in proportion to the number of full days remaining.

8.2. Costs actually incurred by the Contractor in connection with the payment, including the payment service's fee if it is not refunded to the Contractor, are deducted from the refunded amount.

8.3. The refund is made within 10 days from the date the request is received, in the same way the payment was made, unless the parties agree otherwise.

8.4. The cost of the trial period and of days credited as compensation under the SLA is not refundable.

8.5. If the Service is ended because the Customer violated the Acceptable Use Policy, the refund is made under clauses 8.1–8.3, unless the law provides otherwise.

#9. Liability

9.1. The Contractor is not responsible for:

  • the content of a Resource and the lawfulness of the Customer's activity;
  • unavailability of a Resource caused by a fault, overload or wrong configuration of the Customer's Server;
  • the consequences of Attacks aimed at the Customer's Server bypassing the Service;
  • the actions of network operators, domain registrars and certificate authorities;
  • restrictions on access to a Resource required by authorized government bodies.

9.2. The Contractor is not responsible for the Customer's lost profit or other indirect losses.

9.3. The Contractor's liability under the agreement is limited to the amount paid by the Customer for the last month of the Service. The limit does not apply where the law does not allow it, including in relations with consumers.

9.4. The parties are released from liability for failure to perform obligations caused by force majeure.

#10. Personal data

10.1. The Contractor processes the Customer's personal data in accordance with the Privacy Policy.

10.2. The Customer instructs the Contractor to process the personal data of the visitors to the Resource (IP address, browser details, request address, request time) to the extent and for the purposes needed to provide the Service, in accordance with part 3 of article 6 of Federal Law No. 152-FZ. The Contractor keeps this data confidential and takes the protection measures set out in the Privacy Policy.

#11. Dispute resolution

11.1. Disputes are resolved by negotiation. A claim is sent by email to admin@neogate.systems and is reviewed within 10 days.

11.2. If the dispute is not settled, it is resolved in court at the Contractor's place of residence. A Customer who is a consumer may go to court under the rules set by consumer protection law.

11.3. The agreement is governed by the law of the Russian Federation.

#12. Changes to the offer

12.1. The Contractor may change the offer, the Plans, the Acceptable Use Policy, the Privacy Policy and the SLA by publishing a new version at least 7 days before it takes effect and notifying the Customer in the Dashboard.

12.2. A change of price does not apply to a Paid period that has already been paid.

12.3. If the Customer does not agree with the new version, they may give up the Service with a refund under section 8.

#13. Term

13.1. The agreement is in force until either party terminates it.

13.2. The Contractor may terminate the agreement in the cases provided for by clause 6.3 of the offer and by the Acceptable Use Policy.

#14. Contractor's contacts

Arseniy Pavlovich Devov
Email: admin@neogate.systems
Complaints about the content of Resources: abuse@neogate.systems
Dashboard: https://dash.neogate.systems

link to the section copied