Security

How we keep your checks safe.

Pingvale sees your endpoints and your on-call schedule. Here is what we do with that, and what we don’t.

Data we hold

Monitor settings, check results, incident timelines, on-call schedules and the contact details you add for paging. We do not store response bodies; checks keep only the status code, timings and the assertion result.

Encryption

  • All traffic uses TLS 1.2 or newer.
  • Data at rest is encrypted with AES-256.
  • Secrets for authenticated checks (headers, tokens) are encrypted separately and are never shown again after you save them.

Access

  • Single sign-on with SAML and SCIM on the Scale plan.
  • Roles per workspace: owner, admin, responder, viewer.
  • Every change to a monitor, schedule or status page is written to the audit log.
  • Our staff access production only through short-lived, logged sessions.

Check infrastructure

Checks run from 30 regions on two cloud providers. Check runners have no access to customer data beyond the monitor they are running, and they are rebuilt from a clean image every day.

The assistant

The assistant reads alerts, monitor names and deploy markers to group incidents and draft updates. Your data is not used to train models. It cannot post updates, close incidents or change settings on its own.

Report a vulnerability

Write to security@pingvale.example. We reply within two business days and will not take legal action against good-faith research.

Copied