01DATA RESIDENCY
Where your data lives
Primary region
Canada (ca-central-1).
Backup region
Same region. Multi-region available on enterprise contracts.
No data leaves region
All customer records are single-region. AI inference runs against a US-region provider on a sanitised payload only (no PII, no narrative text). EU-only inference configurable per-tenant if a regulator requires it.
02ENCRYPTION
At rest + in transit
In transit
TLS 1.3 only. HSTS enforced. Modern cipher suites only.
At rest
AES-256-GCM. All databases, all backups.
Customer-managed keys (BYOK)
Available for Tier-1 contracts.
Field-level encryption
Confidential reports use null-at-write strategy — reporter identity dropped at intake, not stored encrypted. Stricter than encryption.
03TENANT ISOLATION
5-layer defense in depth
Layer 1 — Application
Every server-side endpoint filters records by the calling operator's org ID. Enforced by middleware on every request.
Layer 2 — Database row-level security
Row-level security is enabled and forced on every tenant-scoped table. The database itself refuses cross-tenant reads.
Layer 3 — Public API surface denied by default
External-facing roles cannot read any tenant data. The path is closed at the database role level, not just the application.
Layer 4 — Per-org background isolation
Background workers wrap every cross-tenant operation in a per-org context so even cross-tenant aggregations cannot read across operators.
Layer 5 — Tested
A CI gate blocks any new server endpoint that lacks the org filter. Every endpoint and worker is audit-tested before deploy.
04AUTHENTICATION
Methods supported
SAML 2.0
Per-org enterprise SSO. JIT user provisioning. SAML-attribute role mapping. SP metadata endpoint.
SCIM 2.0
User provisioning + de-provisioning. Bearer-token auth (sha-256 hashed; token shown ONCE on create).
OAuth (Google / Microsoft)
Per-user. Configurable per org.
Email + magic-link / password
Default. Disable per-org with sso.required = true.
API keys
Bearer-token auth for the integration surface. Per-key scopes (records / actions / audit / webhooks), last-used tracking and audit-logged with key ID. Available on enterprise plans.
05AUDIT POSTURE
Every mutation is logged
What's logged
Every record + workflow + admin mutation. action, entity, before/after snapshot, actor, IP, request_id, api_key_id (if bearer auth).
Retention
7 years default for tenant-scoped records (per ICAO Annex 13 5). Configurable per record type.
Searchable
/settings/audit-log for in-tenant. Filter by entity type, actor, date, action.
Export
JSON or CSV via /api/trpc/auditLog.exportCsv. Bearer-token authenticated.
Tamper-evident
Append-only. No UPDATE / DELETE statements anywhere in the codebase touch audit_log. CI gate enforces.
06REGULATOR ALIGNMENT
Compliance posture
ICAO Annex 13
24h notification + final report deadlines auto-tracked. Investigation phases mapped to workflow stages.
EU 376/2014
72h preliminary + 30d final report deadlines auto-tracked. Just Culture decision flow built-in.
ICAO Annex 19
SMS module aligned (hazards, SPIs, risk matrix, just culture, safety culture).
14 CFR Part 5 / AC 120-92
FAA SMS framework. NTSB Form 6120 export.
CAR 107 / TC AC 107-001
Transport Canada SMS. TSB notification workflow.
EU GDPR
DSR (data subject request) flow. DPA template available. Sub-processor list public.
07CERTIFICATIONS
Where we stand today
SOC 2 Type I
Observation in progress (started Q2 2026).
SOC 2 Type II
6+ months observation post-Type I. Targeting Q4 2026.
ISO 27001
Available on request for EU customers.
Pen test
Annual independent third-party penetration test. Summary attestation available under NDA; the testing firm is identified to enterprise customers under MNDA.
08SUB-PROCESSORS
Categories in the processing chain
Database
Tenant data, audit log and AI execution log. Single-region, encrypted at rest.
Hosting & edge
Application + static assets served from a global edge with automatic SSL.
AI provider
Calibrated AI agents for classification, risk, bowtie and precursor detection. Operator data is never used to train models.
Background processing
Durable workers for notifications, retention, scheduled reports and webhook delivery.
Email delivery
Transactional email for notifications, magic-links and digests.
Identity & storage
Sessions, file uploads, OAuth and SAML callback for enterprise identity providers.
Security monitoring
Error tracking and observability. Stack traces only — operator records are never sent.
Payments
Subscription billing on enterprise plans (handled by an external processor; eAviora never stores card data).
DNS & DDoS protection
Authoritative DNS, DDoS mitigation and TLS at the edge.
Vendor names + DPAs
Full sub-processor list with vendor names and DPA links is published in our Privacy Policy 09 and Terms 09 — the legal homes for processor disclosure.
TRUST CENTER
Deeper reference (~10 min read)
Per-section detail with live examples + CI gate references.
VULNERABILITY DISCLOSURE
security@eaviora.com
24h ack · 7d fix for Critical/High · we credit you in the advisory.