Privacy
Where your files live, and what leaves the machine. Reviewed 2026-10-17.
Your files
Writ opens a text file up to 524 MB anywhere on your disk and edits it where it is. It also keeps a folder of its own,
~/Writ unless you moved it; Settings → General → Folder shows the path. New
files and anything you pipe into the writ command land there, and search covers its text files up to
5 MB each, leaving out folders such as .git, .obsidian and .trash.
Writ's data folder
Writ keeps its own records in ~/.writ, which Settings → Advanced also shows. Among
them:
-
writ.dbholds the search index, which stores the text of each file search covers so search can find it, along with the links, tags and properties read from those files, the paths and order of your tabs and of the files you closed, and each file's preview layout. It also holds text you typed that had not reached its file, such as after a refused save or when Writ quit, until a later save or the next launch puts it on disk. config.tomlholds your settings. It holds no API key.-
history/andhistory.dbhold earlier versions of the files in the folder, so a bad edit or a program's write can be undone. Writ keeps a version when a file is saved, except for your own saves within 10 seconds of the last version kept, for up to 30 days or 200 versions per file, and no more than 250 MB in all. A file's newest version is kept past 30 days. A file over 2 MB is not versioned. -
chats/holds one file per conversation: your messages, the replies, the edits a reply proposed, and the paths and sizes of attached files. It keeps no copy of an attached file and no key. A proposed edit is kept as the whole text the reply proposed for that file, until you apply or discard it. activity.jsonllists what connected programs and chat did with your files, without their text.logs/records what the app did, and can name the files it worked on. Logs rotate daily, and the newest 14 are kept. Crash files, up to eight a run, stay until you delete them.
None of this is written into your folder, so a sync client never carries it.
What the app does on the network
Until you switch on Chat or Rewrite, Writ itself contacts only GitHub, for updates: it fetches a release manifest
and compares versions on your machine. It does this on its own shortly after launch, at most once a day,
and whenever you ask in Settings → About. Turn the automatic check off with
Check for updates automatically. Installing an update downloads the release from GitHub and checks it
against a signing key built into the app. Both requests go to github.com, which redirects them to
release-assets.githubusercontent.com.
Spell check runs against a dictionary bundled in the app. The preview pane runs under a fixed
content-security-policy (default-src 'none', connect-src 'none'), so rendered HTML makes
no network calls while scripts are off for that file, as they are until you turn them on for it. A file whose
scripts you turn on runs its own code, which can reach the network. Writ sends no crash reports, usage data or
telemetry.
The AI connection
Chat and Rewrite are apps you switch on in Settings → Apps. While either is on, the same
section holds the connection they share: provider, address, API key and model. Ollama, LM Studio, llama.cpp and
Jan run on your machine and need no key, so a request to any of them stays there. On macOS 26, on a Mac that
can run it, Rewrite can also use Apple's on-device model, and Writ makes no network request for it.
Point the connection at a hosted provider and Writ asks once, naming the host, before it sends that host
anything. The hosted providers are Anthropic (api.anthropic.com), OpenAI (api.openai.com), Google Gemini
(generativelanguage.googleapis.com), OpenRouter (openrouter.ai), Groq (api.groq.com), DeepSeek
(api.deepseek.com), Mistral (api.mistral.ai), xAI (api.x.ai), Together (api.together.ai) and Fireworks
(api.fireworks.ai); a custom address goes to the host you typed. The answer is recorded for that host alone, so
it does not cover another host, whether a provider's or one you typed. An address that is not https
is refused before any bytes leave, unless it is this machine or a private IP address, such as one on your local
network or Tailscale. Writ asks before it sends anything to a private address, and sends no key over plain http.
To show whether the provider is reachable, Writ requests its model list. That request carries your API key and no text, and goes to a hosted provider only after you allowed it. Settings and the chat pane also ask Ollama, LM Studio, llama.cpp and Jan on this machine (ports 11434, 1234, 8080 and 1337) whether they are running; that request carries nothing.
Connecting OpenRouter opens openrouter.ai in your browser. Writ listens on this machine for the one answer that browser sends back, then exchanges it for a key and stores the key like one you typed. No port is open at any other time.
Rewrite
A rewrite sends the selected text, the instruction for the action you picked, and the model id. With nothing selected, Writ asks before sending the whole file.
Chat
A chat request carries a fixed instruction, the files attached to the conversation, the conversation so far and
the model id. The pane attaches the file in front of you and shows it as a chip you can remove; you add others
with @ or by attaching a folder. Any file open in the editor can be attached, including one outside
your folder, which is sent under its parent folder and file name, never its full path. Nothing that is not
attached is read for a request.
Chat writes a file only when you choose Apply on a proposed edit, and no setting applies one for you. If the file changed after the edit was proposed, Writ refuses to apply it. The proposed text stays in the conversation. If Apply finds a file in your folder changed since the edit was proposed, the proposed text is also saved beside it as a dated copy.
Connected programs
Writ ships an MCP server, writ mcp, so a program you choose can work with the files in your folder.
Connected programs is an app you switch on in Settings → Apps, which also shows the command to
give the program. The program starts the server itself and talks to it over that process's input and output.
Writ opens no port for it, and the server makes no network request. Where that program sends what it reads is up to
that program.
Switching the app on approves nobody. A program's first call is refused and waits in Settings until you approve
that program. Reading, writing and seeing the open file are approved separately; writing includes reading, and
nothing else grants another. Each can be withdrawn in Settings or in config.toml and takes effect on
the next call.
With reading approved, a program has ten tools: list the folder's text files, search the folder, read a file,
read a file's links, backlinks, properties and tags, list the folder's tags, and show a file in Writ at a line or
a heading. With writing approved, it has six more: replace a file's text, create a file, rename one, add to the end of
a file, replace one passage, and make or add to today's file. No tool deletes a file. A write is checked against the
version the program read: it is refused if the file changed since, and the program's text is saved beside the
file. A file the program has not read is not replaced unless it asks to overwrite it, and the text a write
replaces is kept as a version in Writ's data folder. A file outside your folder is out of reach of these tools,
unless the program starts the server with WRIT_NOTES_DIR naming another folder. A write to a file
outside your folder keeps no version.
With Open file turned on for it, a program can ask which file is in front in Writ and read the text you selected there, including text not saved yet. A file outside your folder is named to it by its file name alone. Writ asks the window only when the program calls, hands the answer over in a file in its data folder that the server deletes once read, and lists each call in the activity list with the file's name and not the text.
The activity list
Every call from a program, whether it was allowed, refused or left waiting, and every chat edit you applied or
discarded, is appended to activity.jsonl. A record names the program, the chat or Writ, the tool, the file,
the decision and, for a write, a byte count, never the text. Reads of one file that one program repeats within a minute
are counted on a single record. The file stays on your disk and is capped at 5 MB with one
older generation kept. While Connected programs is on, open it from
Settings → Apps → Connected programs → Program activity.
Keys
On macOS, Windows and Linux, Writ stores an API key in the system keychain (the Secret Service on Linux) under
the service com.writ.ai.
Where the keychain is unavailable, Writ holds the key in memory for the session and warns that you will enter it
again next time. A key is never written to config.toml, the database or a log.
What this site does
This site is a static export served from GitHub Pages, and it serves its own font. It counts page views with a self-hosted Umami script from stats.ibrahemid.com, which it tells to honor Do Not Track. It sets no cookies and embeds no third-party widgets.
Backup and deletion
Back up your folder and any file you keep elsewhere; Writ's data folder is not a backup of them. Writ can rebuild
the index in ~/.writ from the folder. Nothing else in ~/.writ can be rebuilt:
settings, earlier versions, conversations, the activity list, your tab list, and text in writ.db
that had not reached its file.
Delete ~/.writ to reset the settings and records kept there. The sidebar's open folders and the
pane layout are kept apart, in the web view's storage (~/Library/WebKit/com.writ.editor on macOS).
Your folder and every file you opened elsewhere
stay untouched. An API key is not in that directory: clear it from your keychain, or from
Settings → Apps while Chat or Rewrite is on.
Source of truth
Everything above about the app is in the repository, github.com/ibrahemid/writ, with the decisions on what leaves the machine in ADR-031 and the checks in the threat model. If you find a network call this page does not describe, file an issue and it will be treated as a bug.