Legal

Privacy Policy

What we collect when you use Screenshot for Web, why we collect it, who helps us run the service, how long we keep each thing, and the rights you have over it.

Operated by HYDRANODE LTD · Last updated 16 October 2026

01Who we are and what this covers

Screenshot for Web (screenshotforweb.com) is run by HYDRANODE LTD, a company registered in England and Wales (company number 15672526), whose registered office is at 124 City Road, London, London, England, EC1V 2NX. In this policy, “we” and “us” mean HYDRANODE LTD.

This policy covers the website, the dashboard, the API, the free tools and our emails. For your account, billing and usage data, we are the data controller. For the content of the pages you capture, see the pages you capture.

02What we collect

  • Account details: your name and email address, whether you’ve confirmed it, and a bcrypt hash of your password if you set one. If you sign in with Google: your Google account’s identifier, your profile picture, and the sign-in tokens Google issues.
  • Plan and billing: your plan, its renewal date, and Stripe’s references to you and your subscription. Stripe holds your card and billing details; we don’t.
  • API keys: a SHA-256 hash of each key, its first characters and last four, its name, and when it was created, last used and revoked.
  • Usage records: for each capture or job, the address captured, the kind of capture, the format, how many screenshots it counted as, and the time.
  • What you send us to capture: addresses and options, including any HTML, JavaScript or CSS you send, webhook addresses and secrets, monitor settings (the address, the schedule and an alert email), and prompts for AI analysis.
  • Captures: the images and PDFs we make for you, monitor images and the differences between them, and website-history images.
  • Free tools: the address you enter, and counters keyed by your IP address (for IPv6, its /64 network) that limit how many captures each visitor makes. The image goes back to your browser and isn’t stored.
  • Server logs: for each request, your IP address, your browser’s user agent, the address requested with its query string, and the time; for each capture, the address captured; and when a capture fails, its main options, such as the format and device. API keys, signatures, download links, credentials in addresses (such as passwords and tokens) and webhook addresses are blanked out, and any HTML, scripts, styles or prompts you send are left out.
  • Sign-in counters: counts of wrong passwords, wrong sign-in codes and sign-in emails, kept against the email address and your network (your IP address, or for IPv6 its /64 network), so passwords can’t be guessed at speed.
  • Emails we send you: email confirmation, password reset, subscription and payment notices, and the monitor alerts you set up.
  • Messages you send us, and what we need to answer them.
  • Cookies that keep you signed in: see the Cookie Policy.

03What we don’t collect

  • No card numbers: they go to Stripe.
  • No analytics, advertising or social media trackers, on the site or in the dashboard.
  • No selling or renting of your data, ever, and no profiling.
  • We don’t use your captures or what you send us to train AI models.

04How we use it

  • To run the service: sign you in, make and deliver your captures, run your jobs and monitors, and count your usage against your plan.
  • To bill you, through Stripe, and to keep the records the law requires.
  • To keep the service safe and working: limiting requests, stopping abuse, and finding and fixing faults.
  • To answer you when you write to us.
  • To send the emails the service needs: confirmation, reset, subscription and payment notices, and the monitor alerts you ask for. We don’t send newsletters or marketing.

06The pages you capture

When you ask for a capture, our browser visits the address you give and records what it shows. Pages can contain personal data about other people. You decide what to capture and why, so you need a lawful reason to capture and use it, and for that content we act on your instructions.

We use captures only to deliver them to you, and we don’t publish them. Identical requests can share a capture held in our storage or cache, because the result is the same.

07Who we share data with

These companies help us run the service, each only for its part:

Who
OVH Ltd
What for
Runs our servers, in London (United Kingdom)
What they receive
Everything we hold except stored captures
Who
Google Cloud
What for
Stores captures: images, PDFs, batch files and monitor images
What they receive
Captures and their file names
Who
Stripe
What for
Payments, subscriptions, tax and invoices
What they receive
Your name, email address, card and billing details, and your plan
Who
Resend
What for
Sends our emails
What they receive
Your email address and the email itself
Who
Google
What for
“Continue with Google” sign-in, if you use it
What they receive
What you agree to share at sign-in: your name, email address and profile picture
Who
OpenRouter
What for
AI analysis, only when you ask for it. OpenRouter passes the request to the company that hosts the model.
What they receive
The captured image and your prompt, but not your account details or the page's address
Who
Internet Archive
What for
Website history: past copies of pages come from its Wayback Machine
What they receive
The address you ask about. The free history tool asks it straight from your browser.

We also disclose data when the law requires it, and if HYDRANODE LTD or Screenshot for Web is sold or merged, your data would pass to the new owner under this policy.

08International transfers

Our servers are in the United Kingdom. Google Cloud, Stripe, Resend, OpenRouter and the Internet Archive may process data in the United States and other countries. Where they do, the transfer relies on UK adequacy regulations (such as the UK extension to the EU–US Data Privacy Framework) or on standard contractual clauses that these companies provide.

09How long we keep things

Data
Account details, plan and Stripe references
How long
While your account is open; deleted within a month of you asking us to close it
Data
API keys (hashes, first characters, last four, names, dates)
How long
While your account is open, revoked keys included
Data
Usage records (the address captured, the kind of capture, format, time)
How long
While your account is open: they drive your usage page and quotas
Data
Batch and website-history jobs, and monitor settings
How long
While your account is open, or until you delete the monitor
Data
Screenshots and batch files made through the API
How long
30 days from when they were made
Data
Monitor images and the differences between them
How long
Until you close your account
Data
Website-history images
How long
Kept, because they show public archived pages and are reused for anyone who asks for the same site and period; they aren't stored against your account
Data
Captures in our short-term cache
How long
One hour, or up to 24 hours if you set cacheTtl
Data
AI analysis results
How long
7 days, so repeating a request isn't charged twice
Data
Free tool counters (by IP address)
How long
Within a day of your last capture
Data
Sign-in counters (by email address and network)
How long
15 minutes for wrong passwords and codes, an hour for emails
Data
Server logs
How long
Rotated and overwritten as new logs arrive, and cleared whenever we update the service
Data
Email confirmation and password-reset links
How long
Expire after one hour
Data
Invoices and payment records
How long
As long as tax law requires (six years in the UK)
Data
Messages you send us
How long
As long as we need them to help you and to keep a record of what we agreed

10Your rights

You can ask us to:

  • give you a copy of your data;
  • correct it;
  • delete it, including closing your account;
  • restrict how we use it;
  • send it to you, or to someone else, in a common format;
  • stop using it where we rely on legitimate interests.

Write to contact@screenshotforweb.com from the email address on your account. We answer within one month. If you’re unhappy with how we handle your data, you can complain to the UK’s Information Commissioner’s Office (ico.org.uk) or, in the EU, to your local data protection authority. We honour the rights that other privacy laws give you where they apply.

11Children

Screenshot for Web isn’t meant for children, and you must be 16 or older to use it. If we learn that a child has an account, we delete it.

12Changes to this policy

When this policy changes, we update the date at the top. If a change matters, we also say so on the site or by email before it takes effect.

  • 16 October 2026: first published.

13Contact

Questions about privacy, and requests about your data, go to contact@screenshotforweb.com.