Privacy Policy
The design principle throughout: collect the minimum, keep it anonymous where possible, and let raw logs expire.
Kept with your accountEmail, a password hash or Google sign-in reference, your watchlist and alerts.
Never collectedIP addresses or device fingerprints in analytics. No third-party ad trackers in our code.
Expires on its ownRaw analytics events are deleted after ninety days; only aggregates remain.
What we store about an account
An email address, a password hash (or a Google sign-in reference), your watchlist rows, your alert definitions, and — if you connect it — a Telegram chat reference for alert delivery. That is the account.
Product analytics — anonymous by construction
Usage analytics use a random identifier that your own browser generates for itself. It is never derived from your account, never joined to it, and carries no IP address or device fingerprint. Your browser also reports its time zone so we can count visits by country; only the country is kept, never the time zone itself. Raw event rows are deleted after ninety days; only aggregates remain. Search analytics likewise store the query text and result count — not who searched.
What we do not do
We do not sell personal data, do not run third-party ad trackers in our own code paths, and do not expose individual users' searches or activity to administrators — admin reporting is aggregate-only by design.
Cookies and local storage
Local storage holds your session token when you sign in, interface preferences, and the random analytics identifier described above. No cross-site tracking cookies are set by our code.
Deletion
Deleting your account removes the account row, watchlist and alerts. Anonymous analytics rows contain nothing that maps back to you, before or after deletion.