Data residency
Insurer data is stored in the insurer’s region, and a node does not serve requests from another region. For those who need full control, the system is installed in the client’s infrastructure and runs with no connection to the cloud.
Storage region
Each insurer has its own data storage region. A node refuses service to an insurer from another region.
Shared or separate database
The insurer works in a shared database separated by organization or in a separate database that is created automatically.
Your own infrastructure
Installation in the client’s infrastructure or a private cloud. The license is signed with Ed25519 and verified with no connection to the cloud, and on expiry the system switches to read-only mode instead of stopping.
Personal data encryption
Passport and other personal data is encrypted with AES-256-GCM with key rotation, and the keys are stored in HashiCorp Vault.
Anonymization
At the data subject’s request, scans, addresses, correspondence, sessions and saved cards are anonymized in one operation.
Telemetry without personal data
Traces and metrics contain no personal data of clients.
Deployment
The general data storage rules of the A3 ecosystem are described on the A3.Solutions website.
Data storage in the ecosystem- Docker and Helm with a separate node for background jobs
- Partitioning of growing tables
- Metrics of missed deadlines and queue depth through OpenTelemetry
- Automated tests for every release: about 2,350 checks
Shall we discuss hosting for your requirements?
Tell us where the data must be stored and what your regulator and security team require.