Privacy

The anonymous watchlist uses a random browser identifier stored in an HTTP-only cookie. The server associates that identifier with the subscription products, storefronts and target prices you choose. It does not require a name or account.

Clearing this site's browser data removes your browser's access to that watchlist. Current in-app alerts are shown only through the same browser identifier.

The site counts visits to canonical public page paths so frequently used App datasets can be refreshed first. Each Redis record contains only a date, a normalized path and an aggregate count. Query strings, IP addresses, User-Agent strings, referrers, visitor identifiers and event-level timestamps are not stored in this dataset.

Daily aggregates expire after 45 days and scheduling uses at most the latest 28 days. The counter sets no analytics cookie, does not attempt to recognize a returning visitor, ignores known automated clients, and does not send an event when the browser exposes Do Not Track or Global Privacy Control.

The hosting system may retain bounded request, health and error logs needed to keep the service secure and diagnose failures. Application logs are designed not to include secret credentials or raw protected notification destinations.

The current public site does not enable third-party behavioral analytics, advertising trackers or advertising cookies.

Email, Telegram and Web Push delivery are not currently active. Before email alerts are enabled, the site will require explicit consent and verification. The prepared email design encrypts the destination and stores a separate keyed hash for matching; unsubscribing erases the encrypted destination.

Links to Apple and App publishers take you to their services, which apply their own privacy notices. This page will be revised when the site adds a public contact channel, third-party analytics, advertising, user accounts or materially different processing.