Docs
Trust

Security

How Numezis protects your data — encryption, access control, audit.

Numezis is built for Swiss SMEs and their fiduciaries. Security is not a post-launch add-on — it's part of the architecture. This page summarizes how we protect data; a more detailed Security Whitepaper is available on request.

Hosting and data residency

  • The application and the primary database run in Switzerland, in Geneva, at Infomaniak (a Swiss operator). Customer documents, offsite backup copies and encryption keys are held in Switzerland, in Zurich, at Google Cloud.
  • Artificial-intelligence processing (language models, semantic vectors, document reading) runs in Sweden (EU, Microsoft Azure); inbound email is received in Germany (EU, AWS). Application error collection (Sentry) and web search for enrichment (Tavily) are located in the United States and receive no accounting or payroll data.
  • The complete list of sub-processors, with the location of each, is Annex 1 of the data processing agreement. We do not claim that all processing stays in Switzerland: it does not.

Encryption

  • In transit — TLS 1.3 minimum on all endpoints. HSTS preload enabled for www.numezis.com.
  • At rest — documents and offsite backup copies are encrypted (AES-256). The primary database is not encrypted by the database engine: it is protected by access control, network isolation and encrypted backups.
  • Application-level — personal-data fields of documents and integration credentials are encrypted with AES-256-GCM before they are stored.

Access control

  • Tenant isolation — Every API request carries an AccessMode scope. Code reviews and CI checks (audit-accessmode-scoping, audit-repository-scoping) enforce that no query can cross tenant boundaries.
  • Role-based — Workspace roles (Admin, Manager, Operator, Viewer) with custom-role extensions.
  • MFA — TOTP and WebAuthn passkeys. Workspace admins can enforce MFA org-wide.
  • SSO — Google Workspace and Microsoft 365 OIDC on paying plans.

Audit and logging

  • Every state-changing action writes to a per-tenant audit log: actor, timestamp, before/after, IP and user-agent.
  • Logs are retained for the active subscription period plus the legal Swiss commercial-records minimum (11 years for accounting and payroll events).
  • Tenants on the Pro+ plans can export their audit log via API.

Software supply chain

  • All code goes through pull-request review with at least one approval.
  • Dependency updates are gated by automated CI (test suite, security audit, supply-chain pinning via package-lock.json).
  • Container images are built locally then pushed to Google Artifact Registry; no third-party hosted CI handles secrets.

Incident response

  • 24/7 monitoring of error rates, latency, and unauthorized-access attempts via Sentry + Cloud Monitoring.
  • Severity-1 incidents (data exposure, full outage) trigger a status page update within 30 minutes and a written post-mortem within 5 business days.

Reporting a vulnerability

Please email security@numezis.com with steps to reproduce. We acknowledge within 1 business day. We do not yet run a paid bug bounty but recognize researchers publicly with their consent.

Capability-level guides (not duplicated on this trust page):