Security & Compliance
Security & Compliance posture
This page describes what's in place today, what's in progress, and what's on our compliance roadmap. For questions specific to your evaluation, contact compliance@foxnose.net.
At a glance
| Capability | Status |
|---|---|
| Per-tenant data isolation by data model | In place |
| Schema-validated API surface (typed filter operators) | In place |
| Granular role-based access control | In place |
| Audit log (30-day retention) | In place |
| EU data residency | In place |
| GDPR mode (optional, per project) | In place |
| Data Processing Agreement | In place |
| Sub-processors disclosure | In place |
| Three authentication models (JWT + Simple + Secure) | In place |
| US data residency zone | In progress |
| Extended audit log retention (90+ days) | In progress |
| Independent penetration test report | In progress |
| SOC 2 Type 2 certification | On the roadmap |
| HIPAA Business Associate Agreement | On the roadmap |
What's in place today
Per-tenant data isolation
Multi-tenancy is structural. Collections are the isolation boundary; a Flux API connects only the Collections you grant it, with per-Collection allowed_methods. A Collection invisible to a Flux key over REST is invisible over MCP. See Access Control.
Schema-validated API surface
The Flux query language uses a fixed allowlist of filter operators. Clients cannot submit raw SQL, Cypher, or arbitrary query DSL. See Search & Filtering.
Authentication
JWT for dashboard users; Simple Key for development; Secure Key (ECDSA P-256 signatures) for production. See Flux API Authentication.
Role-based access control
Roles scope at four granularities: organization, project, environment, and custom permission sets across content management, environment management, Management API, and Flux API.
Audit log
Every create, update, and delete on content produces an immutable event record. 30-day retention. Logs capture actor, action, entity, timestamp, IP, and request origin; request and response bodies are not stored. Audit data is scoped to the caller's read permissions.
EU data residency and GDPR mode
Core operational data is stored exclusively in the EU. Project data follows the storage zone chosen at project creation; EU is the only available zone today. Projects in the EU zone can enable GDPR mode, which guarantees that request processing also stays within the EU. See Data Residency.
DPA and sub-processors
A Data Processing Agreement is available on request. Sub-processors are listed publicly.
In progress
- US data residency zone — additional storage zone alongside EU.
- Extended audit log retention (90+ days, configurable) for paid plans.
- Independent penetration test report.
On the compliance roadmap
The items below are tracked against customer demand. If your evaluation depends on either, write to compliance@foxnose.net so we can update our planning with your timeline in mind.
- SOC 2 Type 2 certification.
- HIPAA Business Associate Agreement.
Reporting a security issue
Email security@foxnose.net with details, reproduction steps, and a contact channel. We acknowledge reports within one business day. Researchers are credited in our release notes.
For data-processing and compliance questions, contact compliance@foxnose.net. For general support, support@foxnose.net.