Privacy
Arximus uses the data needed to provide backup, restore, verification, storage, alerts, audit, and reporting. The platform is built around data minimization, encryption, access control, and customer visibility.
Data minimization
Arximus uses operational metadata, backup metadata, connection state, verification status, restore status, storage usage, audit events, and encrypted backup data when backup is enabled.
The service avoids unnecessary sensitive data in logs, dashboards, diagnostics, alerts, and reports.
Customer control
Customers control what systems are connected, which assets are protected, how retention is configured, who can trigger restores, and which users can access reports.
Disconnection, data export, deletion requests, and support access controls belong in the customer operating model.
Data categories
The data model supports recovery, verification, storage governance, and proof.
Asset
Protected asset ID, environment type, connection status, host metadata, backup policy, restore state, and readiness status.
Backup
Job ID, type, manifest hash, encrypted sizes, chunk hashes, verification state, and restore eligibility.
Storage
Encrypted chunks, manifests, restore artifacts, retention state, immutable state, and storage usage.
Restore
Restore plans, approvals, selected recovery points, validation checks, warnings, and reports.
Access
User actions, operator actions, support access, credential changes, restore approvals, and deletion requests.
Alerts
Backup job alerts, overdue backup alerts, storage warnings, restore updates, and drill results.
Privacy with purpose
Arximus keeps the service focused on operational data, encrypted backup data, and evidence needed to prove recoverability.
Next step
Security policy, terms, and status pages explain the operating model around the service.