Security

Last updated 2026-04-16. How we protect credentials, traffic, and customer data.

Encryption

In transit

TLS 1.3 everywhere. HSTS preloaded. No TLS below 1.2 allowed. Cipher suites restricted to modern AEAD.

At rest

AES-256-GCM on Postgres and object storage. Disks on Fly.io and Supabase are encrypted by default.

Key management

Access controls

Vulnerability disclosure

If you find a security bug, report it to security@metercall.ai. PGP key available on request. We acknowledge within 24 hours and triage within 3 business days. Safe-harbor for good-faith research.

Bug bounty

Rewards scale with severity. Pre-launch bounty runs on a private invite basis; expanding to public on HackerOne in Q3 2026.

SeverityRangeExample
Critical$2,500 – $5,000Auth bypass, customer credential exposure, full RCE
High$750 – $2,500Priv-esc, IDOR exposing another customer's data
Medium$250 – $750Stored XSS, SSRF without cred exposure
Low$100 – $250Reflected XSS on unauth surface, CSRF on low-risk action

In scope: *.metercall.ai, our Fly.io gateway, the iOS/Android agent apps when they ship.

Out of scope: rate-limit bypass on unauth endpoints, missing security headers without exploit path, clickjacking on static pages, third-party vendor issues (report directly to them), social engineering, physical attacks, DoS.

Penetration testing

Annual third-party pen test. Next test: Q2 2026 (NCC Group, pending). Executive summary available to Enterprise customers under NDA.

SOC 2

SOC 2 Type II audit in progress — observation period started Q1 2026, report expected Q3 2026 (Prescient Assurance). We'll post the Type I letter when it drops.

Incident response

On-call rotation 24/7. Customer notification within 72 hours of confirmed breach affecting your data, with preliminary details and a commitment to a fuller RCA within 14 days. Status page at status.metercall.ai.

Secure development

Last updated 2026-04-16. Questions → /contact.html