Acceptable Use Policy

Last updated: 2026-11-12.

Scope

Snap renders screenshots of URLs on demand: the anonymous GET /v1/screenshot endpoint, the authenticated API, the MCP endpoint, and hosted Visual CI. This policy applies to every one of those surfaces.

What you may do

Capture publicly reachable URLs you own or have permission to render and store. That includes your own QA and preview workflows, regression testing, and your own authenticated pages through Snap's documented authentication features.

What you may not do

• Circumvent access controls or anti-bot measures. A blocked target answers render_blocked — do not attempt to defeat it.
• Capture private, authenticated, or paywalled content without authorization.
• Scrape at volume through the anonymous or free endpoint: it is a demo allowance, not a bulk rendering service.
• Redistribute captures of content you have no rights to.
• Use Snap to host, store, or re-serve content, or to infringe anyone else's IP or legal rights.
• Deliberately load targets to degrade them — overload, exploit probes, or anything that harms the target.
• Misrepresent captures as human-verified.

Enforcement

Violators may be rate-limited, suspended, or have their keys revoked. Anomalous anonymous traffic is per-IP limited and may be blocked. Snap may also refuse captures that fail SSRF or abuse admission.

Abuse contact

If your page is being captured and you want it stopped, email security@i2dev.com with the URL(s). We investigate and can blocklist or refuse the target.

Security contact

Report vulnerabilities to security@i2dev.com; the process is documented on the i2dev security page.