Capture policy

Capture is always explicit

The clipper captures a page only when you click save. It never captures in the background.

What is stored

When you save a page, your archive stores the page’s content and layout, the page URL and title, the time of capture, and any collection, tags, or notes you added. Captured data is sent over HTTPS and stored in your private library.

What is never captured

Every save passes three safety checks — a local blocklist in the extension, a scan of the page itself, and a server-side check that has the final say. A save is blocked when any of them matches:

• Protected sites — sign-in and identity providers (Google accounts, Microsoft, Okta, Apple ID, and similar), payment services, major banks and brokerages, and healthcare, tax, payroll, and government portals.
• Protected page types — URLs whose path indicates login, authentication, password reset, MFA/verification codes, checkout, or payment.
• Sensitive forms on the page — one-time-code fields, credit-card fields, embedded payment frames, and password fields on pages that look like sign-in screens.

When a save is blocked, the popup explains why. If the server-side safety check can’t be reached, the save is blocked and you’re asked to try again — the clipper doesn’t guess.

Scrubbing inside captures

Even on pages that are allowed, the capture is scrubbed before it leaves your browser:

• Password and hidden form fields are always emptied.
• Text you typed into inputs and text areas is cleared.
• Fields whose names suggest tokens, sessions, secrets, or keys are emptied.
• Page resources whose URLs carry credentials — access tokens, signatures, API keys — are excluded from the archive rather than fetched and stored.
• Password-manager UI injected into the page is removed from the capture.

Retention and deletion

Your captures are retained while your account is active. If your trial expires or you cancel, data is retained for 60 days and then permanently deleted — see the privacy policy for the full retention schedule and your rights.

Acceptable use

You’re responsible for having the right to save and store the content you capture, and the service can’t be used to store illegal or harmful content. The terms of service spell out the boundaries.