Security
What the server never receives
- Your private keys, whether generated or imported.
- Encryption passwords and passphrases.
- The plaintext of your messages and files.
All cryptographic operations run in your browser (Web Crypto API, OpenPGP.js, age, Argon2 in WebAssembly). There is no table of private keys or messages in the database, and no history of operations.
What the server knows
- Your Discord ID, username and avatar.
- The public keys you choose to publish, their metadata and their history.
- Your sign-in sessions (only a SHA-256 hash of the token is stored).
Measures in place
- Strict Content Security Policy: no third-party scripts, no trackers, no ads.
- State-changing requests protected against CSRF (origin check, SameSite cookies).
- Validation of every input, parameterised SQL queries, rate limiting.
- Public key fingerprints are recomputed by the server; private keys pasted by mistake are rejected.
- Sensitive buffers are wiped after use (as far as JavaScript allows).
- Dependencies locked with
package-lock.json.
A limitation to be aware of
A web application is served by a server: if that server were compromised, it could serve modified code. For very sensitive use, prefer installed and verified tools (GnuPG, age) or a self-hosted, verified copy of HashTag. Signed releases are planned.
Reporting a vulnerability
Contact MecDu.Dev via mecdu.dev. Please don't disclose the issue before it is fixed.