Acceptable use policy
Use OverRider only on websites you own or have written permission to test. Do not use it to generate ad impressions or clicks, to inflate metrics reported to advertisers, clients or investors, or to overload third-party services.
OverRider is a testing tool. Like any testing tool it can be misused, and some misuses carry consequences serious enough to be worth stating plainly.
Acceptable
- Testing websites you own. Load testing, analytics validation, QA, staging checks.
- Testing on behalf of a client who has given you written authorisation.
- Testing your own infrastructure — CDN behaviour, caching, rate limits, autoscaling.
- Validating your own tracking — analytics properties, tag manager containers, consent flows.
- Research and education, on systems you control.
Not acceptable
Advertising fraud
Never point OverRider at pages to generate ad impressions or clicks — including on your own site. Ad networks detect this reliably. The realistic outcome is permanent termination of your AdSense or network account and forfeiture of unpaid earnings. In many jurisdictions it is also fraud in the legal sense.
This applies to every form of it: display impressions, click-throughs, affiliate link traffic, and sponsored-post traffic used to justify a rate.
Sites you do not own or control
Sending automated traffic to someone else’s website without their permission is unauthorised use of their infrastructure. Depending on volume and jurisdiction it may breach computer misuse laws, and at minimum it breaches their terms of service.
Misrepresenting metrics
Using generated traffic to inflate figures shown to advertisers, clients, investors or acquirers is misrepresentation, regardless of which tool produced the numbers. The traffic being technically real does not make the representation honest.
Denial of service
Load testing is for infrastructure you are responsible for. Directing high-concurrency traffic at a third-party service to degrade it is an attack, not a test.
Circumventing protections you were not asked to test
The anti-detection features exist so your test traffic behaves like a real browser on your own site. Using them to get around access controls, paywalls or rate limits on services you do not own is outside what this tool is for.
Why this matters to you specifically
These are not abstract risks:
| Misuse | Realistic outcome |
|---|---|
| Ad traffic generation | Ad account terminated, earnings forfeited, possible legal exposure |
| Inflating client reports | Contract terminated, professional reputation damaged |
| Traffic to third-party sites | Abuse complaints to your ISP, potential legal action |
| Polluting your own analytics | Months of unusable data and decisions made on bad numbers |
Keep test traffic out of your real reporting
Even for entirely legitimate testing, generated traffic mixed into your production analytics will distort your figures — the engagement metrics in particular, since OverRider sessions rarely bounce.
Consider using a separate GA4 property for testing, applying an internal-traffic filter, or at minimum documenting your test windows so nobody later reads a spike as real growth.
Your responsibility
You are responsible for how you use OverRider and for complying with the terms of service of every platform involved — your host, your analytics provider, your ad networks, and any site you send traffic to.
If you are unsure whether an intended use is acceptable, ask us at support@overrider.io before running it.
Last updated: