← Back to Home
Security & Data Protection
Your data security isn't just a feature — it's a fundamental design principle of OpsChaos Scanner.
🛡️ Data Non-Disclosure Guarantee
We guarantee that your operational data will never be disclosed, sold, shared, or used for any purpose beyond generating your chaos report.
- ✓Your data is NEVER sold to third parties — under any circumstances.
- ✓Your data is NEVER shared with other customers, partners, or affiliates.
- ✓Your data is NEVER used for marketing, advertising, or profiling.
- ✓Your data is NEVER used to train AI/ML models.
- ✓Your data is NEVER retained beyond the 72-hour auto-deletion window.
- ✓Each scan session is completely isolated — no data crosses session boundaries.
Encryption Architecture
- •AES-256-GCM application-level encryption — OAuth tokens and PKCE verifiers are encrypted before storage.
- •TLS 1.3 in transit — all data transmitted between your browser, our servers, and third-party APIs is encrypted.
- •PKCE (Proof Key for Code Exchange) — OAuth authorization codes are protected against interception attacks.
- •Encryption keys are environment-specific and never committed to source control.
Access Control
- •Read-only OAuth scopes exclusively — we can never modify, delete, or send data in your tools.
- •Minimum-privilege principle — we request only the exact permissions needed for analysis.
- •No admin access required — individual user-level OAuth grants are sufficient.
- •You control which tools to connect — skip any tool you're not comfortable sharing.
Token Lifecycle
- •OAuth tokens are generated when you approve access to each tool.
- •Tokens are immediately encrypted with AES-256-GCM and stored in the database.
- •During analysis, tokens are decrypted in-memory only for the duration of API calls.
- •Immediately after analysis completes, all tokens are permanently wiped from the database.
- •We never store refresh tokens — one-time access only, no persistent access to your accounts.
Data Lifecycle
- •Session created → 72-hour countdown begins.
- •Analysis runs → only aggregated counts are stored (never raw content).
- •Tokens wiped → immediately after analysis (0 persistence window).
- •Report available → viewable until 72-hour expiration.
- •Auto-deletion → background process purges all session data at 72 hours.
- •Manual deletion → "Delete My Data" button for instant, irrecoverable removal at any time.
LLM Data Handling
- •Aggregated metrics (counts, ratios, durations) are sent to OpenAI API for analysis using the configured model.
- •No raw content (emails, messages, files) is ever sent to the LLM.
- •OpenAI does not use API data for model training (per their API data usage policy).
- •LLM responses are not cached or reused across sessions.
Infrastructure Security
- •Application hosted on Railway with automated deployments.
- •PostgreSQL database with encrypted connections (SSL required).
- •No public database access — database is only accessible from the application server.
- •Environment variables for all secrets (API keys, encryption keys, OAuth credentials).
- •Security headers: X-Frame-Options DENY, X-Content-Type-Options nosniff, strict Referrer-Policy.
Compliance Posture
- •GDPR-aligned data practices: consent-based processing, right to deletion, data minimization.
- •No PII stored — only aggregated operational metrics.
- •Data processing agreement available upon request for enterprise customers.
- •Regular security reviews and dependency audits.
Security Questions?
For security-related inquiries or to report a vulnerability, contact security@opschaos.com.