November 18, 2026
Acceptable Use Policy
This Acceptable Use Policy ("AUP") governs your use of Peel's websites, dashboard, APIs, and related services (the "Service"). It is part of and incorporated into our Terms of Service.
1. Allowed Uses
Peel is intended for legitimate product, engineering, research, operations, and automation use cases, including building deterministic APIs from website behavior and public web content.
Permitted uses may include:
- analyzing public web content,
- building internal tools, automations, and integrations,
- using your own valid credentials for a target you are authorized to access, when Peel supports that flow, and
- commercial use that otherwise complies with law and these policies.
2. Prohibited Uses
You may not use the Service to:
- break the law or help others break the law,
- access systems, accounts, or data without authorization,
- use stolen, shared, leaked, or otherwise unauthorized credentials,
- automate an account you are not authorized to automate, even if you hold its login,
- collect, profile, resell, or otherwise exploit personal data without a lawful basis,
- spam, harass, stalk, or facilitate surveillance or intimidation,
- copy or republish copyrighted or paywalled material in a way that infringes rights or substitutes for the original source,
- generate abusive request volume, denial-of-service traffic, or other harmful load,
- bypass sign-ins, paywalls, or other access controls you are not entitled to pass, or defeat technical protection measures in breach of law or a site's terms,
- evade blocks or rate limits in a way that is unlawful or abusive,
- distribute malware, phishing content, or fraudulent workflows,
- interfere with the Service or other users,
- share API keys or account credentials outside your organization contrary to your plan or our instructions, or
- use Peel in a way that creates material legal, security, or reputational risk for Peel or third parties.
3. Target-Site Controls and robots.txt
robots.txt is a voluntary, advisory signal for automated agents — it is not a law or a contract, and Peel does not treat it as an access-control mechanism. By default Peel does not block builds or requests based on a target's robots.txt; operators who require robots.txt enforcement for a deployment can enable it via configuration.
You are solely responsible for the targets you direct Peel to access. You represent that, for each target, you have the right to access and use that content and request surface, and that your use complies with applicable law and any agreements that bind you. Reviewing each target's terms, robots.txt, and applicable law is your responsibility, not Peel's.
Peel still applies abuse, security, and operational safeguards (such as SSRF protections, domain blocks, and rate limits), and we may refuse to build, execute, continue serving, or support targets that present abuse, legal, operational, or policy risk.
4. Personal Data and High-Risk Use Cases
If you use Peel to process personal data, you are responsible for making sure you have a lawful basis and that your downstream use complies with privacy, consumer-protection, employment, sector-specific, and other applicable law.
Do not use Peel for unlawful scraping, unlawful people-search or dossier-building, credential abuse, financial crime, stalking, or other high-risk activity.
5. Enforcement
We may investigate suspected violations of this AUP and may take action without prior notice, including:
- issuing warnings,
- rate-limiting or blocking targets,
- suspending or terminating accounts,
- disabling APIs, builds, or workflows,
- preserving relevant records, and
- reporting activity to affected parties or authorities where appropriate.
We are not required to monitor all activity, but we may do so to protect the Service, users, third parties, and Peel.
6. Reports from Site Operators and Rights Holders
A site owner who proves control of a domain can block Peel from it at once on the site-owner page. Copyright and illegal-content notices have their own notice form.
Anyone can report misuse of the Service. That includes website operators who want Peel traffic to their site reviewed or stopped, and rights holders who believe an API or marketplace listing infringes their rights. Email kaan@peel.sh and include:
- your name, organization, and how to reach you,
- the domain or URLs concerned, and the Peel endpoint or marketplace listing if you know it,
- dates, times, and any request details you have, such as IP addresses or user agents,
- what you would like us to do, for example block your domain or remove a listing, and
- for a rights claim, the work or right involved, why you believe it is infringed, and a statement that your report is accurate and made in good faith.
A person reviews every report. Depending on what we find, we may disable an endpoint, remove a marketplace listing, block builds and calls against a domain, ask you for more information, or act against the account involved under section 5. We may tell the affected customer that a report was made.
7. Updates
We may update this AUP from time to time. Material updates will be posted here and may also be communicated through the Service or by email.