Acceptable Use Policy: OpenWAF Tasks addendum (draft)
Last updated: October 29, 2026
This is an English translation provided for convenience. In case of any discrepancy, the Spanish version prevails.
Pending legal review. This addendum describes the rules we apply to OpenWAF Tasks today. It has not yet been reviewed by a lawyer and may change.
In short
- OpenWAF Tasks runs your scripts and AI agents on a schedule in OpenWAF Browsers. Use it for work a person could do and would put their name to.
- No spam, no mass posting, no account creation, no scraping against a site’s terms, no getting around CAPTCHAs.
- Every write a task makes needs the approval of a person, who is responsible for what they approve.
- We keep a record of every run and every approval, to handle abuse.
- We may pause tasks and suspend organizations without notice when they are abused. Report abuse to abuse@openwaf.dev.
1. Scope
This addendum adds rules to the Acceptable Use Policy for OpenWAF Tasks, the scheduled browser tasks of OpenWAF Cloud, operated by AI Services LLC. It applies to every organization that has access to OpenWAF Tasks, to its members, to its API tokens and to every script, agent or person that creates, runs or approves its tasks. Tasks run in OpenWAF Browsers, so the OpenWAF Browsers addendum applies to them too. Everything in the Acceptable Use Policy and the Terms of Service still applies; where this addendum is stricter, it prevails for OpenWAF Tasks.
The organization is responsible for what its tasks do, including what an agent decides on its own and what its members approve.
2. Prohibited uses
You must not use OpenWAF Tasks, or let a script or an agent use it, for:
- spam: unsolicited messages, comments, posts or form submissions, or advertising where it is not welcome;
- mass posting: publishing the same or similar content in many places, threads, accounts or sites, or at a pace that no person would keep;
- creating accounts, or producing fake engagement: reviews, ratings, votes, comments, clicks, views, followers, sign-ups or purchases that do not come from a real decision of a real person;
- scraping or crawling a site where its terms of use or its robots.txt forbid that kind of automated access, or collecting personal data without a legal basis;
- getting around CAPTCHAs, bot challenges, logins, paywalls or rate limits, including by passing them to people or to third-party solving services;
- acting on accounts you are not authorised to use, or posting on behalf of someone who has not agreed to it;
- harassment, fraud, scams, phishing, malware, or creating or sending illegal content;
- getting around the approval of actions, the per-domain limits or the read-only browser, or splitting work across tasks or organizations to exceed them.
3. Approval is required
A task cannot post, submit or delete anything on its own. It proposes the exact steps, and a member of the organization approves or rejects them. Whoever approves an action must read its steps and its target first, and is responsible for it as if they had done it themselves. Do not approve actions in bulk without reading them, and do not give approval rights to people who will not review what they approve.
Automatic approval is available only on the decision of an operator, for internal, non-public targets. We do not offer it for third-party sites.
4. What we keep
For every run we keep its status, logs, screenshots, output, the requests the read-only browser blocked and, for agents, the number of model calls and tokens. For every approval we keep the proposed steps and their hash, the target, who approved or rejected it, when and why, and the result. Screenshots and other artifacts are kept for 30 days. We use these records to run the service, to enforce quotas and this addendum, and to handle abuse reports. How we process personal data is described in the Privacy Policy.
5. Suspension and termination
We may pause a task, cancel its runs, stop OpenWAF Tasks for an organization or for everyone, or terminate an organization’s access, at any time and without notice, when we see or are told about abuse or a breach of this addendum, or when a use puts the service or other people at risk. Access to OpenWAF Tasks is given on approval during the public beta and can be withdrawn. We may also preserve the relevant records and disclose them to the competent authorities when the law requires it.
When we act, we will tell the organization why whenever possible. The appeals process of the Acceptable Use Policy applies.
6. How to report abuse
If a task of OpenWAF Tasks is misusing your site or service, write to abuse@openwaf.dev with the date, time and time zone, the affected URLs, the source addresses and, if present, the Web Bot Auth headers of the requests, a description of the abuse and your contact details. Section 7 of the Acceptable Use Policy applies to authorities.
7. Changes
This addendum is a draft pending legal review, and we may update it. Significant changes will be notified as described in the Terms of Service.