Privacy
Short version: PIMA stores what it needs to tell you whether your services are up, and nothing else.
What is stored
- Account: email address, password hash, role, optional TOTP secret
- Monitor configuration: names, target URLs, intervals, expected status
- Probe results: timestamp, success or failure, latency, HTTP status and error text for each check
- Incidents: start and end time, cause, failure count and notification count
- Audit trail: account events and configuration changes with actor, address and user agent
- Notification attempts: which channel, when, how many attempts, and the error returned
What is not collected
- No third-party analytics, advertising or fingerprinting scripts
- No tracking pixels in the dashboard, in alerts or in email
- No content of the pages being monitored beyond what a keyword assertion needs (a bounded read of the response)
- No data sold, shared or transferred to anyone
Retention
Probe results are kept for 7 days by default
(PIMA_RAW_RETENTION). Beyond that, hourly rollups are retained so long-term
uptime remains available without keeping every individual check.
Delivered notifications are pruned after 30 days. Expired sessions are deleted
automatically.
Cookies
One cookie, pima_session, which holds a random session token. It is HttpOnly,
SameSite=Lax, and Secure over HTTPS. A second short-lived cookie is used
during two-factor sign-in. There are no advertising or analytics cookies.
Where data lives
PIMA is self-hosted: the database is a file on your own server, and backups are your responsibility. If you run PIMA as a managed service, the operator of that service is the data controller and this page describes what the software stores.
Your rights
You can export or delete any of this from the admin interface, or by asking the operator of your instance. Deleting a monitor removes its history with it, which is deliberate: the history is the record of what that monitor saw.
Changes
Material changes to this page will be dated. Last updated 2026-10-01.