Acceptable use and fair use
The boundaries of acceptable use and the fair-use limits on free, the plan and AI metering.
Published 1.0 · 2026-09-18
Effective date: 18 September 2026
1. Acceptable use
You may not use WebCrew to:
- operate on websites you are not authorised to operate on — every connected site warrants authority (Terms §3.1);
- scan, test or attack systems beyond the websites you connected;
- process or distribute unlawful content, or use the service to violate applicable law;
- circumvent metering, tenant isolation, or the approval boundary;
- resell the service itself other than by managing your clients' sites inside your own workspace (that is what it is for).
We may suspend affected workspaces on violation, per Terms §6.
2. Fair use on the free plan
Free exists to evaluate WebCrew on up to five production websites. It provides visibility — inventory, uptime and connection status, version and vulnerability visibility, read-only agent access — within limits that keep it free: 30 days of history, bounded API and agent request rates as published in the Documentation, no retained backups, no scheduled autonomy, no promised support.
Free is capped at five production sites per Account. Free is not infrastructure for running a fleet. Systematic workarounds — rotating sites through free workspaces, splitting one fleet across accounts, or registering multiple accounts for one organisation — are outside fair use, and we will ask you to consolidate before we do anything else.
3. Fair use on the paid plan
The plan includes the operational loops it lists, sized for normal agency use per site:
- Backups: the published daily cadence and retention window per site. Hourly restore points are the High-frequency Backup add-on.
- Monitoring and checks: at the published intervals; the plan is not a load-testing or scraping service.
- Reports: scheduled white-label reports per site at the published cadence.
- API and MCP: rate limits as published in the Documentation, generous enough for real automation, bounded enough that one workspace cannot degrade others.
4. AI metering
AI actions are metered, never silently billed:
- Credits are the unit of metered AI usage, purchased in advance at the rate published on the price page. The rate is published, not implied, so that a revaluation would be a visible price change under clause 12.2 of the Terms rather than a quiet one.
- Allowances and metering are per production site per day, resetting at midnight Europe/Amsterdam. Unused daily capacity does not roll over.
- Staging sites receive no paid-site allowance.
- When metered usage is exhausted or a spend ceiling you configured is reached, the agent tells you and stops. It does not queue unauthorised work and it does not bill an overage you did not enable.
- Heavy sustained usage is better served by bring-your-own-key, and the product recommends it when your usage pattern crosses that line.
5. What fair use is not
Fair use is not a hidden cap. Every bounded quantity above is published with its number, and hitting a boundary produces a message that names it — never a silent degradation. Where your genuine use outgrows a boundary, the answer is a conversation about add-ons or BYOK, not a surprise invoice.