Policy

Acceptable use

Last updated 26 August 2026

What it is for What is prohibited What we enforce in code Reporting misuse

Scrinly renders web pages and returns visual evidence: screenshots, ordered regions, comparisons, monitoring results, or a Visual Style Guide. This policy governs what customers may point it at. It applies to every plan, including the free one, and breaking it is grounds for suspension without refund.

What Scrinly is for

• Capturing screenshots and previews of pages, including your own product.
• Visual regression testing, QA and monitoring of sites you operate.
• Giving an agent or pipeline visual context from JavaScript-heavy pages.
• Reviewing the visual system of a page you are authorised to inspect.
• Archiving how a page looked at a point in time.

What is prohibited

Accessing what you are not entitled to

• Pages behind a login, paywall or access control you do not hold the right to use, including by supplying credentials or cookies that are not yours.
• Any attempt to defeat a site's access controls, rate limits or bot protections.
• Using Scrinly to evade a site's technical restrictions or to turn repeated captures into unauthorised systematic traversal.

Other people's property

• Reproducing, republishing or passing off a third party's website, design or content as your own.
• Using screenshots, regions, comparisons, or Visual Style Guides to clone a site you have no right to copy.
• Infringing copyright, trademarks, trade secrets, or a site's own terms of service.

People's personal data

• Collecting, aggregating or indexing personal data about individuals — names, contact details, profiles — from any source.
• Building people-search, lead-scraping or profile-enrichment products on top of Scrinly.
• Processing special-category personal data through the API at all.

Volume and disruption

• Any use intended to degrade, overload or deny service to a target site.
• Systematically harvesting a site's content for redistribution or resale.

Illegal and harmful content

• Anything unlawful where you or the target are located.
• Child sexual abuse material, content facilitating violence or harassment, or malware distribution.

What we enforce in code, not just in policy

A policy nobody enforces is a wish. These are properties of the system rather than promises about behaviour:

• Restricted Scrinly-operated traversal obeys robots.txt. Any internal override requires a domain verification token at /.well-known/scrinly-verify.txt, remains confined to that verified host, and is never a public customer capability.
• There is no proxy support. Proxy parameters are rejected by the API and the platform provides no upstream proxy, so evading an IP block is not something Scrinly can do for you.
• No CAPTCHA solving and no authentication bypass. Neither exists in the product.
• Per-host rate limits of one request per second and two concurrent, shared across all customers hitting the same host.
• Restricted automated traversal identifies itself with a stable user-agent linking to our automation transparency and blocking instructions.

Reporting misuse

If you believe Scrinly is being used against your site or your rights, email hello@scrinly.com. Include a hostname and an approximate time and we will identify the account and act on it. We can block a domain at our end on request from its operator, and we do so without requiring the requester to prove anything beyond an obvious connection to the site.