Privacy
We would rather not know who you are. This page says exactly what that means, in the terms the database actually uses.
Last updated 30 August 2026.
The short version
- No analytics, no advertising, no third-party scripts, no tracking pixels.
- No cookie banner, because the only cookie is the one that signs you in.
- You can hold an account with no email address and no name at all.
- Nothing about you is sold, shared for advertising, or used to train anything.
- One button deletes all of it, immediately.
What we store
Everything, in the order it comes into existence. Rows marked optional exist only if you chose the thing that creates them.
| What | Why it exists | How long |
|---|---|---|
| Your email address (optional) | To send sign-in links and reminders to. Absent entirely on a passphrase account. | Until you delete the account |
| A timezone, and a display name if a sign-in provider gave us one | So a reminder says a time you recognise. | Until you delete the account |
| The hash of your passphrase (optional) | It is the account. We never hold the words themselves — they were shown to you once and not written down here. | Until you delete the account |
| Google’s opaque id for you, and the address it reported (optional) | Only if you sign in with Google, so that signing in twice is signing in once. | Until you delete the account |
| Hashes of sign-in links, and the IP address that asked for one | The hash is how a link is redeemed. The address is how one caller is stopped from mailing sign-in links at the whole internet. It is never used to decide who you are. | Deleted a week after the link expires |
| Hashes of your session cookies, and the browser string that made each one | To keep you signed in, and to let a session be revoked. | Deleted a month after the session expires |
| Which creators you follow, and any per-creator overrides | It is the product. | Until you unfollow, or delete the account |
| Your notification settings, including any Discord webhook URL you paste | To know where to send what, and when. | Until you change them, or delete the account |
| A record of each notification: which stream, which channel, when, and whether it sent | So a reminder is not sent twice, and so a failure can be retried. | Until you delete the account |
We also store public facts about creators — channel names, avatars, stream titles and start times. That is not personal data about you, and it is the same information their channel page shows to anybody.
What we do not store
No password, ever, in any form. No payment details, because there is nothing to pay. No phone number, no address, no date of birth, no real name. Nothing from your YouTube account: not your subscriptions, not your watch history, not your comments — we never ask Google for them and the sign-in scopes we request cannot return them. No advertising identifier, no fingerprint, no profile of what you clicked.
Cookies
Two, both strictly necessary, neither of them ours to sell:
- The session cookie. Set when you sign in, unreadable by JavaScript, and holding nothing but a random token. It is what makes the next page know it is you. It lasts thirty days.
- A one-shot passphrase cookie. Set for the few seconds between the request that mints a new passphrase and the page that shows it to you, and cleared by that page. It exists so a passphrase is never put in a URL, where it would end up in a browser history.
There is no analytics cookie, no advertising cookie, and no third party setting one, which is why there is no banner asking you to accept any.
Who else sees any of this
- Our email provider handles the messages we send you, and so necessarily sees your address and what the message says.
- Discord, if you give us a webhook: we post your reminders to it, and Discord sees them like any other message in that channel.
- Google, if you sign in with Google, knows you signed in to this service.
- YouTube, Twitch and Kick are asked about creators, never about you. We hold one application account with each and use it for everybody, so none of them can tell how many people follow a channel here, let alone which. We do not tell them who follows whom, and they have no way to learn it from us.
- Our hosting provider runs the machine everything sits on, as hosting providers do.
That is the entire list. Nobody buys anything from us, because we do not sell it.
Server logs
Each request writes one line: a request id, the method and path, the status code, and how long it took. Sign-in attempts that trip a rate limit also log the address they came from, because a rate limit that cannot be investigated is not one. Logs are not joined to accounts, are not analysed, and roll over.
Deleting everything
The bottom of the settings page deletes your account. It asks you to type a word first, and then it is immediate: every row in the table above goes with it. There is no grace period, no thirty-day window, and no archived copy waiting to be restored, which is also to say there is no undo.
Backups of the database are kept for operational reasons and are overwritten in the normal course of things; a deletion reaches them when the backup that predates it is rotated out.
You can see nearly all of what we hold without asking: the dashboard is who you follow, the settings page is your settings, and the history page is what we have seen. If you want the rest, or a copy in a file, ask at .
Your rights
If you are in the UK or the EU, the law gives you the right to see what we hold about you, correct it, take it elsewhere, and have it erased. The honest position is that the pages already show you nearly all of it and one button erases all of it, so most of those requests are things you can do yourself, faster than we could do them for you. For anything else, write to .
We keep what is listed above because you asked for a service that cannot work without it — there is no way to email you before a stream without an address to email — and for nothing else.
Children
This is not aimed at children and we deliberately collect nothing that would let us tell how old anybody is.
Changes to this page
If what we store changes, this page changes with it and the date at the top moves. We will not quietly start collecting something and describe it afterwards.