Privacy policy
Early draft — not yet legally reviewed. Last updated: 14 July 2026.
The short version
Today, everything you save in MightBuy lives in your own browser (localStorage). We don't hold a server-side copy of your items, we don't track your browsing, and the extension only reads a page when you actively save it. When that changes (accounts and sync are planned), this policy will change first.
Who we are
MightBuy is operated by [Decision needed: legal identity — sole trader (e.g. “Chris Dykes, trading as MightBuy”) or a limited company? Include registered address]. For anything privacy-related, contact [Decision needed: contact email — e.g. privacy@ the production domain (domain itself still to be chosen)].
[Decision needed: check whether ICO registration (the UK data-protection fee) is required once real accounts launch — likely yes, ~£40/yr]
What we collect today (wireframe stage)
- Your saved items, lists, and settings— stored in your browser's localStorage only. They never leave your device. Clearing your browser data deletes them.
- Sign-in — accounts are currently simulated locally. No credentials are sent to or stored on any server.
- Add-by-URL— when you add a product by pasting a link (or saving from the extension), our server fetches that page's public metadata (title, image, price) to fill in the item. We don't store the page or the URL beyond standard, short-lived hosting logs, and we don't build any profile from it.
- Hosting logs — when deployed, our hosting provider (planned: Vercel) keeps standard request logs (IP address, user-agent, timestamps) for security and operations.
The browser extension
- Reads a page's product details only when you click save on that page. It does not read your browsing history, does not run analytics, and sends nothing to our servers.
- Stores your preferences and list names locally in your browser (extension storage).
- Never adds, modifies, or replaces affiliate links, codes, or cookies — see how MightBuy makes money.
Cookies & analytics
MightBuy currently sets no cookies — your items and settings use localStorage, which stays on your device.
- [Decision needed: analytics — none today; decide whether to add a privacy-friendly option (e.g. Vercel Analytics or Plausible, no cross-site tracking) or stay analytics-free as a trust feature]
- Affiliate cookies (planned): when affiliate links go live, clicking out to a retailer may lead the affiliate network or retailer to set cookies on their sites so the sale can be attributed to MightBuy. That happens after you leave MightBuy, on your click, and never silently in the background.
What's coming (we'll update this first)
- Accounts & sync — planned via Supabase (Postgres/auth). Your items would then be stored server-side under your account. [Decision needed: choose Supabase hosting region — UK/EU region keeps UK GDPR transfers simple]
- Price-drop alerts — would require an email address; opt-in only.
- Smarter auto-categorisation— may send an item's title/metadata (never your identity or full history) to an AI model to suggest a category. [Decision needed: choose the AI provider and confirm what item data is sent; name the provider here when live]
Shared wishlists
If you share a list, anyone with the link can see it — its name and every item on it. Don't put anything private in a shared list's name or notes. Unshare a list to withdraw it.
Your rights (UK GDPR)
You have the usual rights: access, rectification, erasure, restriction, portability, and objection. Today, exercising most of them is delightfully simple — the data is in your browser, so you can export or delete it yourself (clear the site's data). Once accounts exist, email us and we'll handle requests within one month.
You can complain to the UK Information Commissioner's Office (ico.org.uk) if you think we've mishandled your data.
Children
MightBuy isn't aimed at children. [Decision needed: set a minimum age — 13 is the UK GDPR floor for consent-based services; 16 or 18 is simpler and fine for a shopping tool]
Changes
We'll update this page as the product grows (accounts, alerts, AI categorisation) and note the date at the top. Material changes will be flagged in the app before they take effect.