Privacy

Last updated 28 October 2026.

This policy covers the hosted Posterna service at posterna.com. The open-source packages run inside your own app and send nothing to Posterna unless you give them a site key; Data handling lists exactly what they send and what the service stores.

Questions or requests about your data: [email protected].

What we collect

• When you sign in with GitHub: your GitHub account id, username, name, email address and avatar. We ask GitHub only for your identity (the read:user and user:email permissions) and keep no GitHub access token. Posterna never asks for a password: you sign in on github.com.
• When you add a site: its name and domain. We store a hash of the site key, not the key.
• From your installs: hourly counts and install state, as described on Data handling. Never your visitors' IP addresses, full URLs, query strings, header values or page contents.
• When you run the probe: the domain you entered, a salted hash of your IP address (used only to limit runs to 10 an hour), and the results of the run. A probe report is public to anyone with its link.
• When you use the operator form: what you enter: organization, contact email, key directory URL, agent names and notes.
• When you use the echo endpoint or the agent lab: nothing is stored or logged. Your IP address is used for the check and for rate limiting in memory, then discarded. The one exception is a lab link Posterna makes for its own tests (it carries a signed run id): for those requests the lab keeps the verdict, the User-Agent and the signature details, never the IP address.
• When you visit posterna.com: posterna.com runs Posterna on itself, in monitor mode, like any install. It labels each request and keeps only the same hourly counts an install sends (verdict, reason, operator, agent, purpose and path group, as described on Data handling), never your IP address, the full URL, header values or page contents. It blocks nothing.
• When you email us: your message and address.

What we use it for

To run the service: signing you in, showing your dashboard, applying your settings, limiting abuse, reviewing operator listings, and answering you. We do not sell data, show ads, or use analytics or tracking scripts.

Cookies

Cookies are used only to sign you in and keep you signed in: three during GitHub sign-in (a security token, the page to return to, and one that protects the sign-in exchange for 15 minutes), then one session cookie. A session lasts 30 days and is extended when you use the site. Reading the public pages sets no cookies.

How long we keep it

• Your account, and each site with its key: until you delete them.
• Hourly counts: 13 months. Install records: 30 days after the install last reported.
• Sessions: until they expire, 30 days after your last visit.
• Probe runs: 30 days.
• Operator requests: 12 months.
• Lab runs from Posterna's own tests: 90 days.

A daily job deletes data once its period has passed. Data handling has the details per table.

Who else handles data

Railway and Cloudflare, like any web host, see the IP address and details of every request to posterna.com and may keep logs of them under their own policies. Posterna's own application logs never record IP addresses, URLs, header values or request bodies.

We share data with no one else, except when the law requires it.

Security

Site keys are stored as hashes. Posterna's signing keys live only in the hosting provider's environment variables. Every page and action that touches a site checks on the server that it is yours.

Your choices

• Delete a site: in the site's Settings. Its key, counts and install records are deleted at once.
• Delete your account: on the Account page. Your account, sessions, sites, keys, counts and install records are deleted at once.
• Anything else, such as a copy of your data or deleting a probe report or an operator request: email [email protected].