HomeFeaturesPricing

Acceptable Use Policy (AUP) - Zirvo

Last updated: June 12, 2026 • Version: 1.0

Table of Contents

  1. 1. Prohibited Use
  2. 2. Authorization Requirement
  3. 3. Infrastructure Abuse
  4. 4. Rate Limiting and Fair Use
  5. 5. Security and Reverse Engineering
  6. 6. Network and Probe Abuse
  7. 7. Enforcement
  8. 8. Monitoring, Auditing and Logs
  9. 9. Abuse Reporting and Contact

This Acceptable Use Policy defines the strict guidelines and rules for using all services, APIs, tools, distributed probe networks, and systems provided by the Zirvo platform, a global ecosystem for critical monitoring and digital infrastructure observability.

This AUP applies to all Users, organizations, and tenants (regardless of their plan - Free, Pro, or Agency). Compliance with this document is a mandatory requirement to maintain the security, integrity, availability, and high performance of Zirvo for the entire global customer community.

1. Prohibited Use

It is expressly forbidden to use the Zirvo Platform to perform, assist, conceal, plan, or facilitate any of the activities described below:

a) Network Attacks and Service Disruption

Using Zirvo verification resources or global probe network to conduct DoS/DDoS attacks, connection exhaustion, brute force, or packet flooding against any endpoint or server.

b) Unauthorized Reconnaissance and Mapping

Using the verification network to perform open port scanning, private network mapping, aggressive content scraping, data mining, or systematic explorations without formal written authorization.

c) Unauthorized Monitoring

Instantiating uptime monitors to track resources or proprietary assets belonging to third parties who have not explicitly authorized compliance data collection or logging.

d) API Abuse and Excessive Automation

Conducting abusive read or write calls against Zirvo public APIs to circumvent Rate Limits, or implementing scripts simulating multiple users to divert the platform computational capacity.

e) Distribution of Malicious Content or Artifacts

Using the platform, public status pages, or hosted data paths to disseminate links to malware, exploits, phishing, or fraudulent schemes.

2. Authorization Requirement

2.1. Legitimacy Principle

The User declares and warrants that they have full and verifiable legal authority over all digital systems and assets registered on the Zirvo platform for monitoring. You are only authorized to register assets that:

  • Are legitimately owned by you or your registered legal entity (tenant);
  • Are personally or officially administered by you in compliance with internal institutional rules;
  • Have written and verifiable authorization issued by the respective infrastructure owner.

2.2. Ownership Verification

Zirvo reserves the right to require, at any time, documentary proof or automated ownership validation routines as a mandatory prerequisite to enable or maintain active high-frequency monitors.

3. Infrastructure Abuse

To protect the resilience and operational latency of our global mesh during high-scale periods, the following is strictly prohibited:

a) Intentional Check Overload: Creating a disproportionate volume of redundant queries against the same host at sub-second intervals to emulate aggressive behavior exceeding operational quotas.

b) Artificial Traffic and Stress Testing: Using the Zirvo network to subject monitored applications to heavy load tests or massive data volumes. Our probe requests exist solely to read compliance parameters (uptime and SLA) - not to simulate active volumetric traffic.

c) Platform Performance Impact: Executing actions aimed at exhausting Redis session memory, congesting our distributed queue buses, or forcing prolonged timeouts on our monitoring workers.

4. Rate Limiting and Fair Use

4.1. Dynamic Technical Limits

We operate under a strict Rate Limits model managed across three independent layers: global IP level, regional tenant/organization level, and specific endpoint level. These limits ensure no single tenant can monopolize I/O, database connections, or worker parallelization capacity.

4.2. Blocking for Anomalous Behavior

Any traffic that appears anomalous or outside the predictability standard for the selected plan may be unilaterally throttled, temporarily suspended, or rejected entirely without prior notice.

4.3. Fair Use Enforcement

Monitoring quotas are established with technical precision. Attempts to circumvent them through multiple ghost accounts, artificial IP rotation, or malicious configuration duplication will result in permanent blocking of the associated credentials.

5. Security and Reverse Engineering

The architecture and algorithms that power our detection processes are highly confidential protected assets. The User is strictly prohibited from:

  • Attempting decompilation, disassembly, or reverse engineering of Zirvo compiled tools, Workers, or proprietary SDKs;
  • Actively exploring protected private API routes, endpoints, or hidden administrative interfaces;
  • Bypassing authentication mechanisms (JWT), encrypted API Key authentication, or implementing schemes to bypass billing engine flows;
  • Using any invasive method to monitor or extract the topological map, PostgreSQL database schemas, or Redis clusters internal to Zirvo.

6. Network and Probe Abuse

6.1. Exclusive Purpose

The infrastructure of verification servers and sub-workers distributed across multiple global data centers exists exclusively for website reliability monitoring, SSL certificate verification, and statistical resolution of corporate DNS queries.

6.2. Blocked Malicious Activity

Any attempt to use our probe IPs to inject SQLi, XSS, simulate false incidents, or make consecutive calls against third-party firewalls constitutes a serious breach of trust and will result in immediate resource revocation and submission of traffic logs to the appropriate cybercrime law enforcement authorities.

7. Enforcement

In the face of any suspicious or inappropriate behavior, or direct violation of the rules set forth in this AUP, Zirvo reserves the right to execute severe and immediate punitive measures. Such measures include:

• 1. Temporary suspension of the Account, Workspaces, or Monitors involved;

• 2. Permanent account termination with total forfeiture of refund rights;

• 3. Automatic blocking of traffic and requests directed to Zirvo platform hosts;

• 4. Revocation of access and blocking of API keys with no right to technical appeals;

• 5. Inclusion of domains in firewall restrictions across our entire redundant mesh.

Emergency sanctions applied in critical situations to contain immediate threats will be applied without prior notification to the User.

8. Monitoring, Auditing and Logs

For strict compliance, abuse management, and infrastructure integrity purposes, we collect and audit telemetry data based on platform usage.

Connection records, API call patterns, monitor configurations, and associated metadata may be retained and analyzed to detect violations of this AUP and to protect the stability of the platform and its users.

9. Abuse Reporting and Contact

If you identify or suspect that Zirvo corporate probe infrastructure is being misused against your servers, or to report abusive instances associated with our addresses, use our official channels:

Legal and Compliance: legal@zirvo.com.br

Security and Vulnerabilities (Abuse Detection): security@zirvo.com.br

Technical and Platform Support: suporte@zirvo.com.br

Executive Communications: zirvo@zirvo.com.br