Privacy principle

SOS is designed to collect the minimum information required to run accounts, licences, security status and requested services.

Data processed

• Account data such as email and display name.
• Subscription/order data handled by WordPress/WooCommerce and enabled payment providers.
• A hashed device identifier, device label, platform, app version and security posture.
• Security notifications.
• For Secure Share, encrypted ciphertext plus expiry/download metadata. The decryption key is kept in the URL fragment and is not submitted to the SOS server.
• For SOS Vault, encrypted item ciphertext and an encrypted vault-key wrapper. Vault passphrases, recovery codes and the unwrapped vault key are not submitted to SOS.
• For passkeys, SOS stores the credential public key, label and counter metadata; the passkey private key remains with your authenticator.
• For encrypted backup, SOS stores encrypted file chunks and an encrypted manifest. The file/Vault keys are not submitted in plaintext.
• For Breach Monitor, monitored email values are encrypted at rest on the control plane and hashed for local matching. In SOS 0.10, email-breach matching is local-authorised-data only: no account-key email-breach provider is enabled. Pwned Passwords checks use k-anonymity and never send the password.
• For email aliases, SOS stores alias metadata and forwards only to the account email; the mail provider necessarily processes mail delivery.

Web & privacy protection

SOS Web Protection does not upload full browsing history, typed form contents or the destination list shown by the desktop connection monitor. Threat checks use a SHA-256 hash of the destination domain. Data Guard, anonymisation, browser permission checks, Platform Shield recognition/account checklists and spam/scam text heuristics run locally in the browser. Personal SOS connectors store only the domains, executable/app names, publishers and protection policies the user chooses to add; connectors cannot contain executable code. When you explicitly use Smart Protect, the public name you type may be sent to an available public 4get instance to discover public official-web information. Optional AI Horde explanations receive structured risk/reason codes rather than passwords, private messages, emails or browsing history. If you enable SOS Safe DNS, DNS requests are processed by the configured account-free resolver (Quad9 by default). The server rate limiter uses a keyed hash derived from the request IP and stores it temporarily.

Your choices

WordPress privacy export/erase tools include SOS device, alert and share metadata. Accounting/order retention can remain subject to legal obligations.

Contact

contact@suiteofsecurity.com