Your key.
Your control.
No email or password is required. This page explains the data the account system needs and the infrastructure processing we cannot describe as no logs.
Your account key
Your browser generates a random 256-bit account key and shows it once. The original key is not sent to our server or saved in browser storage by the application. Signing in sends a derived proof over HTTPS. The server stores a separate SHA-256 verifier of that proof.
Anyone with your original key or a stolen login proof can sign in. Keep your key private. We cannot show it again or restore access if you lose it. No system is uncrackable; this design does not protect against a compromised device, malicious browser extension, phishing, or a compromised service.
What the application stores
- A random account ID, key verifier, and creation timestamp.
- Hashed session tokens, account references, and creation and expiry times for currently retained sessions. Sessions last up to 12 hours.
- Hashed browser-verification tokens with a 30-minute lifetime.
- Short-lived aggregate request counters, without account IDs or IP addresses.
The application does not record browsing history, a sign-in history, IP addresses, user-agent strings, scan results, email addresses, or original account keys. It contains no advertising or analytics integrations.
Session sign-out deletes the corresponding server-side session immediately. Expired session and verification rows and request counters are deleted during subsequent verification requests; they cannot authenticate after expiry even before cleanup. Account records remain until an account-deletion process is implemented. Cloudflare database backups may retain previous data according to its service retention.
Desktop trial and paid-key eligibility
The desktop app sends a hashed hardware identifier when you check eligibility, start a trial, or activate a paid key. The service stores a separately hashed device reference and the original trial start and expiration. This record remains after the trial ends to prevent another trial on the same recognized device, including under a new account.
Anonymous trial creation and hardware-ID-only trial status checks are disabled while a verified trial-authorization flow is prepared. Existing trial records are retained, but are not exposed through the anonymous API.
Paid-license checks use short-lived per-key request counters containing a separately hashed key reference, count, and expiry. These expire within two minutes and are removed on subsequent licensing or verification requests. They do not store the original key, IP address, or a history of individual requests.
Paid-key records contain a key verifier, duration, activation and expiration times, revocation status, and the hardware reference assigned at activation. Licensing does not collect your files, scan activity, email address, or raw hardware identifier. These device references are pseudonymous identifying data, not anonymous data. Internet access is required for licensing checks. Public downloads and checkout remain unavailable while the app is in development.
Necessary cookies
__Host-rc_session is a Secure, HttpOnly, SameSite=Strict session cookie with a 12-hour maximum lifetime. __Host-rc_clearance is a Secure, HttpOnly, SameSite=Strict browser-verification cookie lasting 30 minutes. Both are limited to this host and are not accessible to page JavaScript.
No account key is stored in cookies, localStorage, or sessionStorage. Copying a key is an explicit action and places it on your device clipboard, which your operating system or other software may retain.
Cloudflare and human verification
Cloudflare hosts the website, database, and Turnstile verification. Visitors encounter a server-validated browser check before protected pages, and account creation and sign-in require a new verification. Cloudflare may process IP addresses, request metadata, device signals, security events, and infrastructure logs. Its processing and retention are separate from this application's minimal records.
We do not promise zero logs, anonymity, or zero infrastructure retention. The application does not intentionally log request bodies, keys, proofs, cookies, or individual account activity. Privacy information remains available before browser verification.
Desktop product and payments
The intended desktop policy is local scanning without file, scanned-path, or scan-telemetry uploads by default. Those release behaviors still need verification. Website accounts do not activate antivirus protection. Public downloads, subscriptions, and payment collection are not available.
Account controls and contact
The dashboard supports signing out of this browser or all active sessions. Account-key rotation, account deletion, and a verified privacy contact are not available in this initial account release. Do not send keys or private files through unverified channels.
Support information โ