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 to have one of your already-enrolled devices online and signed in. It will re-wrap the share for the new device in the background, and the folder opens on the next try. If none of your other devices can come online, write to us before you remove any of them.

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.

Their next unlock is refused. A folder they already have open locks itself as soon as the revocation reaches their device, and within minutes if that device is offline.

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

When you lock it, when you quit ZapLock, when the machine sleeps, and when it loses its connection for longer than the timeout you set. ZapLock re-encrypts whatever changed while it was open.

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 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.

In development. A folder you lock today will open in it when it ships — the vault format doesn't change.

From inside the app, under Danger Zone in settings, or from 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.