Trust at Aurakore

Signed evidence, live

Aurakore's own AI agents are recorded in an Excubitor ledger, the same product our customers use. Each record is hash-chained to the one before it. Every hour, a signing job signs the newest chain position with a managed signing key the ledger's writer does not hold, and stores the checkpoint in storage whose retention is locked, so nobody, including us, can change or delete it before its retention period ends. A new checkpoint is signed when new records have arrived since the last one, so a quiet hour adds none.

"Chain intact" is the answer of the same check our customers run in the Excubitor console: it recomputes the hash chain and compares it with the newest signed checkpoints, and reports a rewritten record, a missing record, or a checkpoint signed by any other key. This page shows our own ledger only. We do not publish anything about individual customers.

SOC 2

Information security policies

Our information security policy set is in review.

• Information Security PolicyIn review
• Access Control PolicyIn review
• Change Management PolicyIn review
• Incident Response Policy and PlanIn review
• Business Continuity and Disaster Recovery PolicyIn review
• Vendor and Third-Party Risk Management PolicyIn review
• Data Classification, Retention and Disposal PolicyIn review
• Acceptable Use and Security Awareness PolicyIn review

Subprocessors

The subprocessors of the Excubitor hosted service, as listed in its Data Processing Addendum. The service providers of the Aurakore ERP are described in section 6 of our Privacy Policy.

Where data is stored and processed

On the shared service, customer data is stored in the United States. An Enterprise customer can instead have a dedicated deployment, and chooses the region where its data is stored and processed. On a dedicated deployment, AI model processing stays in that region or jurisdiction, through our AI model provider's regional endpoint there. On the shared service, AI model processing may run in any of our AI model provider's regions.

How we protect data

• In transitEncrypted with TLS.
• At restEncrypted with AES-256 by our cloud provider.
• Two-factor sign-inEnforced by the server, which refuses accounts without a second factor.
• SessionsNo session lasts 12 hours or more.
• Idle sign-outThe Excubitor console signs a person out after 15 minutes idle, enforced by the server.
• Tenant isolationEach customer's data sits in its own database schema.
• Signed releasesExcubitor releases are signed with a key held in a managed key service, with a signed software bill of materials.
• Staff accessNo standing access. In Excubitor, staff reach a customer's ledger only through a read-only grant for one workspace, with a reason and a limit of four hours. The grant and every read under it are recorded in that customer's ledger.

Retention and deletion

• Deleted documentsA deleted Excubitor document can be restored for 30 days, then it is permanently purged.
• After terminationExport for 30 days after termination. Aurakore then deletes the data it holds for the customer from production within a further 30 days, and from backups within 35 days after that, except where the law requires keeping it. Aurakore keeps its own billing and account records as long as its legal obligations require.

Full detail is in section 8 of our Privacy Policy.

Contact security

To report a vulnerability, or to request security documents, write to security@aurakore.com.