Help with ZapLock

ZapLock encrypts the files inside a folder you already have, where they already are. The folder keeps its name and its full path — ~/Clients/Board-Pack-Q3 stays ~/Clients/Board-Pack-Q3. There's no disk image to mount, no vault folder to move your work into, and no new drive letter.

When you unlock it and choose in place, every app on the machine sees an ordinary folder again. Aliases, recent-file lists, backup jobs and sync clients that already point at it keep working.

Any folder you can write to: on your internal disk, on an external or USB drive, or inside the folder Dropbox, Google Drive or iCloud already syncs.

Avoid pointing ZapLock at system folders, application bundles, or a folder an app is actively writing to (an open database, a running VM image).

Yes — a free ZapQR account. It's what proves who you are and what holds the server half of each folder's key. ZapLock never stores your files or a whole key. The full list of what we hold is on the privacy page.

A new device starts with no key share for your existing folders — signing in as the owner deliberately hands over no key material. The new device needs a share wrapped to its own key before it can unlock anything.

The fix is a device that already opens the folder. ZapLock for Mac hands the new device its key in the background while it is running and can reach the folder. On an iPhone or iPad, tap Hand over when ZapLock asks. On Android or Windows, unlock the folder there once. Then try again on the new device. If none of your other devices can come online, write to us before you remove any of them. The guide shows this step by step.

Share it to their ZapQR account by email address. They unlock it on their own device — you never send them a password, and you never send them the key. Sharing needs a Personal or Team plan. Opening a folder someone shared with you is free.

Their next unlock is refused. A folder they already have open locks itself as soon as the revocation reaches their device, and a device that is offline locks it once its offline timeout runs out.

Revoking a session from your phone locks every machine signed in with it.

When you lock it, when you quit ZapLock, and when it sits idle past the auto-lock time in Settings. A Mac also locks when it sleeps or its screen locks, and an iPhone or iPad locks as soon as you leave the app. A device that can't reach our server for longer than its offline timeout locks too. If you unlocked a folder in place, ZapLock re-encrypts whatever changed.

Yes. There's one documented vault format, held to the same test vectors by every ZapLock app we build, so a folder locked on a Mac opens on a Windows PC, an iPhone, an iPad or an Android phone.

ZapLock encrypts from the moment you protect the folder, and the plaintext is removed as each file is written back on your device. But a sync provider may still hold earlier, unencrypted versions of those files in its own version history. Clear that history through your provider if it matters to you.

Yes. ZapLock is on the Microsoft Store for Windows 10 (version 2004) or later. Right-click a folder in File Explorer to lock it. Folders you locked on a Mac, iPhone, iPad or Android phone open on Windows too — it's the same vault format.

On a Mac, iPhone or iPad, in the app under Danger Zone in Settings. From any device, including Android and Windows, on the web at zapqr.ai/delete-account.

Unlock anything you still want to read before you delete. Once the account is gone, the server half of every key goes with it, and a folder still locked cannot be opened again by anyone — including us.

Sign in on another device and revoke the lost device's session. Every folder that device had open locks itself once the revocation reaches it, and its key share stops being released.