Skip to content
FRSign inBook a walkthrough

Trust center | Security one-pager

One page for your security review.

Prints on one page. Every line is answered in full in the trust center.

Read the ten blocks
eAviora

Security and compliance summary
Reviewed 13 October 2026
eaviora.com/trust

Security one-pager

For procurement, IT security and risk teams. Each line is answered in full at eaviora.com/trust.

Where data lives

  • Stored in Canada, in the Montréal region of our database provider.
  • The application runs in the United States, US East region.
  • Files and backups stay in the storage region.

Isolation

  • Row-level security forced on every organization’s tables.
  • The application role cannot bypass it; a missing filter returns no rows.
  • Five layers, from request checks to the database.

Encryption

  • AES-256 at rest on database, files and backups (provider-attested).
  • HTTPS with strict transport security (HSTS); TLS 1.0 and 1.1 refused.
  • API keys and provisioning tokens stored hashed, shown once.

Backups and recovery

  • Seven rolling daily backups, in the same region.
  • Point-in-time recovery is not enabled: up to one day of changes at risk.

AI governance

  • eAvy proposes; a person accepts, changes or dismisses before a write.
  • No AI can move a record’s workflow stage.
  • Agents read only the fields they are set up to read; no reporter identity.
  • eAviora trains no model on your data. AI is processed through OpenRouter.

Confidential reporting

  • Three access levels on every record and document: Standard, Confidential and Privileged.
  • The name of a confidential reporter shows only to cleared readers.
  • On an anonymous report, the reporter’s name is hidden from everyone, our staff included.

Sign-in and access

  • SAML 2.0 single sign-on (Okta, Microsoft Entra, Google), enforceable.
  • SCIM 2.0 provisioning and removal.
  • Authenticator codes, session list, sign out everywhere.
  • API keys scoped read, write or admin.

Audit trail

  • App and API changes write their audit entry in the same transaction.
  • Append-only and chained in the database.
  • Searchable in the app; exports as JSON or CSV.

Portability

  • Export every record and the audit log as JSON or CSV, any time.
  • Occurrences export as E5X for ECCAIRS.
  • CSV import up to 50 MB, with column mapping.

Not yetStated plainly

  • SOC 2 Type I in preparation; no certification claimed.
  • No third-party penetration test performed yet.
  • ISO 27001 not held. Bring-your-own-key is not supported.
Vulnerabilities: security@eaviora.com, acknowledged within 24 hoursDPA version 1.4 | eaviora.com/subprocessors© 2026 Eaviora Inc.
The sheet, as it prints | reviewed 13 October 2026
Four readings

The page in four readings.

5Isolation layers. From request checks to the database.
7Daily backups. Rolling, in the same region.
3Access levels. Standard, Confidential and Privileged.
24Hours to acknowledge. Every vulnerability report.
Ten blocks

Security one-pager. Every block.

For procurement, IT security and risk teams. Each line is answered in full at eaviora.com/trust.

  • Where data livesStored in Canada, in the Montréal region of our database provider.In place
  • IsolationRow-level security forced on every organization’s tables.In place
  • EncryptionAES-256 at rest on database, files and backups (provider-attested).In place
  • Backups and recoverySeven rolling daily backups, in the same region.In place
  • AI governanceeAvy proposes; a person accepts, changes or dismisses before a write.In place
  • Confidential reportingThree access levels on every record and document: Standard, Confidential and Privileged.In place
  • Sign-in and accessSAML 2.0 single sign-on (Okta, Microsoft Entra, Google), enforceable.In place
  • Audit trailApp and API changes write their audit entry in the same transaction.In place
  • PortabilityExport every record and the audit log as JSON or CSV, any time.In place
  • Not yetSOC 2 Type I in preparation; no certification claimed. No third-party penetration test performed yet. ISO 27001 not held. Bring-your-own-key is not supported.Not yet

Bring your questionnaire.

We answer it live, on the running platform.