The short answer: An AI agent can usually open any file your user account can open, unless that tool's own settings stop it. Ignore files and deny rules only bind the tool that reads them, and their own docs list gaps, such as terminal commands or scripts the agent runs. Encrypting the folder at rest works for every tool at once: while ZapLock has it locked, an agent that opens the folder finds only ciphertext, file names included. Unlock it in place and it's an ordinary folder again, for AI tools too, until you lock it.
Why ignore files aren't a wall
Each AI tool has its own way to skip files, and each one stops only itself. Here's what each tool's own documentation says.
| Tool | Its own setting | What its docs say it doesn't cover |
|---|---|---|
| Claude Code | Read and Edit deny rules in settings | They apply to its file tools and to commands that name a file, such as cat. They don't apply to a command that reads files without naming them, such as grep -r, or to a script the agent runs. For enforcement at the OS level, the docs point to its sandbox. |
| Cursor | .cursorignore | The terminal and MCP server tools used by Agent can't block access to ignored files, and Cursor says complete protection isn't guaranteed. |
| GitHub Copilot | Content exclusion | Set by an organization on Copilot Business or Enterprise. Not supported in the Edit and Agent modes of Copilot Chat. |
| OpenAI Codex | Filesystem deny entries in a permission profile | In beta. They apply to sandboxed local commands. Connectors, MCP servers and browser or computer use have their own controls. |
| JetBrains AI Assistant | .aiignore | JetBrains says ignored files may still be processed in some cases, due to unforeseen issues. |
| Any other agent or indexer | Whatever it ships with | You have to find and maintain each one. |
These settings are still worth using. But a setting in one tool does nothing about the next one you install, and ZapLock doesn't ask which tools you use.
The protection is in the files, not in each app
Encrypted in place
The folder keeps its name and path, so links, sync and backups keep working. Its contents become AES-256-GCM ciphertext.
Names are encrypted too
An agent listing a locked folder sees encrypted file names and ZapLock's own marker files, not your documents.
We can't open it either
Each folder's key is split between your device and our service. Neither half opens anything alone, so our half decrypts nothing.
It also locks itself: when you quit ZapLock, when it's idle past the auto-lock time you set, and on a Mac when it sleeps or its screen locks. See the guide for the full list.
Two ways to open a locked folder
Open one file in the app Only that file gets a temporary readable copy, removed on lock The folder itself stays encrypted.
An ordinary folder again
For every app on that computer,
AI tools included
Until you lock it again. Use it when
you want an AI tool on those files.
Which folders to lock, and which not to
- Client files and contracts on the same laptop where your coding agent runs
- Finance, tax and HR folders
- Scans of IDs, passports and other personal records
- Another client's project you aren't working on today
Not the project your agent is working in: ZapLock can't lock a folder that's in active use, a system folder or an app bundle, or a folder inside another locked folder. For secrets inside the repo you're working on, use that tool's own deny rules or a secrets manager.
ZapLock isn't a sandbox. It doesn't control what an agent clicks, types or runs, and it doesn't protect a folder while you've unlocked it in place. For that, use a container, a separate user account or the tool's own sandbox.
How to keep AI agents out of a folder
With ZapLock on a Mac, a Windows PC, an iPhone, an iPad or an Android phone.
Install ZapLock and sign in
Get it from the Mac App Store, Microsoft Store, App Store or Google Play, and sign in with a free ZapQR account.
Sign in on a second device
Each device holds its own share of a folder's key, so a second signed-in device means losing one doesn't lock you out.
Lock the folder
On a Mac, right-click it in Finder and choose Services → Protect with ZapLock. On Windows, right-click it in File Explorer and choose Protect with ZapQR. On iPhone, iPad or Android, tap + or Add folder… and pick it.
Run your AI tools as usual
While the folder is locked, any tool that opens it finds encrypted names and contents. Browse a file inside ZapLock, or unlock it in place, when you need it.
When someone leaves, their access goes with them
With ZapLock Team, removing a person deletes their share of every team folder's key on our side, so their devices can't open those folders again. How offboarding works. Team is $9 per seat a month, or $7.50 billed yearly, with a 3-seat minimum. See pricing.
What ZapLock won't do
Worth knowing up front, so nothing surprises you later.
- You need a free ZapQR account. That sign-in is what replaces the password.
- Opening a folder needs a connection to our service, which releases its half of the key. A new unlock waits until you're back online.
- If a folder's key lives on only one device and you lose that device, the folder can't be opened. Sign in on a second device before you lock anything you can't lose.
- No Linux, and the apps aren't open source.
- Sync services keep version history. If plain copies were ever synced, your provider may still hold them.
Blocking AI agents from your files: FAQ
How do I stop AI agents from reading my files?
Use each tool's own exclusion setting where it has one, and encrypt the folders no tool should see. A locked ZapLock folder reads as encrypted names and contents to every app, so you don't depend on each tool honoring its settings.
Can Claude Code or Cursor read files outside my project folder?
Coding agents run with your user account's permissions, so depending on the tool, its settings and the commands it runs, they may be able to. A folder ZapLock has locked stays encrypted wherever the agent looks.
Is .gitignore enough to keep AI tools away from files?
No. .gitignore tells git what not to track. Whether an AI tool also skips those files depends on the tool and the feature, so it isn't a security control.
Do .cursorignore or deny rules protect files from every AI tool?
No. Each one applies only to the tool that reads it, and the tools' own docs list gaps, such as terminal commands or scripts the agent runs.
Can AI tools read a ZapLock folder?
Not while it's locked. They see encrypted file names and contents. Once you unlock it in place, it's an ordinary folder for every app on that computer until you lock it again.
Does it work with Copilot, Claude, ChatGPT or other AI apps on my computer?
Yes. ZapLock needs no integration or per-tool settings, because the protection is in the files themselves.
Can I still use an AI tool on a locked folder's files?
Yes. Unlock the folder in place, or open one file with Browse inside ZapLock, which makes a temporary readable copy of that file only and removes it when the folder locks.
Is ZapLock a sandbox for AI agents?
No. It protects folders. To limit what an agent can run, use a container, a separate user account or the tool's own sandbox.
Can ZapLock or DaSecure open my files?
No. Each folder's key is split between your device and our service, and our half alone decrypts nothing.
Is it free?
Yes, for one folder. ZapLock's Free plan locks one folder for good on Mac, Windows, iPhone, iPad and Android, and opening folders is always free. Personal adds unlimited folders and sharing with up to 3 people. See pricing.
Lock your first folder in a minute.
Free for one folder, for good. On Mac, Windows, iPhone, iPad and Android.
Built-in options checked 9 November 2026 against: Claude Code permissions · Cursor ignore files · GitHub Copilot content exclusion · OpenAI Codex permissions · JetBrains AI Assistant .aiignore.