Privacy
What LOWIER measures, what it stores, and what it does not.
Last updated 9 October 2026.
Draft - pending owner and legal review
The section "Controller, legal basis and your rights" below is a placeholder prepared by the LOWIER team, not a legal statement. It, and the privacy contact address, must be confirmed by the site owner and reviewed by a qualified lawyer before this page is relied on as a published privacy notice. Everything else on this page describes what the software actually does today.
Measurement we use
LOWIER is hosted on Vercel and uses Vercel Web Analytics to count page views and traffic in aggregate. That measurement is operated by Vercel as our hosting provider; what it collects, and for how long, is described in Vercel’s own privacy documentation rather than restated here.
According to Vercel’s own privacy documentation, that measurement uses no third-party cookies and identifies visitors by a hash derived from the incoming request rather than by a stored identifier; the data points it may store include the page URL, the referrer, filtered query parameters, an approximate location (country, region, city), and the device type, operating system and browser. The visitor session it derives is discarded after 24 hours.
LOWIER may also collect its own first-party interaction analytics: a small set of events recording that someone interacted with the site, opened a product, clicked through to a retailer, saved a favourite, searched, or changed a filter. These events are stored by LOWIER and are not shared with an advertising network or any other third party.
First-party interaction analytics are not necessary in order to browse LOWIER. They are intended to run only where analytics have been agreed to. Before that, no analytics identifier is created, nothing is written to your browser’s session storage for analytics, and no event is sent.
The analytics session identifier
An analytics session is labelled with an opaque random token. It is generated in your browser from random values; it is not derived from your IP address, your device, your browser or anything you have typed; and it cannot be used to recognise you on another site, on another device, or on a later visit.
The token is held in your browser’s session storage - not as a cookie, and not as a marketing identifier. Because it is not a cookie, it is never attached to ordinary requests for pages or images.
An analytics session ends at whichever of these comes first:
- 30 minutes without a recorded interaction;
- 12 hours after the session began;
- when the browser tab is closed, or the browser session ends.
A later interaction then starts a new session with a new random token. The previous one is overwritten and cannot be recovered from anything LOWIER stores.
What an analytics event can contain
- which LOWIER market you are browsing;
- the language of the page;
- the kind of page it happened on - for example "products", "product" or "deals" - rather than the full address;
- identifiers for the product, the retailer offer and the retailer involved;
- whether a favourite was added or removed;
- for a catalogue search, only how many characters were typed;
- for a filter change, the names of the filters that changed and how many are active - never the values chosen.
What is not stored
- the text of what you searched for - only its length;
- your IP address: it is not written into LOWIER’s own event records;
- your browser’s user-agent string;
- any device or browser fingerprint - no JA4 or comparable technique is used;
- your name, your e-mail address, or any account identity;
- advertising identifiers of any kind.
These events are used to count sessions and to see which products and retailers people are interested in. They are not used to build a profile of you, to target advertising, or to make an automated decision about you.
One honest caveat: like any website, LOWIER cannot be reached without your device sending its IP address to our hosting provider as part of the connection itself. What this page states is narrower - that the IP address is not written into LOWIER’s own analytics records.
How long events are kept
Raw first-party analytics events are intended to be kept for 90 days. The intention after that is to keep only aggregated counts, which are no longer tied to an individual session.
Clicks through to retailers
When you click through to a retailer, LOWIER records that a click happened, which product and offer it was for, and which retailer it went to. That is used as aggregate product analytics - which products and shops people are interested in - and in connection with affiliate reporting.
our affiliate disclosure explains how LOWIER earns from retailer links.
Controller, legal basis and your rights
Pending confirmation by the site owner and a qualified lawyer.
Who is responsible for this data as the controller, which legal basis is relied on for analytics in each market, how to request access to or deletion of data, and which supervisory authority is competent - all of this still has to be stated here. The LOWIER team has deliberately not filled it in: these are legal determinations for the site owner and their adviser, and a plausible-sounding placeholder would be worse than an acknowledged gap.
Questions
Privacy questions can be sent through our contact page, pending a dedicated privacy contact address being confirmed.