Security & Trust
PlanningPoker.live is an open-source, serverless app built entirely on Google Cloud. Here's how we keep your data safe.
Architecture Overview
PlanningPoker.live runs on a fully serverless architecture powered by Firebase and Google Cloud. There are no custom servers, no VMs, and no SSH surface to attack. All infrastructure is managed, patched, and secured by Google.
Marketplace Security Reviews
PlanningPoker.live is listed on four major collaboration platform marketplaces. Each platform conducts its own independent security and compliance review before approving an app for distribution.
Open-Source Codebase
The entire PlanningPoker.live codebase is public on GitHub. This includes the Angular frontend, Firebase Cloud Functions, Firestore security rules, and storage rules. Anyone can audit the code, verify our security claims, and see exactly what data we access.
We believe transparency is the strongest security signal a small app can offer. Instead of asking you to trust a black box, we invite you to read the source.
View source on GitHubGoogle Cloud & Firebase Certifications
Firebase is part of Google Cloud and inherits its world-class security infrastructure. All data is encrypted at rest (AES-256) and in transit (TLS 1.2+). Google manages infrastructure patching, DDoS protection, and physical data center security.
Learn more: Firebase Security & Privacy · Google Cloud Compliance
Data Handling & Storage
What we store
- Room data: topics, votes, card sets, timer state
- Display names chosen by participants
- Email address (only if you create an account)
- Organization metadata (name, member list)
- Stripe customer reference (for premium users)
What we don't store
- Passwords — Firebase Auth handles hashing
- Credit card numbers — Stripe handles payments
- Sensitive PII beyond your email address
- Screen recordings, keystrokes, or clipboard data
- Data from your Jira/Linear beyond synced issues
Authentication & Access Control
Transport & HTTP Security
All traffic to PlanningPoker.live is served over HTTPS with modern security headers. The serverless architecture means there are no managed servers, VMs, or SSH endpoints to attack.
Strict-Transport-SecurityHSTS with preload — max-age=31536000; includeSubDomains; preloadContent-Security-PolicyRestrictive CSP limiting allowed script, style, and frame sourcesX-Content-Type-Optionsnosniff — prevents MIME type sniffingReferrer-Policystrict-origin-when-cross-originMonitoring & Error Tracking
Security Questions?
If you have security questions, need to complete a vendor assessment, or want to report a vulnerability, reach out to us at [email protected].
You can also review our Privacy Policy and Terms & Conditions.