BoundrixAI

Privacy Policy

Last Updated: January 2026

1. Data Minimization & Retention

BoundrixAI operates on a principle of least privilege and strict data minimization.

  • Request Bodies: By default, LLM request and response bodies are processed in-memory for zero-retention. If you opt-in to observability logging, data is doubly encrypted (AES-256-GCM) and subject to a configurable Time-To-Live (TTL), defaulting to 30 days.
  • API Keys: We never store your raw API keys. We store only cryptographic hashes (`key_hash`) for verification. Provider credentials (e.g., OpenAI keys) are stored using envelope encryption.

2. Data We Collect

  • Telemetry: Request latency, token usage counts, error rates, and model performance metrics.
  • Audit Trails: Immutable logs of configuration changes (e.g., "Contract Updated", "Member Invited") stored in our `audit_logs` ledger.
  • Identity: Business email addresses and authentication provider identifiers (Auth0/SAML/OIDC).

3. PII Redaction

Our inspection engine supports real-time PII detection. When configured, sensitive entities (Credit Cards, SSNs, PHI) are redacted before they leave the secure gateway environment. Redaction rules are enforced at the contract level.

4. Infrastructure & Subprocessors

We utilize SOC 2 Type II compliant cloud providers for hosting. Data is logically isolated using Row-Level Security (RLS) enforcement at the database layer, ensuring strictly verified tenancy access.

5. Contact

For Data Processing Addendum (DPA) inquiries or to request a data export, please contact privacy@boundrix.ai.