Built on Sign in with ZapQR

Lock any folder. It stays exactly where it is.

ZapLock encrypts every file in a folder you choose, in place, keeping the folder's name and its path. Unlock it with a ZapQR sign-in. Share it with someone and take that access back in seconds.

Coming soon. ZapLock 1.0 is in review for the Mac App Store, the App Store and Google Play. A Windows version is in development.

macOS · iPhone · iPad · Android · AES-256-GCM

ZapLock ~/Clients/Board-Pack-Q3

minutes.docx unlocked

forecast.xlsx unlocked

lock

minutes.docx encrypted

forecast.xlsx encrypted

Same name. Same path. Nothing moved.

How it works

Three steps. No new drive.

Protect

Pick a folder — on your disk, a USB drive, or inside the folder Dropbox or Google Drive syncs. Its contents are encrypted where they sit, and the plaintext is removed as each file is written back.

Unlock

Sign in with ZapQR. Choose in place and it behaves like a normal folder again for every app on the machine, or open files one at a time from inside ZapLock.

Lock

Lock it, quit, sleep or walk away and ZapLock re-encrypts whatever changed. Lose your connection and an open folder locks itself after a few minutes — you choose how many.

Why it's not another vault

Disk images and vault folders make you move your work somewhere else and remember it lives there. ZapLock doesn't.

The folder never moves

No disk image, no separate vault location, no new drive letter. The folder keeps its name and its path, so the things that already point at it keep working — including the sync client that carries it to your other machines.

We can't open your folders

Files are encrypted with AES-256-GCM. The key is split: one half stays in your device's secure hardware, the other is released by ZapQR only while your sign-in and your access are both valid. We hold one half and cannot decrypt anything with it. File contents and file names never leave your device.

Take access back

Share a folder with anyone who has a ZapQR account; they unlock it on their own device. Remove them and their next unlock is refused — a folder they have open locks itself as soon as the revocation reaches their device, and within minutes if it is offline. Revoking a session from your phone locks every machine signed in with it.

One folder, every platform

One documented vault format, versioned and held to a shared set of test vectors by every ZapLock app we build. A folder locked on a Mac opens on an iPhone, an iPad or an Android phone — and on a Windows PC when that app ships.

One thing worth knowing. ZapLock encrypts a folder from the moment you protect it. If that folder already syncs to Dropbox, Google Drive or iCloud, those services may still hold earlier, unencrypted versions of the files in their own version history. Clear that history through your provider if it matters to you.

Part of the DaSecure platform

Your sign-in is the key

ZapLock is the first thing that ZapQR identity actually opens. It isn't a separate account, a separate password or a separate app to trust — the sign-in you already have is what releases the key.

ZapQR ──▶ ZapLock

A ZapQR sign-in releases the server half of the key. End that session and every folder it opened locks.

ZapLock ──▶ iotPush

Unlocks, new devices and revocations can land on your phone as a notification you can act on.

One account ──▶ every product

The same ZapQR account signs you into ZapLock, your site, and the DaSecure consoles.

See the whole platform →

Your account

What we hold, in plain terms

ZapLock uses a free ZapQR account to prove who you are and to hold the server half of each key. It never stores your files or a whole key.

Delete your account and data → Privacy policy → Terms of service → Support →

# stored on our servers

email address

account identifier

device id + public key, per device

vault id + label, per folder

encrypted key share, per vault

# never stored

your files

your file names

a whole key