Privacy policy for Klaxon — page alerts, to phone
Klaxon — page alerts, to phone by Acid Alchamy
Klaxon posts alerts to one place: the hub address you enter in its options page. There
is no account, no backend of ours, no analytics, no crash reporting and no third-party
service of any kind.
What it reads: the text of pages you asked it to watch; the text of pages you open
yourself, but only on sites you granted and only while a keyword rule for that site is
on; whatever you send by hand from the right-click menu; and the filename, size and
source address of a download if you switch download alerts on — with the query string
removed, because that is where a presigned link or a one-time token lives and you never
saw that address in the first place.
What it transmits: one HTTP POST per alert, to your hub address and nowhere else. The
alert carries a title, a short body, the page's address, and — for a page change, a
reading item or a keyword hit — the relevant page text as an attachment.
What it stores in your browser: your settings and hub address; your hook token, under
its own key in extension storage, never displayed again and never included in an
exported configuration file; your watches, each holding up to 64 KB of the last text
read from that page so there is something to compare against; your keyword rules and
the pages they have already matched; and an activity list of the last 150 alerts. None
of it is uploaded anywhere, including to us.
Site access: none is requested at install. The extension asks for one site at a time, at
the moment you create a watch, a keyword rule or a page-problem entry for it, and you can
withdraw any of it from about:addons. A keyword rule or a page-problem site can be
scoped to every site instead, if that is what you want — you type * and confirm it, and
Firefox asks for access to all websites at that point. It is never the default and an
empty box is never read as meaning everywhere.
Cookies on watched pages: when it fetches a page you asked it to watch it uses the
session your browser already has, the same as opening the page in a tab, which is how a
page behind a login can be watched at all. It never asks for a site password and never
fills a form. Uptime checks carry no cookies.
Full policy: https://klaxonalerts.com/privacy