← Back to MileMaxx
Legal

Privacy Policy

Last updated · 11 April 2026

This is the privacy policy for MileMaxx — the browser extension and the marketing website at milemaxx.com. It explains what we collect, why we collect it, who sees it, and what your rights are.

We’ve written this to match what the product actually does. If you find a gap between what this document says and what MileMaxx does in practice, email hello@milemaxx.com and we’ll fix one of the two.

1. Who “we” are

MileMaxx is an independent project run by Alex Cowan. There is no parent company. There are no investors. There is one email address you can reach us on: hello@milemaxx.com.

2. What the browser extension collects

The MileMaxx browser extension looks at one thing: the URL of the tab you’re currently on. It checks that URL against a retailer catalogue stored in the extension or cached locally in your browser to decide whether any of the shopping portals you’ve enabled cover that retailer.

It does not collect:

  • Your browsing history.
  • The contents of any page.
  • What you put in your shopping cart.
  • Your keystrokes, mouse movements, or scroll position.
  • Your credit card, payment details, or account logins.
  • Anything about tabs you don’t have focused.

The matching happens inside your browser. The URL of the shop you’re currently on is not transmitted to MileMaxx.

To keep retailer data fresh, the extension periodically downloads updated offers files from data.milemaxx.com and stores them locally in your browser. Those update checks do not include the retailer URL you’re visiting.

The extension stores your selected country and the list of portals you’ve enabled in your browser storage so it doesn’t have to ask every time you open it. It also stores the cached retailer catalogue there. We do not get a remote copy of those settings from your browser.

3. What the website (milemaxx.com) collects

When you visit milemaxx.com we don’t run third-party analytics. There is no Google Analytics, Plausible, Mixpanel, Hotjar, or similar tool. We don’t load tracking pixels.

Google Fonts

The site loads two typefaces — Inter and Fraunces — from Google’s font CDN. When your browser fetches those font files, Google receives your IP address and basic request metadata. If you’d rather not share that with Google, a browser extension such as uBlock Origin will block the request and the site will fall back to your system fonts.

Newsletter signup

If you submit the email form to subscribe to the Monthly Ledger, we store:

  • The email address you gave us.
  • Your IP address at the time of signup.
  • Your browser’s user-agent string.
  • The timestamp.
  • Which form on the site you submitted (so we know which signup path works).

We keep the IP and user-agent so that if the form is abused by bots or we spot spam signups, we can investigate. We don’t use either for targeting or profiling.

Server logs

The web server keeps standard access logs — IP address, URL requested, user-agent, timestamp, response code — for operational reasons. These rotate out after 14 days.

4. What we don’t do with any of it

We don’t sell data. We don’t share it with advertisers, data brokers, or retargeting partners. We don’t build a profile of you across sessions. We don’t feed your email address into lookalike audiences on ad platforms.

If we ever change any of this, we will say so loudly, by email, before it takes effect.

5. Where the data lives

The newsletter database and the marketing site run on infrastructure we control. Email addresses are stored in a MySQL database along with the fields described above.

We don’t currently use a third-party email service provider. When we start sending the Monthly Ledger, we may add one — and we’ll update this policy with the provider’s name before we start sending.

6. How long we keep things

  • Newsletter email addresses — until you unsubscribe or ask us to delete them. An unsubscribed row is kept for 30 days so we can tell whether an existing address is re-subscribing, then deleted.
  • IP addresses and user-agents for signups — 12 months from the date of signup, then deleted.
  • Server access logs — 14 days.
  • Extension local storage — until you uninstall the extension or clear your browser’s storage. That’s in your hands, not ours.

7. Your rights

Depending on where you live, you have legal rights over your data — for example, under the UK GDPR, the EU GDPR, or California’s CCPA/CPRA. Whatever your jurisdiction, we will honour the following requests from anyone:

  • Access — tell us your email and we’ll show you everything we have on file for it.
  • Correction — tell us what’s wrong and we’ll fix it.
  • Deletion — tell us to delete you and we will.
  • Export — we’ll send you a JSON or CSV of your data.
  • Objection — if you disagree with how we’re handling your data, you can object and we’ll stop.

To make any of these requests, email hello@milemaxx.com from the address on file. We’ll reply within 14 days.

If you’re in the UK or EU and you’re unhappy with our response, you have the right to complain to the Information Commissioner’s Office (UK) or your local data protection authority.

8. Cookies

The website sets no cookies of its own. We don’t need them: there’s no login, no session, no tracking. Your browser may cache static files (HTML, CSS, images) — that’s normal HTTP caching, not a cookie.

9. Children

MileMaxx is not aimed at children under 13, and we don’t knowingly collect data from anyone under 13. If you’re a parent or guardian and you think we have data about your child, email us and we’ll delete it.

10. Changes to this policy

When we change this policy, we’ll update the “Last updated” date at the top. For any change that affects what we collect or how we use it, we’ll give newsletter subscribers at least 14 days’ notice before the change takes effect.

11. Contact

hello@milemaxx.com is the only channel. A human reads every message.