Security Policy

Screpy uses commercially reasonable safeguards to protect accounts, website monitoring data, audit results, reports, and product infrastructure.

We do not claim security certifications on this page. Security practices may change as the product, infrastructure, and threat environment evolve.

Screpy may use access controls, encrypted connections, logging, monitoring, provider-level infrastructure protections, backups, and internal review practices to reduce risk.

The public site is configured for Cloudflare Workers, and Cloudflare may provide hosting, runtime, routing, and infrastructure-level protections for parts of the service.

Customers are responsible for keeping login credentials secure, using strong passwords, limiting user access to authorized people, reviewing workspace permissions, and contacting us quickly about suspicious activity.

Customers should only crawl, audit, monitor, or track websites and data they own, manage, or are authorized to access.

If you believe you found a security issue, email hello@screpy.com with a clear description, affected URL or feature, reproduction steps, impact, and any relevant screenshots or logs.

Please avoid accessing, modifying, deleting, or exfiltrating data that does not belong to you. Do not run tests that disrupt service availability or harm other customers.

We review security reports based on severity, reproducibility, and potential customer impact. We may contact you for more detail and may limit public disclosure until a fix or mitigation is available.

Screpy does not currently offer a public bug bounty program unless a separate written program is announced.