Privacy policy

Last updated: 2026-09-18. Plain description of what this service actually does with your data — no boilerplate.

Who is responsible for your data

Ghezam Capital (Ahmed & Ayoub), operating Screenshot Happy, based in Spain. Contact for any privacy request: ghezamcapital@gmail.com.

What we actually collect

• Support requests (the form at /docs#support or a direct call to POST /support): the email address and message you submit, stored so we can read and reply to it.
• API usage log: each successful call to /screenshot stores the URL you asked us to capture and the time of the request. We do not store your IP address, and this log entry is not linked to your API key or identity.
• API keys and account data: if you get a key through /docs (free tier or a paid plan), we store the key, the email you gave us, your plan, and how much of your monthly quota you've used.
• Payment and billing data (paid plans only): if you subscribe to a paid plan, payment itself is handled entirely by Stripe — we never see or store your card number. We do store the identifiers Stripe gives us to manage your subscription (customer ID, subscription ID) and its status (active, cancelled, payment failed), linked to your API key.
• Monitors (paid plans only, via /monitors): if you set up a scheduled monitor, we store the URL you're watching, the webhook URL you gave us, your check interval and change threshold, and the most recent screenshot captured for that URL (kept only to compare against the next check, not a history of past ones).

That's all. We don't run analytics, ad pixels, or any third-party tracking script on this site — see "Cookies" below.

Why we process it

To answer support requests, to operate the API you're calling (rate limiting and abuse prevention require knowing what was requested and when), and — for keys tied to an email — to manage that account. We don't use your data for advertising and we don't sell it to anyone.

How long we keep it

Honestly: there is currently no automatic deletion job. Support tickets and usage log entries are kept until deleted by request (see below) or until the operator manually clears old records. If this changes to a fixed retention period, this page will say so.

How to get your data deleted or corrected

Email ghezamcapital@gmail.com with the email address you used and what you want deleted or corrected. Today this is done manually by the operator directly in the database — there is no self-service deletion button yet.

Who else sees this data

The database is hosted with Supabase (our database sub-processor) and the service itself runs on Railway. If you subscribe to a paid plan, your payment details and billing information are processed by Stripe — see Stripe's own privacy policy for how they handle it, we never see your card details. None of these three are used for anything beyond running this service.

The Supabase project is hosted in eu-west-1 (Ireland, EU). Your account and usage data stays inside the EU/EEA. Stripe may process and store payment data outside the EU/EEA under its own safeguards — see Stripe's policy linked above.

Cookies and tracking

This site sets no cookies and loads no analytics, advertising, or tracking scripts of any kind — checked directly against the page source on 2026-09-14. Because of that, no cookie consent banner is shown. If that ever changes (an analytics tool is added, for example), this page and a cookie notice will be updated first.

Your rights

Under the GDPR you can ask to access, correct, delete, or export your data, or object to how it's used. Contact ghezamcapital@gmail.com. You can also complain to the Spanish data protection authority (AEPD) if you think we've mishandled your request.

Changes

If what this service actually does with your data changes, this page changes with it — no silent edits to what's already been described above.