Trust Center
What we collect, where it lives, how long we keep it, and how we protect it — stated plainly, in the same words we'd want from anyone holding our data. This page describes what the AEAntivirus server actually does today; our Privacy Policy and Terms of Service are the governing documents.
What data is collected
- Account data — your email address, your first and last name (if you give them), and a scrypt-hashed password. If you turn on two-factor authentication, your authenticator secret is stored server-side only and recovery codes are stored hashed.
- License data — your license key, the email it was issued to, its plan and status, the current billing period end, and the Stripe customer/subscription identifiers that link it to your payment.
- Device / install data — for each protected device: an install identifier and device token, the computer's hostname, app and definitions versions, platform, a hashed device fingerprint (so a reinstall reuses the same seat), protection-module on/off states, scan counts and times, lifetime threats blocked, and a small CPU/memory snapshot from the last check-in.
- Detections — when the app finds a threat: the threat name, the file path on that device, and the time. Your files themselves are not uploaded for ordinary detections.
- Operational records — sign-in attempts, an email delivery log (recipient, subject, whether it sent), support messages you send us, and an admin audit log of actions taken in the admin console.
We do not sell personal data, and threat lookups from the app send file hashes — never your files and never your browsing history. Parental-control and web-filter decisions happen on your PC; the sites your family visits are not sent to us.
Where it is stored
- Our server database — account, license, device, and detection records live in the AEAntivirus server's database, hosted on Render.
- Payments — card payments are processed by Stripe. Your card number never touches our server; we store only the Stripe identifiers needed to manage your subscription.
- Email — verification mail, alerts, and digests are sent through the mail provider configured for this server.
How long it is kept
- Account and license records are kept while your account exists.
- The server's automatic retention purge is off by default — nothing is deleted unless the owner turns it on. When enabled, detections, heartbeat history, and audit entries older than the configured window (90 days by default) are purged on a daily schedule, and every purge is itself audit-logged. Accounts holding the Extended threat history add-on keep detections for 365 days instead.
- The email delivery log prunes entries older than 90 days automatically.
- The admin audit log is a file that keeps its newest 5,000 entries.
- Operational stores (detections, email log, login attempts, verdict reports, job runs, archived support messages, Stripe event log) can be pruned by age — 30, 90, or 180 days — from the admin Data cleanup screen. Licenses, accounts, devices, and payment data are never prunable there.
How we protect it
- Passwords are hashed with scrypt and a per-password salt — never stored in plain text — and passwords known to have appeared in public data breaches are refused at sign-up and checkout.
- Two-factor authentication (authenticator-app TOTP codes, with hashed one-time recovery codes) is available for customer accounts and protects the admin console; passkey sign-in is also supported for accounts.
- Audit logging — admin actions (license changes, refunds, settings, data prunes, backups) are written to the audit log with a timestamp and actor.
- Secrets stay secret — configuration screens show whether a key is set, never its value; API tokens are stored only as SHA-256 hashes and shown once, at creation.
- Backups with exclusions — the admin one-click data download always excludes credential material: the session secret, the admin 2FA secret and recovery hashes, customer vault contents, and any .env-style file never enter the archive, and every download is audit-logged.
- Sessions expire after inactivity, and you can review and revoke your account's active sessions from My Account.
Who else processes data
Three kinds of providers touch the data above, each only for its job: Stripe (payments and subscriptions), Render (server hosting), and the configured mail provider (sending email). We do not share your data with data brokers or advertisers.
Read the Privacy Policy Terms of Service Ask a privacy question