Pingvera legal ← Back to home
Trust

Trust and security

Only statements you can verify: how checks and the agent work, how we protect passwords and payments, and what Pingvera does not do. No promises we cannot back up.

01

How external checks work

Site checks run from the outside, from locations in Russia and Europe. Nothing has to be installed on the site.

  • —Every request is signed: the User-Agent contains Pingvera, so checks are easy to filter out of your analytics.
  • —An outage is confirmed by several locations before you are notified. One location with a network problem does not raise an alert.
  • —An event closes by itself once the check passes again. There is no “acknowledge” or manual resolve: the record reflects check data only.
02

The server agent

The agent is only needed for server metrics (CPU, memory, disk, services). It works one way.

  • —The agent only sends data. It has no inbound connection, accepts no commands and never runs anything on the server on our initiative.
  • —The agent does not update itself. Only the server owner installs a new version, by reinstalling.
  • —The installer checks the SHA-256 checksum of the downloaded file against the one the service publishes and refuses to install on mismatch.
03

Passwords and payments

  • —Passwords are stored only as an argon2id hash with OWASP-recommended parameters. A password cannot be recovered from the hash, so we never know it and never send it.
  • —Payment happens on the payment provider’s page. Card data never reaches our servers.
04

Your data

  • —We do not sell or share personal data. Details are in the Privacy Policy.
05

Backups

  • —The configuration database (sites, checks, users, events) is backed up daily, check history weekly.
  • —Backups are pulled by a separate server that has read-only access to production, so compromising a production server does not let anyone delete the backup archive.
  • —Once a week a fresh backup is actually restored into a separate database, and an automated check confirms it contains organisations, users, checks and migrations.
06

What Pingvera does not do

  • ✕It does not log in to your server or run commands on it.
  • ✕It does not update the agent behind your back.
  • ✕It does not run incidents for people: no assignees, escalations or on-call schedules. Pingvera reports “up / down / up again” and helps you understand why.
  • ✕It does not use ICMP ping. Server reachability is checked over a TCP port.
07

When Pingvera is not for you

  • —You need an on-call system with escalations and shift schedules — Pingvera can send alerts into one via webhook, but does not replace it.
  • —You need application performance monitoring (APM): request traces, slow functions.
  • —You need check locations in Asia or the Americas: today they are only in Russia and Europe.
08

Report a vulnerability

Found a security issue? Email info@pingvera.com with the subject “Vulnerability”. Please do not publish details until we reply.

09

Documents

← Back to home · Privacy Policy · Terms of Service