Security built into the architecture.
Arckium handles operational data for buildings, hospitals and critical infrastructure. This page describes the controls that exist today. Infrastructure detail and our sub-processor list are available under NDA.
Tenant isolation on every request
Each authenticated request resolves a tenant context before any query runs, and server-side guards constrain queries to the active property. Reaching another property's data requires an organisation-admin role and an explicit group scope.
Encrypted credentials, encrypted transport
Traffic is served over TLS. The credentials we store on your behalf, meaning SMTP passwords, PMS client secrets and push signing keys, are encrypted in the database with AES-256-GCM under a key held outside it. Infrastructure-level encryption at rest and our hosting provider's configuration are shared under NDA during procurement.
Audit log
Security-relevant actions write a record carrying actor identity and email, the action, the target, before and after state, and a timestamp, across auth, data, admin, configuration and system categories. Records are never edited; they are only removed when a person exercises their right to erasure.
Access control enforced at the API
Roles are assigned per property and checked by guards on the server, so the API refuses what the interface does not offer.
Signed sessions
Sessions use signed JSON Web Tokens with an eight-hour expiry, validated on every request.
Responsible disclosure
Report security issues to contact@arcana-soft.com. We acknowledge within two business days, triage by severity and keep you updated until the issue is fixed. We do not pursue good-faith researchers.