Security & compatibility

Private folders. Clear limits.

Trust starts with knowing exactly what a tool protects—and what it does not. These are the current, development-stage facts about FoldCrypt.

Local workflowAES-256 by macOSRecovery keyNo cloud required

Local by design

FoldCrypt is designed to protect the folder on the storage you choose. No FoldCrypt cloud account or cloud storage is required.

AES-256 by macOS

The development build uses encrypted sparse images created by macOS. FoldCrypt coordinates the workflow around them.

Password not stored

The password is passed to the macOS encryption process and is not saved by FoldCrypt. Choose a strong, unique password.

Recovery is your responsibility

A recovery key is shown when protection is created. Store it separately: without the password or recovery key, the data cannot be recovered.

Protection boundary

FoldCrypt protects locked folders—not the whole Mac.

  • Open folders remain readable by anyone who can access them.
  • FoldCrypt does not provide per-person identities, permissions, or centralized team administration.
  • Malware, a compromised Mac, weak passwords, and an already-open folder remain risks outside the locked container.
  • Encryption protects access. It does not protect against drive failure, deletion, corruption, or the loss of every backup.

Compatibility status

The verified matrix comes before release.

FoldCrypt is being built for shared Mac SSD, hard-drive, and RAID workflows. Compatibility testing is still in progress; the final macOS, architecture, drive, and file-system list has not been published yet.

Until public testing opens
  • There is no public app download.
  • Do not rely on an unfinished build for critical data.
  • Keep a separate, verified backup.
  • Test an exact workflow on non-critical material first.

Release gate

Signed, notarized, tested—then downloadable.

The public build will appear only after the release checks and compatibility documentation are ready.

View release status