Skip to content
UxerProof

Acceptable use

Acceptable use policy

Last updated: draft. This policy forms part of the terms of service.

Draft for legal review. This document is an accurate description of intended practice, written for engineering and product alignment. It has not yet been reviewed by counsel and is not final contractual language.

1. Authorisation

You may direct UxerProof only at websites and applications your organisation owns or is expressly authorised in writing to test. You must complete domain verification for every Environment and you must keep that authorisation current.

2. Prohibited activity

  • Testing any system without the owner's authorisation.
  • Security testing, vulnerability probing, fuzzing or attempts to bypass access controls.
  • Load, stress or denial-of-service testing, or any use intended to degrade a service.
  • Scraping, harvesting or bulk extraction of content or personal data.
  • Credential stuffing, brute forcing, or use of credentials you are not authorised to use.
  • Circumventing rate limits, bot protection, paywalls or terms of a third-party service.
  • Uploading production personal data, payment card data or regulated health data as Circuit input.
  • Using the platform to generate deceptive traffic, fake engagement or fraudulent transactions.
  • Reselling or providing access to the execution service as a standalone browser-automation utility.
  • Attempting to access another workspace's data, or to identify other customers.
  • Interfering with the platform's isolation, sandboxing, metering or audit mechanisms.

3. Content standards

Personas, Circuit definitions and workspace content must not contain unlawful material, harassment, or content designed to make an AI User produce it.

4. Fair use of execution capacity

Circuit credits define your entitlement. Automated or scripted attempts to exceed your entitlement, or to obtain execution capacity outside the metered path, are prohibited. Credit restoration exists for genuine infrastructure failures and must not be claimed otherwise.

5. Reporting

Report suspected abuse or a security issue through support.

6. Enforcement

We may suspend a Circuit, an Environment, a workspace or an account where we reasonably believe this policy has been breached. Where the breach is serious — in particular, testing without authorisation — suspension may be immediate and without notice. We will tell you what triggered the action and, for recoverable cases, what is required to restore access.

7. Changes

We will give notice of material changes to this policy before they take effect. See also responsible testing.