Privacy: what we store, and what we do not
What reaches our servers, who else gets to see it, how long it stays, and how to get rid of it.
What we collect
An email address, because an alert has to go somewhere. A username is generated from it. A first and last name are optional and stay empty unless you fill them in.
Your password is never stored. What we keep is a salted hash of it, with a salt unique to your account. We cannot read your password, recover it, or tell it to you.
From ordinary use we keep your IP address, used for rate limiting and abuse detection, and the identification string your browser sends, recorded alongside the session. We also keep sign-in timestamps, the products you track, the countries you track them in, the alerts you configure, and anything you write to us in a support ticket.
Opening an account does not require a phone number, a postal address or a date of birth. There are no such fields on your user record.
Where your alerts go
A recipient is the destination of an alert, and what we store depends on the kind. For email, the address. For Slack, the delivery URL your workspace issues, which we show back to you masked. For WhatsApp, your phone number, normalised to international format. For Telegram, the numeric chat identifier the bot is given.
Delivering a message means handing it to somebody else. Slack and Telegram receive the message and its destination. WhatsApp messages go through Twilio, which receives your phone number. Email leaves through our mail provider.
Every delivery attempt is logged so you can see why a message did not arrive: provider, status code, latency. For email that log holds the address the message was sent to. For Slack, WhatsApp and Telegram it holds only an internal recipient reference, never the value itself.
Payments and invoices
Card details never touch our servers. Stripe and PayPal handle the payment; we receive a transaction reference, an amount, a currency and a status.
Invoices carry more, because an invoice needs an identity. If you supply one, we store the billing name, address, city, state or province, postal code, country and tax identifier you entered, along with the line items.
The credit ledger records every credit added or spent, including a short note of which product and country a credit was spent on.
What we do with it, and what we do not
We use it to run the service: check prices, send the alerts you asked for, keep your account working, answer support tickets, and send verification and password-reset messages.
We use it for security: rate limiting, detecting abuse, and slowing down repeated failed sign-ins.
We do not sell, rent or trade personal information. Your IP address is not shared with anyone for advertising. Apart from the payment processors and message providers named above, and the infrastructure that hosts and serves the site, we hand your data to no one else unless the law requires it or someone's safety is at stake.
Your data may be processed outside the country you live in.
Cookies, tracking and third parties
This site sets no cookies of its own. It runs no analytics. It makes no request to any third party — the fonts are served from our own domain, and the content security policy blocks the rest.
The only thing kept in your browser here is one entry recording whether you chose the light theme, the dark one, or your system setting. It holds one of three words. It is not an identifier.
When you arrive at the front page we read, once, the language your browser advertises, to decide whether to send you to the Spanish version. That is a header your browser sends with every request; we do not store it.
The app is different because you are signed in there: your session tokens, your account record and your interface preferences live in your browser's local storage rather than in cookies. Signing out clears the tokens and the account record.
How long we keep it, and how to delete it
You can delete your account yourself from account settings. It is a hard delete: your user record, sessions, API keys, tracked products, alerts, recipients, verification tokens, invoices, payment transactions and credit ledger are all removed.
Recorded price history stays. It describes products rather than people, and it is what makes the public product pages work; it comes from publicly available Amazon product pages, and we are not affiliated with, endorsed by, or sponsored by Amazon.com, Inc.
Two things about you survive the delete. The delivery log does, and for email it holds the address a message went to. Support tickets do too: the ticket, its messages and the email address on them stay, detached from the deleted account. Neither is pruned automatically today, and we would rather say that than imply otherwise.
A signed-in session expires on a clock set when you sign in — a short one by default, a longer one if you asked to stay signed in. Rate-limiting records expire within minutes. Changing your password ends every active session at once.
Your rights, and how to use them
You can ask for a copy of your data, ask us to correct it, ask us to delete it, or opt out of email that is not an alert you configured yourself. There is no self-service export button: write to [email protected] or open a support ticket, and a person will do it.
Deleting your account is the exception: it is a button in account settings and it takes effect immediately.
The service is not for anyone under 18, and we do not knowingly collect data from children.
If this page changes in a way that matters, we tell you by email or with a notice inside the app.