Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Anzi001/Secure-Crypt/llms.txt

Use this file to discover all available pages before exploring further.

Sharing sensitive files over email, cloud storage, or a USB drive no longer requires trusting the transport medium. Once you lock a file with Secure Crypt, the resulting .scrypt or .scryptfold archive is opaque ciphertext — only someone with both the file and the correct password can read it. This guide explains how to prepare your recipient, what to include alongside the encrypted file, and how to use the Force Lock flag to control whether recipients can permanently decrypt what you send them.

​
What the recipient needs

A recipient needs three things to open a Secure Crypt encrypted file:
1

Download and install Secure Crypt

The recipient must download the standalone executable for their operating system from the official releases page:
https://github.com/Anzi001/Secure-Crypt/releases
No Python installation is required — Secure Crypt is distributed as a self-contained executable for Windows (.exe), macOS, and Linux.
2

Receive the password through a secure channel

The password must be shared separately from the encrypted file — never in the same email, chat message, or upload. Deliver it verbally, via a phone call, a separate encrypted messaging app, or any other channel that is independent of the one carrying the file.
3

Receive the .scrypt or .scryptfold file

Send the encrypted file via your chosen transport (email attachment, cloud storage link, USB, etc.). Because the file is ciphertext, it is safe to send over untrusted channels.

​
Explaining encrypted files to recipients

Recipients who have never used Secure Crypt before may not know what a .scrypt file is or what to do with it. The repository includes a ready-made plain-text template you can include alongside your encrypted file: README (Message from file sender).txt 
The enclosed files have been secured with Secure Crypt file encrypter/decrypter free to download on GitHub.
To unlock the enclosed file, use the enclosed access code sent by the sender of this file.
After installing Secure Crypt decrypt your file using the Secure Crypt.
To proceed with the installation, download the latest release from
https://github.com/Anzi001/Secure-Crypt/releases
Copy this file into the same folder or attachment as your encrypted file. It tells the recipient exactly what software they need, where to get it, and that they should have received a separate access code (password) from you.
Secure Crypt encrypted files carry no metadata about the original file’s contents inside the binary blob itself. The original filename is encoded entirely in the .scrypt filename — for example, contract_final.pdf.scrypt decrypts to contract_final.pdf. Recipients can therefore infer the file type and name just from the archive name before they ever enter a password.

​
Sending a force-locked file

The Force Password Every Time checkbox in Secure Crypt enables Mandatory Lock mode. When you lock a file with this option enabled, an M flag byte is written at position 0 of the encrypted archive. This flag is permanent and cannot be stripped without knowing the password.
A recipient who receives a force-locked (mandatory-lock) file can only open it via Quick View — they must enter the password every time and can never produce a permanently decrypted copy on their disk. The UNLOCK FILE and UNLOCK FOLDER buttons will refuse to process the file and show an error dialog titled “Access Denied” with the message “Mandatory lock. Use Quick View.”This is useful in scenarios such as:
  • Read-only sharing — you want the recipient to read the document but not retain a plaintext copy.
  • Time-limited access — you intend to revoke access later by changing the password (by doing a Quick View relock with a new password yourself).
  • Policy enforcement — you want every access to require an explicit password entry, leaving an implicit audit trail.
When sending a force-locked file, tell the recipient in your password delivery message that they should use the ⚡ QUICK VIEW FILE or ⚡ QUICK VIEW FOLDER button, not the Unlock buttons.

​
Password security best practices

Use strong passwords

Use long, random passwords — a mix of uppercase letters, lowercase letters, numbers, and symbols. Avoid dictionary words or anything guessable. A password manager can generate and store these for you.

Use a separate channel

Never send the password in the same email, message, or upload as the encrypted file. If an attacker intercepts the file transfer, they should not also have the password. Use a phone call, a separate app, or an in-person handoff.

Use per-recipient passwords

If you are sending the same file to multiple recipients, lock a separate copy for each recipient with a unique password. This limits exposure: if one recipient’s password is compromised, the other copies remain safe.

There is no recovery

Secure Crypt has no password recovery, hint system, or escrow. A lost password means the encrypted file is permanently inaccessible. Store passwords in a password manager or a secure physical location before locking important files.

Build docs developers (and LLMs) love

Get started for freeTalk to us