Privacy information
This page describes practices confirmed in the current application code. Controller identity, legal bases, complete processor terms, and jurisdiction-specific notices require operator review before public launch.
Technical content reviewed: 2 August 2026. This is not a substitute for review by the identified service operator.
Data handled by the service
The application handles account and authentication data; product URLs and extracted product, price, and stock records; targets, tags, collections, alert settings, and notification history; plus subscription identifiers and status when billing is used.
Application purposes
These records support account access, product-page checks, price history, user-configured alerts, collections, security controls, and subscription management. No separate purpose is asserted here without an operator-approved record.
Optional audience measurement
PostHog measurement starts only after acceptance. The client sends allowlisted route templates, disables automatic capture and session recording, and excludes password-reset, shared-capability, and billing routes. Refusal and revocation stop capture.
Billing workflow
Live paid checkout is currently disabled. If billing is enabled later, the implemented workflow uses Stripe identifiers and server-verified status; public processor and transfer disclosures still require operator review before launch.
Available controls
Authenticated settings provide JSON data export and password-confirmed account deletion. The analytics control shown on every page provides accept, refuse, and revoke actions.
Retention and contact
The application contains account-lifecycle and cleanup logic, but this page does not invent a universal public retention period. Final periods, controller contact, request handling, and legal bases must be supplied and approved by the operator.