Security
What MICrypt protects and what you should verify.
Local processing
File bytes, filenames and passphrases are handled locally. The application uses no accounts, analytics, remote API, or file storage. The host serves the application assets and may keep ordinary page-request logs.
Authenticated encryption
MICrypt uses AES-256-GCM and Argon2id with 64 MiB, three passes, and four lanes. Each file uses a fresh salt and nonce. The browser releases plaintext only after the full authentication tag is verified.
Audit status and limits
This application has not undergone an independent security audit. A compromised browser, extension, device, or hosting origin can defeat local safeguards. Use a strong passphrase and retain trusted backups.
The filename and size may be apparent to anyone with access to the result. Downloaded files are stored by your browser and operating system. Legacy ccrypt cannot verify content integrity.