Security at PaidGuard
We're handling your payment infrastructure. That demands a higher security bar than most SaaS. Here's how we meet it.
Defenses in place
OAuth, not API keys
You never paste a raw API key into PaidGuard. Stripe OAuth flow with explicit scope grants. Tokens stored encrypted at rest.
No money movement
Every permission PaidGuard requests in its Stripe App manifest is read-only. Stripe may add account-level permissions of its own at install time — the install screen lists exactly what you grant, and PaidGuard has no code path that charges a card, issues a refund, or modifies a subscription.
Encryption in transit and at rest
All data encrypted in transit (TLS 1.2+). Database encrypted at rest (AES-256). Backups encrypted. Database hosted on Neon.
No card data stored
PaidGuard never sees or stores customer card numbers, CVVs, or expiry dates. Stripe handles all PCI-DSS compliance. PaidGuard's code has no path that charges a card or stores a payment method — you can see the exact access granted on your Stripe Connected Apps page.
Revoke access anytime
Disconnect from your PaidGuard dashboard, your Stripe dashboard, or both. Token revocation is instant.
GDPR & CCPA compliant
Data export, deletion, and audit logs available on request. Privacy policy is public.
Certifications & posture
Report a vulnerability
Found a security issue? Please email security@paidguard.io instead of posting publicly.
We respond to all reports within 48 hours. Severity-1 issues are addressed within 7 days. We're happy to work with researchers on coordinated disclosure and offer recognition for valid reports.