Privacy Policy
Last updated: July 31, 2026.
BrickPriceWatch does not require an account and does not ask visitors to submit personal information to browse set data. This policy describes the limited usage information processed when the site is visited or a retailer link is followed.
Cookies and browser storage
BrickPriceWatch does not currently set application cookies. If a visitor uses the Watchlist, the selected LEGO set numbers and display details are stored in that browser's local storage so the list remains available on a later visit. The Watchlist is not sent to BrickPriceWatch and can be cleared from the Watchlist page.
No consent banner is shown because the current application does not use advertising, personalization, or cross-site tracking cookies. If that changes, this policy and the site controls will be updated before those tools are enabled.
Aggregate retailer-click analytics
When a visitor follows a retailer link, BrickPriceWatch increments a daily aggregate containing only the date, LEGO set number, retailer, and click count. The BrickPriceWatch database does not store an IP address, browser identifier, account, or individual click history for this measurement.
These totals help rank useful retailer links and measure whether set pages lead to shopping activity. They are not used to build visitor profiles.
Cloudflare infrastructure and logs
BrickPriceWatch runs on Cloudflare Workers and D1. Cloudflare processes request information needed to deliver, secure, and operate the site, which can include IP address, request headers, device or browser information, requested URL, timestamps, and security signals. BrickPriceWatch application logs contain operational events and request status information; they are not designed as a visitor-profile database.
Retailers and external sites
Amazon, eBay, Walmart, and other external sites receive the normal request information generated when a visitor chooses to leave BrickPriceWatch. Those services control their own cookies and personal-data practices. Their privacy policies apply after the visitor reaches them. A retailer may also attribute a qualifying purchase to BrickPriceWatch when an affiliate parameter is present.
Retention
Daily aggregate retailer-click totals are retained for historical traffic comparison; no automatic deletion schedule is currently configured for those non-user-level totals. Operational and security logs are retained according to the active Cloudflare account settings. Catalog and market-source records describe LEGO products rather than site visitors.
Sharing and sale of personal information
BrickPriceWatch does not sell visitor personal information. Request data is processed by Cloudflare as the hosting and security provider, and a visitor initiates data transfer to a retailer by choosing an outbound link. BrickPriceWatch does not provide its aggregate click table to retailers as an identifiable visitor list.
Your choices and rights
Visitors can browse without an account or application cookies and can choose not to follow external retailer links. Depending on location, a visitor may have rights to request access, correction, deletion, restriction, or objection concerning personal information BrickPriceWatch controls.
Use the Contact page for a privacy request and describe the request and the jurisdiction that applies. Because BrickPriceWatch does not keep account or browser identifiers in D1, it may not hold data that can be linked back to an individual visitor.
The public privacy email will appear on the Contact page when the production address is configured.