Privacy Policy

Effective: June 1, 2026

Short version: Wren is local-first. Your notes live on your own computer (or in your own Google Drive if you connect it). Wren does not have a server, does not collect analytics, and does not see your notes. Read on for the details.

What Wren is

Wren is a sticky-notes application that runs entirely in your browser. It is a Progressive Web App (PWA), also available as a native desktop app. Notes are stored as Markdown files either on your local computer (via the File System Access API) or in your own Google Drive (if you choose to enable Drive sync). Wren has no backend server.

What Wren collects

Wren collects no personal data on any server because Wren has no server. Specifically:

No analytics, telemetry, or usage tracking.
No account creation. Wren does not store usernames, passwords, email addresses, or any other identifying information.
No cookies set by Wren itself.
No advertising, ad networks, or third-party trackers.

What Wren stores locally on your device

For Wren to function, it stores a small amount of information in your browser's local storage:

Notes folder reference. If you use local file storage, Wren stores a reference to the folder you chose (a FileSystemDirectoryHandle) in IndexedDB, so you don't have to re-pick the folder every time.
Theme preference. Your light/dark/auto choice is stored in localStorage so it persists across sessions.
A device identifier. A short random string is generated the first time Wren runs on your device, stored in IndexedDB, and used to name conflict-copy files when Drive sync detects edits from multiple devices. The identifier never leaves your device or your Drive.
Sync metadata (Drive only). If you connect Drive, Wren stores sync state per note (last synced revision, dirty flag) in IndexedDB so it knows what has changed and what to upload.

All of this lives in your browser's local storage. Clearing your browser data will remove it. Wren cannot access this data from any other device.

Google Drive integration (optional, experimental)

Wren stores your notes locally by default. Cloud sync via Google Drive is an optional, experimental feature you turn on yourself — it is off unless you explicitly enable it, and your notes stay on your own computer until you do. If you choose to enable Google Drive sync, Wren requests OAuth permission for the drive.file scope. This scope:

Lets Wren see, create, edit, and delete only files Wren itself created in your Drive. Wren cannot see your other Drive files.
Creates a folder named "Wren Notes" in your Drive on first sync. All Wren notes are stored as .md files in that folder.
Reads and writes only when you actively use Wren. There is no background sync from a server you don't control.

The OAuth access token Wren receives is held only in memory while Wren is running. The token is not stored in localStorage, IndexedDB, or any persistent location. When you close Wren, the token is discarded.

You can revoke Wren's access to your Drive at any time:

From within Wren: click "Disconnect Drive" in the settings (when Phase 2b ships).
From Google directly: visit myaccount.google.com/permissions, find Wren, and remove access.

Wren MCP server (optional)

Wren offers an optional companion app called the Wren MCP server that lets an AI assistant — currently the Claude Desktop app — read and create your notes through the Model Context Protocol (MCP). It is a separate program you choose to install; Wren works fully without it.

It runs entirely on your computer. The MCP server is a local program. It reads the notes folder you point it at, on your own disk, and returns results to your AI assistant over a local connection on your machine. It is not a website and has no server of its own.
Wren does not upload your notes. The MCP server sends your notes to no Wren server, no Build with Baker server, and no third-party server — there is none. The only information that leaves your computer is whatever you choose to share with your AI assistant in a conversation, exactly as in any normal chat with that assistant. Your assistant's provider handles that data under its own privacy policy (see "Third parties").
What it can do. Search and read your notes, and create new ones. Notes it creates are placed in a staging area (an _inbox folder) for you to review in Wren before they join your main notes. It does not edit or delete your existing notes.
No account or login. The MCP server needs no Wren account and stores no credentials. You point it at a folder — that is the entire setup.
Removing it. Uninstall it from your AI assistant's extension settings at any time. Nothing of yours is stored anywhere that would need deleting.

Third parties

Wren uses these third-party services. Each has its own privacy policy:

Google Identity Services and Google Drive API — only if you enable Drive sync. See Google's Privacy Policy.
Your AI assistant's provider — only if you install the optional Wren MCP server (for example, Anthropic, if you use Claude Desktop). Notes you share with the assistant in a conversation are handled under that provider's privacy policy. See Anthropic's Privacy Policy.
Your hosting provider — Wren is delivered to your browser as static files from a hosting provider. The host may log standard HTTP request information (IP address, user agent, timestamp). Wren itself does not log or aggregate this data.

Wren does not use Google Analytics, Google Fonts (fonts are bundled), Facebook Pixel, or any other tracking or analytics service.

Data retention

Because Wren stores nothing on a server, there is no retention period to disclose. Your notes are retained as long as you keep them, in the location you chose (your computer's filesystem or your Google Drive). If you delete a note in Wren:

Local storage: the .md file is deleted from your computer immediately.
Drive storage: the file is moved to Drive's trash (recoverable from drive.google.com for ~30 days, then permanently deleted by Drive's policy).

Children's privacy

Wren is not directed at children under 13. Wren does not knowingly collect personal information from children because Wren does not knowingly collect personal information from anyone.

Your rights

Because Wren collects no personal data and stores no data on any server, traditional GDPR/CCPA rights (access, deletion, portability, etc.) apply only to the data on your own device:

Access: all your data is in plain Markdown files on your computer or in your Drive. Open them in any text editor.
Deletion: delete the files directly, or use Wren's delete function. To remove Wren's local state entirely, clear your browser's site data for the Wren domain.
Portability: the .md file format is portable. Copy files to any other Markdown editor (Obsidian, iA Writer, plain text editor) and they will work.

Changes to this policy

If this policy changes, the "Effective" date at the top will update. Material changes (e.g., adding analytics, adding new third-party integrations) will be flagged in Wren's release notes.

Contact

Wren is built by Adam Baker under the Build with Baker creator brand. For privacy questions, contact bakeradm6@gmail.com or open an issue at github.com/buildwithbaker/wren/issues.