Permissions and acceptable use

Your own website and authorized client work

You may archive pages you own and control, including a snapshot before a redesign or a move to static hosting. For client work, obtain explicit authorization covering the domain, capture scope and intended use. Keep a record of the authorization and confirm that the person granting it can do so. Ownership of a site does not necessarily include unrestricted rights to every stock image, font, embedded video or licensed theme on it; check those licenses before moving or republishing assets.

Public pages and personal backups

Public accessibility is not a license. Archiving a public reference page for personal backup or offline reading must still be permitted by the site's terms, applicable copyright rules and other law. Keep the archive private unless you have the right to redistribute it, retain required attribution and notices, and avoid collecting personal or sensitive information. Do not assume that a personal, educational or non-commercial purpose automatically creates an exception. If the permitted use is unclear, ask the rights holder before capturing.

Uses we do not permit

Do not use captures to impersonate a person or business, mislead visitors, republish protected material without rights, distribute malware or harvest personal data. Do not bypass logins, paywalls, CAPTCHAs or other access controls, or use repeated jobs to evade source-site restrictions. Do not remove required copyright or license notices. A downloaded front end is not ownership of the source application, its brand or its content, and the service does not grant permission on behalf of a website owner.

Respect robots rules and source-site rate limits

The current worker and engine do not automatically check or enforce robots.txt, including crawl-delay. Read the site's robots.txt and terms yourself, confirm that your planned use is allowed, and select an appropriate scope before submitting. Advanced workspace controls can restrict path prefixes and, in HTTP mode, lower resource concurrency. Concurrency is not a requests-per-second or crawl-delay guarantee. Do not start a capture when a site's required rate or delay cannot be met; contact its operator for an agreed method instead. Stop if the operator objects or the site signals overload.

Network and access restrictions we enforce

Normal captures accept public HTTP(S) URLs on standard ports 80 and 443, without embedded credentials. URL and DNS checks block private networks, loopback, link-local addresses, cloud metadata endpoints and other reserved destinations. The worker checks main-document redirects and verifies engine egress isolation before dispatch; network filtering also restricts engine/browser outbound traffic. Page, depth, size, time and account-concurrency budgets remain in effect on paid plans. These safeguards are not a substitute for permission checks, and successful URL validation does not authorize a capture.

Handle downloaded material carefully

Archive and report access in the app is restricted to the capture owner. Available ZIPs have a 30-day download window after completion; keep any permitted backup in storage you control. You can delete finished captures from your account. This controls app access and app artifacts, not simultaneous erasure of all engine working copies or audit records. Inspect downloaded files before use: the static preview is sandboxed, but HTTP ZIPs can contain untrusted scripts. The tool does not capture login-protected content, server code or databases, and JS-rendered mode removes scripts rather than replaying a live app.

Report a rights concern or request removal

Use the support-ticket link below to contact the team about an allegedly unauthorized capture, copyright concern or removal request. Sign in or create an account, then open a new ticket. Include the source URLs, any capture identifier or app URL you know, the material at issue, your relationship to the rights holder, the basis of your concern and the action you are requesting. Include enough information to assess the request, but never passwords, access tokens or unnecessary personal data. Replies are available in the same ticket thread. We may request clarification; submitting a report does not itself automatically remove content.

Sign-in is required for the existing support-ticket channel. You do not need to run a capture to report a concern.