Security
ANOXY is built with privacy and security at its core. Here's how we protect your data.
Privacy by Design
ANOXY processes sensitive text without retaining it. Anonymization sessions are ephemeral, encryption is enforced at every layer, and we never use your data for training or analytics. Your data passes through — it doesn't stay.
Data Handling
Ephemeral Sessions
Anonymization sessions have a 1-hour TTL. After expiry, all original text, entity mappings, and PII data are permanently deleted from our systems. No residual data remains.
No PII Retention
We do not store, index, or log the original PII values from your text. Only anonymized tokens and session metadata (counts, timestamps) are retained for quota tracking.
No Training on Your Data
Your text is never used to train models or improve algorithms. PII detection uses pre-trained models and rule-based patterns that operate without learning from user data.
Encryption
In Transit
All API communication is encrypted with TLS 1.2+ (HTTPS). Unencrypted HTTP connections are rejected in production. API keys and tokens are transmitted only over encrypted channels.
At Rest
Database storage uses AES-256 encryption at rest. Session data is stored in memory with encrypted persistence. Backups are encrypted before storage.
Authentication & Access Control
API Key Authentication
API keys are hashed with SHA-256 before storage. Only the key prefix is visible in the dashboard. Full keys are shown once at creation and cannot be retrieved afterwards.
OAuth 2.0 / OpenID Connect
User authentication uses industry-standard OAuth 2.0 with PKCE flow via our self-hosted identity provider. Tokens are signed with RS256 (RSA + SHA-256).
Role-Based Access
Users can only access their own sessions, API keys, and billing data. Administrative endpoints require elevated roles. All access is logged for audit purposes.
Infrastructure Security
Isolated Services
Each service (API, database, cache, identity provider) runs in isolated containers with minimal network exposure. Internal communication uses private networks.
Dependency Management
Dependencies are pinned to specific versions and regularly audited for known vulnerabilities. Security patches are applied promptly.
Audit Logging
Security-relevant events — authentication attempts, API key creation/revocation, billing changes, and administrative actions — are recorded in tamper-resistant audit logs.
Responsible Disclosure
We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly.
How to Report
- Email anoxy@eskom.ai with a detailed description of the vulnerability
- Include steps to reproduce the issue
- Allow reasonable time for us to address the issue before public disclosure
- Do not access or modify other users' data during testing
We acknowledge reports within 48 hours and aim to resolve critical issues within 7 days.