Privacy Policy

Version 1.0.0 · Last updated: November 2026

1. Who We Are

StockWatch is a website monitoring platform that tracks product availability, price changes, and restocks on retail websites. This privacy policy explains how we collect, use, and protect your personal data when you use our web application and Chrome browser extension.

We are based in the United Kingdom and operate under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.

StockWatch is run by a sole trader, not a limited company, and that person is the data controller. For any data subject request (access, rectification, erasure, portability, objection), contact us at the address in §12 and we will respond within the 30-day window required by UK GDPR Art. 12.

2. Data We Collect

2.1 Account Data (Essential)

When you create an account, we collect:

  • Email address
  • Display name
  • Password (stored as a bcrypt hash, never in plaintext)
  • Two-factor authentication secret if you enable 2FA (encrypted at rest with AES-256-GCM)

2.2 Service Data (Essential)

To provide our monitoring service, we process:

  • Monitor configurations (URLs, selectors, polling intervals, keyword rules)
  • Notification settings (Discord webhook URLs, recipient email addresses, push subscription endpoints)
  • Detected product data (names, prices, availability, scan history)
  • Subscription and billing data (handled via Stripe, see §6), including the reason you give if you cancel
  • Browser push subscriptions: device endpoint URL, encryption keys (p256dh, auth) and user-agent string, when you enable push notifications
  • A record of each email we send you: what kind it was, its subject, when it went and whether our email provider accepted it. Not its contents, and nothing about whether you opened it
  • IP address, user-agent, and browser characteristics on each request (for security, abuse prevention, and service delivery)

2.3 Security and Abuse Prevention Data (Legitimate Interest)

To spot account takeover, brute-force logins, one person running several accounts and other security problems, we process:

  • A browser record: a SHA-256 hash of your browser's user-agent and language setting, not your full configuration
  • A random device ID, kept in the sw_device cookie with a copy in local storage (sw_did). We use it only to keep accounts secure and to spot one person running several accounts, never for analytics or advertising
  • A description of your browser and device: how it draws a small test image and processes a short test sound (silently), its graphics chip, which common fonts are installed, its screen size, timezone, languages and number of processor cores. We store it as a keyed hash and use it for the same two things as the device ID, nothing else. It lets us recognise a device after its cookies have been cleared
  • Your email address in a normalised form (lower case, without the dots or +tags your provider ignores), so nobody can open a second account on the same inbox
  • Keyed hashes of your sign-in inbox, your alert destinations (Discord webhooks, Telegram chats and alert email addresses) and the IP addresses and browsers you use StockWatch from, along with the type of network each IP is on (home broadband, mobile, a VPN or a privacy relay), so we can tell when two accounts share them. A person reviews any match, and nothing happens to an account automatically
  • Login timestamps, IP-derived country, and any anomaly flags (new device, new country, impossible-travel)
  • Trusted-device cookies that let you skip 2FA on devices you confirm
  • A limited record of key actions in your account, such as signing up, creating monitors, reaching a plan limit and upgrading, with a timestamp and, for some, IP and user-agent. We keep these under legitimate interest and anonymise them after 90 days (see §4)

You may object to this processing under UK GDPR Art. 21, but we may need to refuse if doing so would compromise account security or our legitimate interests in preventing abuse.

2.4 Where Your Signup Came From (Legitimate Interest)

When you create an account we record how you arrived: the campaign tags on the link you clicked (utm_source and friends), the click identifier the ad platform adds to its own links (gclid from Google Ads, fbclid from Meta, and the equivalents from Microsoft, TikTok and Reddit), the site that referred you if it was not one of our own pages, and the first page you landed on. We use it to work out which channels bring real users, so we know where to spend. We also use the first page you landed on to suggest shops when you start: arrive on a Pokémon page and the Pokémon shops come first. To put shops that sell in your country ahead of the rest, we look up which country your IP address is in each time we suggest shops. We don't store that country.

We read these from the address bar and your browser's referrer at the moment you sign up. Nothing is stored on your device to collect it, so it does not depend on your cookie choices. It is kept against your account under legitimate interest, deleted when you delete your account, and included in a data export. You can object at any time under UK GDPR Art. 21 by emailing us, and we will erase it.

Invite links. Every account has its own invite link, and the share buttons on our pages add a short tag saying the link was shared. If you sign up through someone's link, including one they copied from a page's address (§2.4a), we record that you did and where the link came from. The person who shared it sees a count of how many people opened their link and how many joined, and gets a notification when someone joins, once the new account has confirmed its email. They are never told who you are. When a link is opened we count it, with the page it opened and where the link came from, without storing anything about the person who opened it (the network address is held in memory for twelve hours so one person is not counted twice, then dropped). We also record when the share buttons and the invite card are used: which button, on which page, whether it went out, and your account if you are signed in. That tells us which of them people actually use. Same basis and same rights as above, and your own records are in your data export.

Invite rewards. While they are running (terms §4a), we check whether a friend who joined through your link has set up alerts that can reach them, and before giving either of you a reward we check the two accounts don't look like the same person, using the records described in §2.3. That check is only used to decide the reward: it never changes anything else about either account.

Changed your mind? You can turn analytics and marketing on or off whenever you like. Switching something off stops it immediately and clears what it stored.

2.4a Anonymous Visitor Tracking (Requires Analytics Consent)

If you accept analytics cookies, we also set a one-year visitor cookie (sw_vid) and keep a Visitor record: campaign tags, referrer, landing page, device/browser/OS, IP-derived country and the pages you view. This lets us follow a visit across days and, if you later register, connect the browsing you did beforehand to your account.

Links you pass on. With analytics on, the address of our public pages (such as the home page, the guides, the Pokemon pages and help) carries a short tag, like ?sw=K7QX2MR. Each page you open gets a new one, kept with that page view. If you copy the address or share the page and someone else opens it, we count the open against your tag, and if they sign up we record that they came through a link you passed on. If you have an account, those opens and joins count on your invite card the same as your invite link, and you get the same notification when someone joins. For the person who opens your link we follow §2.4 and store nothing about them. Opening your own link again, from a bookmark or a reload, doesn't count.

Decline analytics and none of this happens: no visitor cookie is set, no first-touch record is written to your browser's local storage, no page views are stored and our pages carry no tag. We keep only the signup record described in §2.4 above.

If you accept analytics and then create an account, we also store the identifier Google Analytics gave your browser (client_id) against that account, and report the sign-up and any subscription payment to Google Analytics from our server rather than from your browser. It is the same measurement you already consented to and no extra information about you is sent: the identifier is what lets those two events join the visit they came from instead of appearing as a stranger. Decline analytics and there is no identifier, so nothing is sent.

While you are signed in, we also send Google Analytics your account ID and the plan you are on. That ID is the random string your account already uses internally, not your name or your email address, and it is what lets the same person browsing on a laptop and on a phone count once rather than twice. We clear it when you log out. Decline analytics and none of this is sent.

2.5 Analytics Data (Requires Consent)

With your consent, we collect:

  • Page views and feature usage within StockWatch
  • Session duration and navigation patterns
  • Device type, browser, and operating system
  • Approximate location (country-level, derived from IP)
  • Performance metrics (page load times)
  • Email engagement — a 1×1 tracking pixel and link-tracking redirects in outbound emails, our marketing emails included if you get them (§2.8), so we can measure delivery and click-through
  • Push alert engagement: when an alert we push to your phone or browser appears, whether you tap it, and which shop it was for
  • Your answers to "Did you get one?": after you tap a restock alert we pushed to your phone or browser, StockWatch may ask whether you got the product. We keep your answer, the reason you pick if you missed it (or that you closed the question), which product and shop the alert was for, and when the alert was sent and tapped and the question shown, so we can see whether our alerts reach people in time. We ask about one alert a week at most, only inside StockWatch, never by push or email. If you withdraw this consent, we delete these answers

Separately, and whatever you choose here, we count clicks from StockWatch to other sites. When you tap a push alert, or click a link to a shop on one of our pages, we add one to that day's total for that shop and that part of StockWatch. The count is sent without cookies, and we keep nothing that could tell us who clicked: no account, no address, no device. It tells us which shops our alerts and guides send people to.

2.6 Marketing Data (Requires Consent)

With your consent, we collect:

  • Campaign attribution data (UTM parameters) linked to your account
  • Referral source information, including whose invite link you joined through (§2.4)
  • Usage patterns for personalisation and segmentation

2.7 The Chrome Extension

If you install the StockWatch Chrome extension, it sends us:

  • When you save a monitor with the picker: the address and title of that page, which parts of it you picked, and what each of those parts said at the time. We keep that so the monitor can find the same part again if the shop changes its page.
  • When a monitor runs in your own browser: the HTML of the page you chose to watch, whenever what you picked changes and at least every ten minutes. The page is sent as your browser sees it. If you are signed in to that shop, it can include what the shop shows you there, such as your name or what is in your basket.
  • With every request: the sign-in token that tells us which account it is.

It sends nothing from any other page you visit, and it does not collect usage statistics. Versions before 2.19 could send feature-usage events if you had switched that on. That switch has been removed.

2.8 Emails From StockWatch (Requires Your Consent)

Besides your alerts and account emails, we only send marketing emails to people who say yes: by ticking the box when you sign up, by switching them on in Settings, or by saying yes when StockWatch asks on your Dashboard. The box is never ticked for you, it isn't part of signing up, and StockWatch works the same whether you get them or not. We never email you to ask.

What you get is what the words you agreed to said. Today they cover the StockWatch weekly, a round-up built around what you watch that can include the odd offer on our plans; up to five tips in your first two weeks while you're getting set up; and, if you pay, two emails on making the most of your plan. We never send more than three in any seven days, the weekly included. If you agreed to our earlier wording, which named only the weekly, that is all you get until you say yes to the rest in Settings. If you said yes on the morning of 2 November 2026, the words you saw also named the odd email when something launches, so you may get those too, within the same three in any seven days.

To build them around you, we use your name, your plan, when you joined and the monitors you've set up: the shops and products they follow and what they've found. That happens inside StockWatch, and nothing about you goes to anyone else to make them.

When you start paying, we also send one email about what your plan gives you and how to use it. That is part of the service you paid for, not marketing, so it comes whatever you choose here.

To run the welcome and plan emails, we keep a record of each series you're in: when you joined it, each step, what we sent, and when and why it stopped. It's in your data export and deleted with your account. We use it to send these emails and to fix them, nothing else.

Each time you switch them on or off, we keep a record of when, where you did it (signup, Settings, the Dashboard, an unsubscribe link, or us acting on your request), the version of the wording you were shown, the IP address and browser you used, and a one-way hash of your email address. That record is how we can show you agreed, as UK GDPR asks of us. When StockWatch asks on your Dashboard, we also note that it was shown, which wording, the kind of device (phone, tablet or computer) and whether you said yes or closed it, so we know how often to ask and which wording works. We keep that for a year.

Stopping them takes one click: the unsubscribe link at the bottom of every one, which works without signing in, your mail app's own unsubscribe button, or the switch in Settings. It stops all of them at once. It doesn't touch your alerts, and turning off alert emails doesn't stop these: they are separate. If you report one of our emails as spam, we stop these too.

If you've allowed analytics (§2.5), we see whether they're opened and which links are tapped. If you haven't, we don't track them at all.

2.9 Testing Changes to the Site and Our Emails

Now and then we show people two versions of a page, an email or a prompt to see which works better: which wording helps more people set up their first monitor, say. If you're signed in, our server picks your version from your account and nothing is stored on your device. If you're not signed in, you're only included if you've allowed analytics cookies, and we use the visitor cookie analytics already sets. We record which version you saw, then count what happened next from records we already keep, such as whether you signed up, set up a monitor or unsubscribed. Reports only ever show totals, never names. We never test prices or alerts. If a test shows you a different wording when we ask about our emails, the version you saw is the one your consent record keeps. We do this under legitimate interests (making StockWatch work better). You can object at any time by emailing us and we'll leave you out of every test. Which tests you were in is part of your data export, and it is deleted with your account.

2.10 The Draws and Invites Page

On the draws and invites page you can keep your own record of each draw or invitation: that you saved it, entered it or asked for it, won it and when the win runs out, bought it or missed it. We keep that record, your switch for new draw alerts, and your switch for Amazon round reminders, with the time you turned the reminders off if you did.

We use the record to send you the reminders it asks for: before a draw you saved closes, before a win runs out, and, if you've asked Amazon for an invitation, an email when a new round of Amazon invitations is going out, so you can check whether you've been invited to buy anything. The first two go to the bell, as a push, and to the email and Discord your alerts use; the Amazon one is an email to your alert address. None of them carries an offer or advertising.

You can stop Amazon round reminders in one click: the unsubscribe link in each one (it works without signing in), your mail app's own unsubscribe button, or the switch on the page. Stopping them doesn't touch your new draw alerts or any other alert, and the page the link opens lets you switch either one back on. The record is in your data export and deleted with your account.

3. Lawful Basis for Processing

Data CategoryLawful Basis
Account & Service DataContract performance
Subscription & Billing (Stripe)Contract performance + legal obligation (UK tax records)
Security, Abuse Prevention & Device RecordsLegitimate interest
Signup Source (§2.4)Legitimate interest
Anonymous Visitor Tracking (§2.4a)Consent
AnalyticsConsent (opt-in)
Marketing & SegmentationConsent (opt-in)
Emails From StockWatch (§2.8)Consent (opt-in). Keeping the record of your choice: legal obligation, so we can show you agreed
The email when you start paying (§2.8)Contract performance
Testing Changes (§2.9)Legitimate interest
The Draws and Invites Page (§2.10)Contract performance. Amazon round reminders: legitimate interest (helping you get the invitation you asked for), and you can stop them in one click
Extension TelemetryConsent (opt-in)

4. Data Retention

  • Account data: Retained until you delete your account. Aggregated, anonymised behavioural records (with all user identifiers removed) survive deletion for product analytics.
  • Monitor events (restock / price-drop / error alerts), the record of emails we sent you, whether our push alerts were seen and tapped, and what you told us about them: retained for 90 days by default, then automatically deleted. Aggregated product price history is retained for up to 12 months for trend charts.
  • Activity and session logs: identifying fields (IP, user-agent) are removed at 90 days; the anonymised behavioural rows are deleted at 180 days.
  • Consent records: retained for audit purposes for as long as you have an account, and for 24 months after deletion for legal-defence purposes.
  • Emails from StockWatch (§2.8): whether you get them, and the record of each time you switched them on or off, are kept while you have an account. If you delete your account, we remove your account ID, IP address and browser from that record and keep the rest (what changed, when, where, the wording version and the hash of your email address) for 24 months, only to answer a complaint or a legal claim, and then delete it. We don't keep your address on a do-not-email list, because a new account always starts with them off. The note of each time we asked on your Dashboard is kept for a year, and the record of each email series you were in until you delete your account.
  • Tests (§2.9): which version of each test you saw is kept while you have an account, and deleted with it.
  • Billing records: our payment processor Stripe and our own subscription event log may retain records for up to 6 years after your last payment, to comply with UK HMRC tax and accounting law. The Stripe customer record retains the email and name you registered with for the same reason.
  • Account-sharing checks: we delete IP address and browser hashes 90 days after we last saw them. We keep the device ID, the inbox and alert destination hashes, and any review of whether two accounts belong to one person, until either account is deleted.
  • Push subscriptions and trusted-device cookies: deleted when you revoke them, when the device unsubscribes, or when you delete your account.

Every outbound notification email includes a one-click unsubscribe link (RFC 8058). You can also disable all email globally from your notification settings. Our marketing emails have their own one-click unsubscribe, which stops them and nothing else.

5. Your Rights

Under UK GDPR, you have the right to:

  • Access your personal data (download via Account settings)
  • Rectify inaccurate data (edit your profile)
  • Erase your data (delete your account)
  • Restrict processing (adjust consent preferences)
  • Data portability (export your data as JSON)
  • Object to processing based on legitimate interest
  • Withdraw consent at any time without affecting prior processing

You can exercise these rights from your Account settings, or by emailing us at the address in §12. DSAR responses are returned within 30 days.

6. Third-Party Processors

We share data with the following processors, each under a Data Processing Agreement:

  • Stripe (US/EU): Payment processing, subscription management, invoice history (PCI DSS compliant)
  • Resend (US): Transactional and notification email delivery, our marketing emails if you get them, plus bounce/complaint webhooks
  • Cloudflare (UK/US, EU bucket for backups): Turnstile bot-protection on signup/login forms (sends your IP and a challenge token), DNS routing, and EU-region R2 storage for our nightly off-site database backups
  • Sentry (US): Server and browser error / performance telemetry. We strip credentials and request bodies before transmission; the URL path, browser user-agent, and your StockWatch user ID may be transmitted to support debugging
  • ImprovMX (US): Inbound email forwarding for our @stock-watch.co.uk addresses
  • Browser push services (Mozilla autopush, Google FCM, Apple APNs): when you enable push notifications, your subscription endpoint identifies the vendor whose servers relay each notification to your device
  • Discord and Telegram: only when YOU configure a webhook URL or chat ID. We send the notification content you opted in to

We do not sell your personal data to third parties.

6.1 Analytics and Marketing Processors (consent-gated)

The following processors only receive data when you have given the matching consent on our cookie banner (Analytics or Marketing). They never load if you decline.

  • Google Analytics 4 (Google LLC, US) — Analytics consent. Site usage stats (pages viewed, session duration, traffic source), plus your account ID and plan while you are signed in. IP anonymisation is enabled. Google's privacy policy: policies.google.com/privacy
  • Microsoft Clarity (Microsoft Corporation, US) — Analytics consent. Aggregated heatmaps and anonymised session recordings to help us see where the product is confusing. Microsoft's privacy statement: privacy.microsoft.com
  • Google Tag Manager (Google LLC, US) — Analytics consent. Container that lets us update tags without redeploying. No tracking of its own. Same policy link as Google above.
  • Meta Pixel (Meta Platforms Ireland Ltd) — Marketing consent. Lets us measure the success of Facebook and Instagram advertising and build audiences. Meta's privacy policy: facebook.com/privacy/policy
  • TikTok Pixel (TikTok Information Technologies UK Ltd, with parent companies in US/Singapore) — Marketing consent. Same purpose as Meta Pixel for TikTok advertising. TikTok's privacy policy: tiktok.com/legal/privacy-policy

You can change your consent at any time from the cookie banner (click “Cookie preferences” in the footer) or from your account settings. Revoking consent stops these processors and clears their cookies on your next page load.

7. Data Security

  • Passwords hashed with bcrypt (12 salt rounds)
  • Two-factor authentication secrets and recovery codes are encrypted (AES-256-GCM) and hashed (SHA-256) respectively before storage
  • Proxy credentials encrypted with AES-256-GCM
  • JWT tokens with httpOnly, secure, sameSite cookies
  • CSRF protection on all state-changing requests
  • Rate limiting on authentication, account-deletion, and password-change endpoints
  • Account lockout after repeated failed login attempts
  • Webhook endpoints (Stripe, Resend) verify HMAC signatures on every request

8. Chrome Extension

The extension asks Chrome for access to all websites. It needs that for two things and uses it for nothing else: to put the picker on a page when you click Pick something to watch, and to open the pages of monitors you have set to run in your browser, in a minimised window, so it can check them. It does not run on, read or record any other page. What it sends us is listed in §2.7.

We use what the extension sends only to run the monitors you set up and to alert you. We do not sell it, we do not use it for advertising, and we do not use it to judge creditworthiness. Nobody at StockWatch reads a page your browser sent unless you ask us to look into a problem with that monitor, or we need to for security or because the law requires it.

The use of information received from the StockWatch Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

9. Cookies and Local Storage

NamePurposeCategory
tokenAuthentication session (JWT)Essential
sw_session30-min session linkage for behavioural continuityEssential
sw_vid1-year anonymous visitor tracking (see §2.4a). Only set if you accept analytics.Analytics
sw_deviceRandom device ID, used only for account security and to spot one person running several accounts. Never used for analytics or advertising. 1 year.Essential
sw_trusted_device30-day 2FA-bypass for devices you confirmEssential
_ga, _ga_*, _gidGoogle Analytics 4 (anonymised usage stats). 2 years.Analytics
_clck, _clsk, CLIDMicrosoft Clarity (aggregated heatmaps, anonymised session recordings). 1 year.Analytics
_fbp, _fbcMeta Pixel (advertising measurement). 90 days.Marketing
_ttpTikTok Pixel (advertising measurement). 13 months.Marketing

We also use browser local storage: stockwatch_consent holds your privacy preferences (essential), and, only if you accept analytics, sw_first_touch remembers how you first arrived so the attribution survives between visits. Declining analytics, or withdrawing it later, removes sw_first_touch. sw_did holds the copy of your device ID described in §2.3 (essential). After you sign in, your browser sends it to us with the device description, and sw_dr: entries record when it last did.sw_signed_in remembers that this browser is signed in, so a page that opens while our servers are busy waits for them instead of showing the sign-in form. Signing out removes it (essential). Apart from sw_did, local storage is never sent with HTTP requests and stays in your browser.

10. International Data Transfers

Your account data is stored on servers in Germany (Hetzner) with encrypted off-site backups in the EU (Cloudflare R2). Some of our processors (Sentry, Resend, ImprovMX, Stripe, plus the analytics and marketing tags in §6.1 if you have consented to them: Google Analytics 4, Microsoft Clarity, Meta Pixel and TikTok Pixel) may process data outside the UK / EEA under Standard Contractual Clauses, the UK International Data Transfer Addendum, or equivalent safeguards. We rely on those providers' published transfer mechanisms; their current locations are listed in §6 and §6.1.

11. Changes to This Policy

When we change this policy, we update the date at the top. If a change affects something you have already agreed to, such as the cookies you allowed, we ask you again with the consent banner. Anything new that needs your consent is asked for on its own, the first time you meet it, as our emails are (§2.8): it doesn't start until you say yes.

12. Contact

For privacy-related queries, data requests, or complaints, please contact us at privacy@stock-watch.co.uk. We aim to respond to data subject requests within 30 days, as required by UK GDPR Art. 12.

You also have the right to lodge a complaint with the Information Commissioner's Office (ICO), the UK's independent data protection regulator (tel. 0303 123 1113).