Terms of Service

01The Service

The Service sends automated test traffic to hostnames your organization has verified, and reports on what came back. There are two kinds of unit: an HTTP request, and an automated browser session run in Chromium. Every unit identifies itself with AutomatedTrafficTest/1.0 in its user agent.

Reports keep three figures apart: test activity, analytics events observed during browser sessions, and verified human visits, which is always zero. The Service does not supply visitors. You must not present its output as human, audience or advertising traffic to anyone, including clients, advertisers, analytics vendors, investors and marketplaces.

02Authorization

You may target only systems you own or are authorized in writing to test. Before a hostname can be used, your organization must prove control of it with a DNS TXT record or a file under /.well-known/; subdomains are included only if you enable them. Each campaign also asks you to confirm your authorization, and that confirmation is recorded in the audit log.

Verification shows that you control a hostname. It does not, by itself, authorize load on systems behind it that belong to others, such as a hosting provider, a CDN or the third-party services your pages call. You are responsible for the load your campaigns place on all of them, and for any permission their own terms require.

When your authority ends, for example at the close of a client engagement, stop testing and remove the domain.

03Acceptable use

Your use must follow the Acceptable Use Policy, which forms part of these terms. It sets out what is never permitted and the actions we may take, from cancelling a campaign to suspending an organization.

04Accounts and organizations

• Provide accurate details. You must verify your email address before adding domains or creating campaigns.
• A person may belong to several organizations. Owners and admins decide who is a member and in which role, and are responsible for what members do.
• Keep passwords and API tokens secret. Tokens are shown once, carry scopes and an expiry, and can be revoked at any time under Settings, API tokens. Revoke any token you believe has been exposed.
• You are responsible for all activity under your organization, through the dashboard or the API.

05Credits and payment

Usage is measured in credits: 1 per HTTP request and 10 per automated browser session, as shown on the pricing page and in every campaign estimate. A one-time trial allowance is added when you verify your email address.

When a campaign is created, its maximum cost is reserved from your available balance. Credits are consumed only for billable units. An HTTP request is billable when the target returned a response, whatever its status code; a browser session is billable when its page navigation received a response. Timeouts, connection errors and blocked destinations are never billed. The rest of the reservation is released automatically when the campaign ends, whether it completed, was cancelled or failed.

Plans are billed monthly through our payment provider and renew until cancelled under Billing; each paid period adds the plan’s included credits, which do not expire. Credit packs are one-time purchases. Prices are set by us and shown before checkout. Card details are handled by the payment provider and never stored by us. Every change to your balance is recorded in the credit ledger under Billing, and refunds follow the Refund Policy.

Credits are not money. They cannot be exchanged for cash or moved between organizations.

06Limits

Every campaign is bounded by your plan’s limits on units, rate per second, duration, concurrent active campaigns and number of domains, and by a platform-wide ceiling on the rate sent to any one host. Where two limits apply, the stricter one wins. We may change limits, and will give notice before reducing those of a paid plan.

07Your data and reports

You keep the rights to what you bring to the Service: hostnames, campaign settings and the results of your tests. We process it to run, secure and bill for the Service, as the Privacy Policy describes. Event logs export as CSV, reports download as JSON, and a copy of your account data is available from Settings, Privacy.

Raw events are kept for 90 days after a campaign settles, the same period on every plan, and are then deleted. After that, the campaign’s report is served from a stored snapshot and daily totals, and the report says so. Export the event log before then if you need it.

08Suspension and closure

You may close your account at any time from Settings, Privacy. If you are the last owner of an organization, closing your account also closes that organization and cancels its running campaigns; their unused reservations are released as usual.

We may cancel campaigns, revoke domain verifications, or suspend users or organizations that breach these terms or the Acceptable Use Policy, as described under Enforcement. A suspended user is signed out everywhere. A suspended organization’s running campaigns are cancelled, and it cannot use the dashboard or its API tokens until the suspension is lifted. Each action is recorded, with its reason, in the audit log.

09Availability and changes to the Service

The Service is provided “as is”. We work to keep it running but do not promise uninterrupted operation, and test regions are offered only where our workers actually run. We may change features of the Service; when a change materially affects a paid plan, we will tell organization owners before it takes effect.

10Liability

To the extent the law allows, our total liability for any claim relating to the Service is limited to the amounts your organization paid us in the twelve months before the claim arose. We are not liable for indirect or consequential loss, including outages or costs at systems you chose to test.

You are responsible for claims brought by third parties because of traffic you directed at systems you were not authorized to test. Nothing in these terms limits liability that cannot lawfully be limited.

11Changes to these terms

When we change these terms we update the date at the top of this page. For a material change we will email organization owners before it takes effect. Continuing to use the Service after that date means you accept the revised terms.

12Contact

Questions about these terms: write to us. To report traffic you did not authorize, use the abuse form.