<\!DOCTYPE html> Security — ThetaZero <\!-- META_PIXEL_SNIPPET -->
🔒

We never sell your data. Your competitor research stays yours. We don't share your report inputs or saved reports with any third party for their own purposes — ever.

🔐

Authentication

JWT-based sessions signed with a secure secret. Passwords hashed with bcrypt. Session tokens expire after 7 days. No persistent server-side sessions.

🛡️

Encryption in Transit

All traffic between your browser and our servers is encrypted with TLS 1.2+. No unencrypted connections accepted.

🔑

Encryption at Rest

Sensitive tokens (OAuth credentials if connected) are encrypted at rest with AES-256-GCM. We never store plaintext secrets.

🏗️

Infrastructure

Hosted on Render (SOC 2 compliant). Database on Neon PostgreSQL with encryption at rest. Production environment isolated from development.

🚫

SQL Injection Prevention

All database queries use parameterized statements throughout the application. SQL injection through our API is not possible.

👥

Access Controls

Team roles (owner/member) with permission boundaries. Rate limiting on all authentication endpoints prevents brute force attacks.

Data Handling

Reports are generated from publicly available web data. When you enter a company name or URL, that input is used only to run your analysis — not shared with other users or sold to third parties.

No competitor data is stored beyond what you explicitly save to your workspace. You can delete any saved report at any time from your workspace.

Data Retention
Infrastructure Security
Responsible Disclosure

Found a vulnerability?

We take security seriously and appreciate researchers who disclose responsibly. If you discover a security issue in ThetaZero, please report it privately before making it public.

Contact: [email protected] — subject line "Security Disclosure"

We'll acknowledge your report within 48 hours and work with you to address the issue. We don't take legal action against researchers who follow responsible disclosure practices.

Scope Limits

When testing, please don't: