Data and privacy: does NearWork upload my files?
Updated 2026-11-12
The short answer: your files, sessions, memory, knowledge base and API keys stay on your machine. What actually leaves the computer is the slice of context you send to a model provider when you run a request.
What is stored locally
All user data lives under one root, LINGXI_HOME (default ~/.LingXi; on Windows C:\Users\<you>\.LingXi; an environment variable can move it to another drive):
| Path | Contents |
|---|---|
config.json | Model slots, providers, permission mode, reasoning depth |
auth.json | Your NearWork sign-in, shared by the desktop app and the CLI |
sessions/, session/ | Session transcripts and the session index |
memory/ | Long-term memory and the knowledge base, including chunks and vectors for imported documents |
skills/, mcp.json, hooks.json | Skills, MCP servers, hooks |
tasks/, teams/ | Scheduled jobs and team data |
log/, backups/, screenshots/ | Logs, backups, screenshots |
None of it is uploaded automatically. To wipe everything, quit the app and delete the whole LINGXI_HOME directory (irreversible — back it up first).
What leaves the machine
| Action | Where the data goes |
|---|---|
| Sending a message | The context, including any file you attached, goes to the provider selected for that slot |
| Using official credits | Requests pass through the NearWork relay (for auth and metering) and on to the upstream model |
| Using your own API key | Requests go straight to that provider's endpoint; NearWork is not in the path |
| Web search / fetch | Keywords or URLs go through the official relay, then to the upstream search service |
| File I/O, command execution, browser control | All local; nothing goes to a server |
| Speech recognition / synthesis | With a networked service, the audio goes to the provider you selected |
Put differently: inference needs the network, your whole dataset does not go to the cloud. If a particular file must not leave the machine, do not attach it, or point the slot at a locally hosted model.
How API keys are stored
On desktop, keys are encrypted with the operating system's own facility (Electron safeStorage: DPAPI on Windows, Keychain on macOS) before being written to config.json; plaintext never touches disk, and the UI hides them by default.
That has one practical consequence: the ciphertext is bound to the current OS account. Copy config.json to a new machine or a reinstalled system and you must re-enter the key once. Other data — sessions, memory, skills — is unaffected.
The CLI prefers environment variables (for example DEEPSEEK_API_KEY), which belong in your shell profile or a secret manager — never in a git repository.
You set the permission boundary
NearWork asks before writing files, executing commands or driving a browser. Four modes:
| Mode | Behaviour |
|---|---|
normal (default) | Read-only automatic; writes and commands confirmed |
strict | Confirmed at every step |
auto | Fully automatic; dangerous commands still blocked |
full_access | Nothing is confirmed |
Use auto and above only for controlled, reversible work; keep normal when the working directory is production.
Frequently asked questions
Are my conversations used for training?
The client does not upload sessions on its own. With official credits the request body passes through the NearWork relay for auth and metering. If your requirements are strict, switch to "own API key + direct connection" and evaluate that provider's data policy — or go further and point the slot at a locally hosted model so inference stays inside your network.
Can I use it on a corporate or classified machine?
Yes, with the right configuration: bring your own key and connect directly, point LINGXI_HOME at an encrypted volume, keep permissions at normal, turn off web-search tools, and use local models if needed. Everything except inference itself then stays on the machine.
How do I migrate to a new computer, and must I retype the key?
Copy the whole LINGXI_HOME directory and sessions, memory, knowledge base, skills and MCP config come along. Because key encryption is tied to the OS account, re-enter the key once under Settings. The NearWork sign-in (auth.json) can usually be reused as is.
Is my data deleted when I uninstall?
Uninstallers generally leave LINGXI_HOME in place, precisely so a reinstall does not eat your sessions and knowledge base. Delete the directory yourself when you are sure.
Next steps
- Connecting external tools? Read the security notes in the MCP guide.
- Not comfortable with permission modes yet? Go back to the quick start.
- Billing and credit rules are on the pricing page.
