Privacy

What this project collects — and what it doesn't

There's no legal team behind this — it's built and run by one person. So instead of boilerplate, here's a direct explanation of what data this project touches, and what it deliberately never does.

If you follow this on Telegram

Joining the Telegram channel is a normal Telegram subscription — the same relationship you'd have with any public channel. As the channel's admin, I can see who's subscribed; that's standard Telegram functionality, not something built for this project, and not something I can turn off. Other subscribers can't see each other, and the subscriber list is never exported, stored elsewhere, sold, or shared beyond what Telegram itself already provides to any channel owner. To stop, just leave or mute the channel in Telegram — there's nothing stored outside Telegram to separately delete.

If you follow this on Mastodon

Following the Mastodon account is a normal Mastodon follow — the same relationship you'd have with any public account. As the account owner, I can see who's following; that's standard Mastodon functionality, not something built for this project, and not something I can turn off. The follower list is never exported, stored elsewhere, sold, or shared beyond what Mastodon itself already provides to any account owner. Which server hosts your Mastodon account is your own choice, not this project's, and is covered by that server's own privacy policy. To stop, just unfollow — there's nothing stored outside Mastodon to separately delete.

If you use browser push alerts

Clicking "Enable Browser Alerts" creates an anonymous subscription: a randomly-issued web address and an encryption key, generated by your own browser (Chrome, Firefox, Safari, etc.) — not by this project. It carries no name, email, or account of any kind attached; there is no way for this project to identify who's behind any given subscription.

That subscription is stored in a small database (Upstash Redis, reached through Vercel) for exactly one reason: knowing where to deliver a notification. It's deleted automatically — whichever happens first: a delivery to it fails permanently (browser uninstalled, permission revoked, device gone), or it simply turns a year old, whether or not it's still working. Nothing is kept indefinitely. To stop receiving alerts sooner, disable notifications for the site in your browser's own settings; the subscription becomes invalid on our end and gets cleaned up automatically the same way.

The project's operator can also see how many subscriptions are currently stored, and clear them, through a password-protected admin page — no additional identifying detail is exposed there beyond what's already described on this page.

The website itself

Visiting balticsignalmonitor.com sets no cookies, runs no analytics, and doesn't track visitors in any way. The live numbers on the page come from your browser fetching a small public status file (status.json) — a plain file request, no different from loading an image.

Third parties this depends on

• GitHub Pages — hosts this website.
• Telegram — runs the channel described above.
• Mastodon — runs the optional account described above, hosted on whichever server you use to follow it, not by this project.
• Vercel + Upstash — host and store browser push subscriptions, exactly as described above.
• Ko-fi — the optional "Support this project" button. Ko-fi only sees anything if you choose to click through and use it; that transaction is covered by Ko-fi's own privacy policy, not this project's.

None of these get more data than what's described on this page, and this project doesn't layer any additional tracking on top of what each of them already does on its own.

Questions

This is a one-person, non-commercial project — if you have a question about anything on this page, or want something looked into, write to [email protected].