w3myPQ – ML-KEM + AES-GCM + ML-DSA

High-security, privacy-focused post-quantum file encryption and sharing tool for WordPress

The standalone BPQ tool and the w3myPQ plugin for WordPress use cross-compatible file format

How to

Generating Post-Quantum Keypair

Before you can securely encrypt or receive files, you must generate your cryptographic identities.

Important: after generated you must download and back up your keys immediately. If you lose them, you lose access to your encrypted files forever (ML-KEM Private key).

Navigate to the w3myPQ Get Keys screen and click into Generate keys.

The browser engine will generate a post-quantum keypair: ML-KEM (for encryption) and ML-DSA (for digital signatures).

Profile Saving (For Logged-in Users): If you are logged into your account, you have the option to save your public keys directly to your profile for seamless future interactions, though this is entirely optional.

File encryption on the device

Guest mode

You can use w3myPQ as a guest to securely encrypt files for your own personal backups, without specifying a recipient’s public key. In this mode, the tool operates entirely client-side: neither your raw files nor your encrypted files are ever uploaded to the server. You can also use the BPQ single standalone HTML file: it is a zero-trust, post-quantum cryptography tool using the same w3Gemini Engine that you can use to encrypt/decrypt files.

If there is auto-loaded from your user profile you can use your profile saved public key, or substitute it uploading the ML-KEM public key that you want to use to encrypt the files. You must make sure you possess the corresponding private key for this public key, as it will be required later for decryption.

You can optionally choose to sign the file using your ML-DSA private key before encryption. This embeds a tamper-proof cryptographic proof of authorship inside the file package.

Once your keys are ready, select the files you want to encrypt from your computer or smartphone. The browser will instantly load them into an isolated, local memory thread and start the encryption.

The code processes the data entirely in your browser’s isolated memory. It seals the file with AES-GCM and wraps the access key using your loaded ML-KEM parameters. As soon as the routine finishes, you can download the encrypted package (a .txt file) directly back to your device.

When you want to access (decrypt) your file again, navigate to the related Decrypt tool screen. First, provide your corresponding ML-KEM private key (or load it via your nest.txt vault phrase) to prepare the browser environment. If the file was signed during encryption, you can also (optionally) provide the ML-DSA public key at this stage to verify the signature and confirm the authenticity of the author. Once your keys have been loaded, upload your encrypted file package (.txt) to start the decryption process and restore your original files.

Secure user-to-user file sharing

Write the username or email into the Recipients field to search for or select the user(s) you want to send the file to. The system will automatically fetch their active ML-KEM public key from their user profile database.
Just like in Guest Mode, your browser processes the selected files entirely in isolated device memory. It seals the contents using AES-GCM and locks the decryption key using the recipient’s ML-KEM public key. Your raw files never touch the network or the server.

Once encrypted client-side, the browser uploads the ciphered binary blob (.txt payload) directly to the secure storage directory on the website’s server. The backend then automatically sends an email to the recipient(s) containing a direct link to the encrypted file(s). Recipients will need to follow the link and provide their private KEM key to decrypt them. As the sender, your email address will be automatically included; however, you can also directly download the encrypted payload.

Cincia keys vault

See the dedicated Cincia keys vault page on how to secure your private keys on your device!

Cincia keys vault

FAQ

Encryption limits

1. The Host System’s Hardware Profile today (2026)

Note: For pure, client-side, zero-dependency browser execution, the maximum realistic limit is around 1 GB to 1.5 GB. However, this limit depends entirely on two critical factors:

• Desktop Environments: A machine with 16 GB+ of RAM can easily push past the 1.5 GB boundary because desktop operating systems allow web browsers to leverage massive virtual memory swap pools.
• Mobile Devices: Even flagship smartphones boasting 12 GB–16 GB of physical RAM are strictly throttled. Mobile operating systems (iOS and Android) enforce a hard sandboxed memory ceiling per browser tab—usually capping a single process at 1.5 GB. Exceeding this causes the browser tab to crash instantly to protect the device’s stability.

2. Browser Sandbox Memory Architecture

Because w3myPQ operates on a True Zero-Knowledge framework, all compression, binary header mapping, and post-quantum ML-KEM-1024 calculations happen entirely in-memory within the browser’s local sandbox space. The data is never offloaded to a heavy backend server. Therefore, the browser must hold both the raw file buffers and the newly generated encrypted binary objects simultaneously in its internal memory heap structure.

Security tips

To make sure your Private keys files remain absolutely un-cracking and leaving no trace while sitting on your filesystem, keep these rules in mind:

Always use a long passphrase: The 700000-loop slowdown relies heavily on entropy. A phrase with 5-6 random words Upper and lower case makes your local nest.txt file mathematically irreversible.

Eg: Correct Horse Battery Staple Purple or Blue Sky Running Fast Turtle

Want zero local temporary traces? Run Firefox in Private Browsing mode.

When you use Firefox in Private Browsing mode, the browser does not save your browsing history, cookies, search history, or temporary cached files to your disk.

Here is exactly how it handles memory and data:

• Volatile Memory (RAM): While the private window is open, it keeps active session data (like temporary cookies and cache) in your computer’s short-term memory (RAM).
• Automatic Cleanup: As soon as you close all private windows, Firefox immediately wipes this data from the RAM and completely cleans up the session.

---

USE FIREFOX 🦊