Security
An overview of how PWR handles database access and data.
- ✓Database credentials are only used to run read-only monitoring queries (pg_stat_*, pg_settings) - never to modify application data.
- ✓Snapshots capture aggregate performance statistics, not row-level application data.
- ✓No sensitive data: PWR never reads your table rows, business data, or PII - only PostgreSQL's own statistics catalogs (query timings, wait events, locks).
- ✓Traffic between the app and the API is served over HTTPS.
Found a security issue? Report it to contact@audit-postgresql.com.
Available 24/7 · Free
Not sure where to start?
On the call, ask us anything about:
Your architecture
Your failover setup
PostgreSQL versioning
Your proxy (PgBouncer / pgpool)
Production impact
Installing on a replica
Security & sensitive data
Book a free 15-minute call so we can answer all your questions (architecture, failover, versioning, proxy, production impact, installing on a replica...), then get PWR running together on your PostgreSQL database.
Book a technical call