Privacy, terms, and the small print.
The short version, written to be read. No cookie banners here, because there is nothing to consent to.
Privacy
The software collects nothing. It runs on your machines, reads the metadata of your SSH key files, and never opens a network connection. There is no telemetry, no crash reporting, no phone-home. Your keys, your events and your baselines never reach us, because there is no channel that could carry them.
This site tracks nothing. It is a static page. No cookies, no analytics, no third-party requests; the fonts are served from this site too. If we ever add privacy-respecting analytics, this page will say so before it happens.
Email works like email. If you write to us, we reply from a human mailbox. Correspondence is kept for support history and never sold, shared, or mined.
What a hosted fleet view may receive
Nothing above changes when you license the software: the engine and the CLI you download are the same binary, and they still open no sockets. A fleet view is a separate component that you run, next to your machines, and it is the only thing that could ever send anything anywhere.
It is opt-in per machine, and it can be self-hosted. Pointed at your own infrastructure, nothing reaches us at all. If you prefer our hosting, this is the complete list of what leaves your machines, and a field can only be added to it with the 90 days' notice the licence promises:
-
Sent: key kind, algorithm, key size in
bits, the
ssh-keygen -lf-compatible fingerprint, octal file permissions, the insecure-permission flag, the@revoked/@cert-authoritymarker, and a timestamp. -
Sent only if you switch it on: the
authorized_keysoption prefix (who may log in from where), theknown_hostshost list, and the key comment. - Never sent: your file paths (you label each machine instead), the content hash of any file, and key blobs of any kind. To be precise about the last one: a fingerprint is derived from a public key and is sent, because a fleet view cannot tell a swap from an addition without it; the key blob itself stays on your machine, and nothing derived from the secret half of a private key is ever emitted at all.
A fingerprint identifies a key, not a person, and it is the one field the product cannot work without: without it a fleet view cannot tell a swap from an addition. Everything else in the list above exists so the change is legible when it arrives.
Terms of the licence
The binding text is the
licence that ships with every release, as LICENSE.txt beside the binaries and
inside every archive. This page summarises it in plain
language; where the two differ, the licence wins.
- What you buy: a commercial licence for the ssh-key-monitor engine and CLI, for your whole organisation, at one flat annual price. It covers any number of machines and any number of engineers, and every update released during an active term is included.
- What we do not count: machines, keys, scans, events, or people. Paid use is self-certified. The engine opens no network connection and contains no licence check, so there is nothing to meter even if we wanted to.
- Free tier: free forever, with no machine limit, for individuals (including sole traders), open source, and education and research.
- Evaluation: any organisation may request 60 days of evaluation before paying, extended on request. No card, no forms.
- Founder band: the first ten paid organisations keep the founder price for as long as their licence stays continuously active.
- Existing customers: anyone who licensed under the earlier per-machine model keeps the terms they paid for until renewal, and may move to the founder band at renewal if a place is left.
- Changes: at least 90 days' notice before any licence change takes effect, and a release you have already downloaded keeps the licence it shipped with, permanently.
- Onboarding: a fixed-scope thirty-day engagement is $1,200, agreed in writing before it starts, and credited in full against the first annual licence if you buy within 60 days. What it covers, and what we never ask for, is described on the pricing page.
- Running it for others: offering the software to third parties as a service, or bundling it into a product you distribute, needs a separate OEM or hosting agreement. Ask first; it is a short conversation.
- Billing and taxes: payments, invoicing, and VAT or sales tax are handled by our merchant of record at checkout. We never see your card.
- Refunds: within 30 days of purchase, one email gets you a full refund. No forms, no interrogation.
- No warranty: the software is provided as is. It is a detection tool: it tells you what changed, and a quiet scan is not a guarantee that nothing changed. Run the baseline diff on a schedule; that part is yours.
- Liability: capped at what you paid us in the twelve months before a claim. We are engineers, not an insurance company.
Which licence version governs what
The current licence is version 1.0,
effective 2026-10-28. Every release states the version it
ships under, in its own LICENSE.txt and on its
download page, and that version governs that release
permanently: a newer licence applies to releases published
after it takes effect, never to a build you already have.
The served text is always the newest one at
/licence.txt, and it is byte-identical to the copy inside each release
it belongs to — checked mechanically, not promised.
Verify what you are running
Trust claims are worth what you can check. Every release publishes a CycloneDX SBOM, the exact non-dev dependency tree the binary was built from, the licence text, and a minisign signature for each artefact. You can therefore confirm that the binary has no network client in it before you run it once, instead of taking our word for the promise above.
Imprint
Artmann Technologies GmbH · Bockenheimer Landstraße 17-19 · 60325 Frankfurt am Main · Germany. Represented by: Lars Artmann (Geschäftsführer). Registered: Amtsgericht Frankfurt am Main, HRB 129896. Post: CAYA Postbox 849316, 96035 Bamberg.
Contact: hello@artmann.tech · Support: ssh-key-monitor@artmann.tech, answered within 48 hours, usually faster.