Privacy

Security data should be limited, documented, and used for protection.

Arximus is designed to collect only the security and operational data needed to protect WordPress sites, verify backups, run restores, deliver alerts, and prove what happened.

Data minimization

The platform should not collect what it does not need.

Arximus is designed around security metadata, operational backup metadata, signed manifests, event records, and encrypted backup chunks when offsite backup is enabled.

The local plugin should not intentionally send passwords, full cookies, authentication tokens, payment data, private form messages, secret keys, recovery keys, or unencrypted backup contents.

Customer control

Cloud connection should be clear and controllable.

The Local Foundation can operate before cloud connection. When Arximus Cloud is connected, service communication is used to provide managed policy, threat intelligence, event correlation, backup storage, restore operations, and alerts.

Customers should be able to disconnect, export local data, delete local data, and review what the service uses.

Data categories

What Arximus is designed to use for protection.

The data model is built around security operations, backup reliability, and incident accountability.

Site

Site metadata

Site ID, plugin version, WordPress version, PHP version, environment status, and connection health.

Requests

Security metadata

Request URI, method, source IP, user agent, endpoint type, event type, rule ID, decision, and timestamp.

Backups

Backup metadata

Backup job ID, type, manifest hash, chunk hashes, encrypted sizes, verification state, and restore status.

Events

Operational events

Firewall, login, upload, policy, malware, integrity, backup, restore, and audit events.

Storage

Encrypted chunks

Encrypted backup chunks may be stored offsite when enabled. Backup contents should be encrypted before upload.

Reports

Proof records

Signed reports may reference events, manifests, policy versions, restore drills, and audit records.

Privacy outcome

The security service remains explainable.

Customers should understand what data is sent, why it is needed, and what should not be sent.

Limit

Collect less

Use fingerprints, hashes, metadata, and redaction where full values are not needed.

Document

Explain clearly

Disclose service calls, data categories, retention, and disconnect behavior.

Control

Give options

Offer export, erasure, disconnect, and local retention controls where applicable.

Protect

Secure storage

Use encryption, access control, audit logs, and tenant isolation in the cloud platform.

Privacy by design

Protection should not require careless collection.

Arximus is designed to protect sites while keeping data collection focused on security and recovery operations.

Next step

Review your data requirements.

We can discuss data categories, retention, encrypted backup storage, privacy settings, and customer controls.