Acceptable Use Policy

1. Permitted Use

You may use Statvisor to:

• Monitor the performance and reliability of your own backend APIs
• Integrate the Statvisor SDK into applications you own or are authorised to modify
• View and analyse API metrics in the Statvisor dashboard
• Manage projects, API keys, and billing for your account
• Access the Statvisor API for programmatic integrations with your own tools

2. Prohibited Use

You must not use Statvisor to:

• Monitor APIs or systems you do not own or do not have explicit authorisation to monitor
• Send false, synthetic, or artificially inflated event data to manipulate metrics
• Attempt to reverse-engineer, scrape, or extract data from other users' projects
• Circumvent plan limits by creating multiple accounts to obtain additional free-tier resources
• Resell or white-label access to Statvisor without a written agreement
• Use the platform in violation of any applicable law, including data protection and privacy regulations
• Transmit malicious code, viruses, or any material that could harm our infrastructure or other users
• Perform any action that places unreasonable load on our ingest or API infrastructure (e.g. deliberate high-frequency event flooding)
• Use the platform to process or transmit end-user personally identifiable information through event payloads
• Attempt to gain unauthorised access to other accounts, servers, or network resources

3. Rate Limits & Fair Use

The Statvisor ingest endpoint is designed for real production API traffic. We apply rate limits to prevent abuse and to ensure fair access for all users. If your usage pattern is consistent with a genuine production workload, you will not encounter these limits under normal circumstances. If you anticipate unusually high event volumes, please contact us before sending to discuss options.

4. Data Sent via the SDK

The Statvisor SDK is designed to capture only performance metadata (route, method, status code, duration). You are responsible for ensuring that no personally identifiable information (PII) is included in the data sent to Statvisor. This includes, but is not limited to:

• Configuring custom path normalization to avoid leaking user IDs in route names
• Ensuring route patterns (not raw URLs) are what gets captured
• Not sending request or response body data via any SDK extension

5. Enforcement

We reserve the right to investigate any suspected violation of this AUP. Upon confirmation of a violation, we may, without prior notice: warn your account, throttle your ingest rate, suspend your account temporarily, or permanently terminate your account and delete associated data. We will endeavour to notify you of enforcement actions by email except where immediate action is required to protect our platform or other users.

6. Reporting Violations

If you become aware of a violation of this AUP by any user, please report it to abuse@statvisor.com. Include as much detail as possible so we can investigate promptly.