Privacy Policy
Last updated: September 14, 2026
1. Information We Collect
When you create a Pyra account, we collect your email address and authentication identifiers provided through Clerk. When configuring keep-alive targets, you provide endpoint URLs, optional HTTP authorization tokens, and desired ping frequencies.
2. Envelope Encryption for Authorization Headers
Any Authorization headers or API credentials stored for authenticating keep-alive pings are encrypted at rest using AES-256-GCM envelope encryption. Secrets are decrypted strictly in memory by worker nodes at scheduled execution time and are never written to unencrypted logs or telemetry streams.
3. Multi-Tenant Database Isolation
All account records, targets, and execution logs are isolated via Postgres Row-Level Security (RLS) enforced at the database connection pool layer. Your infrastructure configurations are cryptographically and structurally inaccessible to other tenant workspaces.
4. Telemetry and Ping Logs
We record HTTP status codes, execution timestamps, and round-trip response latencies in order to provide your uptime dashboard and trigger configured alert thresholds. We do not inspect or store response payloads returned by your servers.
5. Contact Us
For privacy inquiries or data deletion requests, contact our infrastructure security team at privacy@pyra.dev.