Cookie Policy

A cookie is a small file a website asks your browser to keep and send back on later visits. Browsers also give sites other storage that works much the same way. This policy covers both, on screenshotforweb.com and in the dashboard.

The first four come from our sign-in system: they’re sent only over HTTPS, and scripts on the page can’t read them. The fifth remembers a dashboard setting, and the last two are set by Stripe, our payment provider.

When you type an address into the capture box on the home page, your browser holds it in session storage, under tools:autostart, for the moment it takes to open the screenshot tool, which reads it and deletes it. We store nothing else in your browser.

No analytics, advertising, social media or tracking cookies, on the site or in the dashboard. Every cookie above is needed for something you asked for: signing in, paying, or remembering a choice you made. That’s why there’s no cookie banner.

If we ever add anything optional, such as visit statistics, we’ll ask for your consent first and list it here.

When you sign in with Google, Google’s sign-in page sets its own cookies. Stripe’s secure checkout form sets its own cookies inside the form, too. Those follow Google’s and Stripe’s cookie policies.

Your browser’s settings let you see and delete cookies, and block them. If you block ours, you won’t be able to sign in or pay, but the public pages and the free tools still work. Signing out deletes the session cookie.

When we add or change a cookie, we update this page and the date at the top. For the data behind these cookies, see the Privacy Policy.

Questions about cookies go to contact@screenshotforweb.com.