Permission first✳Document the scope✳Be polite✳Stop when asked✳
Permission first✳Document the scope✳Be polite✳Stop when asked✳
Responsible automation guidance

Permission before automation.

This project is for testing websites you own or are explicitly permitted to assess, preferably in staging or through a test endpoint provided by the site owner.

Hard boundary: This project does not attempt to defeat CAPTCHAs, access controls, rate limits, bot protections, or account security. Do not use it to evade protections or access systems without permission.

Appropriate uses

  • Use a documented API where available and follow its terms.
  • Use Playwright Chromium for normal rendering, form, and session testing within an authorized scope.
  • Identify the client honestly with a stable, descriptive profile.
  • Keep cookies and session state only in a local profile for an authorized test account.
  • Use conservative delays, bounded retries, and exponential backoff.
  • Use only proxies that you own or are explicitly authorized to use and have configured.

Do not use this project to

  • Solve or bypass CAPTCHAs or security checks.
  • Spoof fingerprints, headers, cookies, or TLS behavior to impersonate users or defeat bot detection.
  • Scrape proxies, abuse residential proxies, or evade IP blocks.
  • Stuff credentials, scrape private data, bypass authentication, or access systems outside written scope.
  • Continue after an explicit opt-out, stop request, or access denial.

Operational checklist

  1. Confirm written authorization, target scope, and allowed test methods.
  2. Prefer staging or a test endpoint supplied by the owner.
  3. Set a low request rate and a clear stop condition before starting.
  4. Log outcomes without sensitive payloads; remove secrets from logs and history.
  5. Stop on 401, 403, repeated 429 responses, or an explicit opt-out.
  6. Stop immediately when the system owner asks.

For a CAPTCHA or security challenge during an approved test, pause and use the documented human handoff; do not solve or automate the check. See the terms and scope and the privacy notes.