Privacy Policy
Your Mac. Your data. Your control.
Wren is built around a simple rule: your personal workspace lives on your Mac, and anything that leaves it does so because you asked, using a connection you chose. This policy explains exactly what that means today, including the limits.
1. What this policy covers
This policy covers the Wren website and the Wren app for macOS. Wren is an independent project developed by Shibaditya Deb. It isn't a company, and there is no Wren server, account or cloud service: the app runs on your Mac and talks directly to the services you connect.
Wren is in development. Some features described here are built but not yet available in a released version, and some are still being completed; where that matters, this policy says so. If something here no longer matches the app, the app's source code is public on GitHub, and this policy will be corrected.
2. The Wren website
- The website is a set of static pages. It has no cookies, analytics, advertising or tracking scripts, and it doesn't store anything in your browser.
- Fonts, images and scripts are served from the same site. It loads nothing from other companies' servers.
- Downloading the app asks you to sign in with Google. Sign-in runs through Supabase Auth, the service that keeps Wren's download list, and Google's own sign-in page. Google tells Supabase your name, email address and profile picture link, and Supabase keeps your account record (those details and when you signed in), as described in Supabase's privacy policy. Wren's download list keeps your name, email address, the version you downloaded and the date. It's used only to know who is trying Wren and to contact early users about important fixes; it isn't sold, shared or used for advertising, and the website can't read it back. The sign-in token Supabase returns is used once by this site to record the download and isn't stored. To have your entry and account deleted, contact the developer through GitHub.
- The app itself never uses that sign-in; it has no Wren account.
- The site is hosted on Vercel. Like any web host, Vercel receives the standard information your browser sends with each request, such as your IP address, the page requested, the time, and your browser's user-agent, and may keep it in its logs to run and protect its service, as described in Vercel's privacy notice. Vercel's optional visitor analytics and performance tracking are not turned on for this site.
- Links to GitHub take you to GitHub, which has its own privacy policy.
The product illustrations on the website are mockups with fictional content. The website never connects to your calendar, email or AI accounts.
3. The Wren macOS app
Wren stores its data in your user Library on your Mac, in ~/Library/Application Support/Wren, and its preferences in macOS's standard preferences for the app. Nothing is synced to iCloud or to any server of Wren's own, because there isn't one.
Wren connects to the internet only for things you set up or ask for:
- ChatGPT (
auth.openai.com,api.openai.com), when you connect your OpenAI account and send a request. - Google (
accounts.google.com,oauth2.googleapis.com,gmail.googleapis.com,www.googleapis.com), when you connect Gmail or Google Calendar. - Notion (
mcp.notion.com), when you connect Notion. - Your own local AI (Ollama at
127.0.0.1, on your Mac), if you set it up.
Each connector only talks to its listed addresses; Wren refuses any other. Opening links (for example “Open in Gmail” or “Manage usage”) opens your browser.
4. Tasks, reminders, goals, history and preferences
Stored on your Mac, in Wren's database (Wren.store):
- Everything you capture, with your original wording, its interpreted title, dates, reminders, recurrence, status and history.
- Goals, waiting items, follow-ups and the observations Wren showed you.
- Records of GPT requests you sent: what you said, what was sent, the answer, the model names, times and status.
- An activity log of actions taken and why they were allowed. It holds short labels rather than full content: for example an item's title, the first 80 characters of a GPT request, or “Email from” plus a sender's name.
- The permissions and standing rules you set.
Stored in the app's preferences: settings such as shortcuts, notification and digest times, quiet hours, important senders, an unsent capture draft, and each connector's status (the connected account's email or workspace name and the last error).
If the database can't be opened, Wren saves what you type to a plain text file (emergency-captures.txt) in the same folder so nothing is lost.
5. Voice and microphone
- Voice is optional and starts only when you press the voice shortcut or click a Voice button. Wren never listens in the background and has no setting to do so. macOS asks you for Microphone and Speech Recognition permission; you can withdraw either in System Settings › Privacy & Security.
- Wren uses Apple's speech recognition in on-device mode, and refuses to run if on-device recognition isn't available for your language. Apple's on-device recognition processes speech on your Mac. Wren doesn't record or store audio.
- The microphone is used only while you hold the push-to-talk shortcut (up to 60 seconds; letting go ends it), or after you click Voice until you pause, press Stop or cancel (up to 30 seconds). It's off while Wren transcribes and runs the command, and it doesn't restart by itself. Locking your screen, putting your Mac to sleep or quitting Wren stops a recording.
- The recognised text is shown to you and handled exactly like typed text. It's kept only if it becomes an item or request you run.
The voice feature is still in development and hasn't yet been verified end to end with a real microphone.
6. AI providers and external processing
Local AI (optional)
If you install Ollama and choose a model, Wren sends the text of your captures to it on your own Mac (127.0.0.1) to understand them better. Nothing goes to an outside service.
ChatGPT (optional)
- By default, “ask GPT” opens the ChatGPT website in your browser and copies your request to the clipboard (or, if you turn on the experimental option, puts it in the page address). You send it there; it then belongs to your ChatGPT account under OpenAI's terms. Wren never reads your ChatGPT conversations. It stores a conversation's address only if you link it, reading the clipboard only when you click Link conversation.
- To run requests inside Wren instead, you connect by signing in on OpenAI's own page (“Sign in with ChatGPT”). Wren never sees your password.
- In that mode, the text of your request is sent to OpenAI with your account's authorization and counted against your ChatGPT plan. Wren asks OpenAI not to store the request (
store: false); OpenAI's handling of it is governed by OpenAI's terms and policies. - Only the request is sent. Wren doesn't attach your items, notes, email or anything else, unless you add specific context yourself in Delegate, which shows exactly what will be sent. Items you've marked private are left out unless you tick them for that request, and text that looks like a password, key or card number is removed unless you choose otherwise.
- Wren's background tasks never use your ChatGPT account. Email is never sent to ChatGPT or any other AI service.
- The answer is saved in Wren's database on your Mac, where you can open it later.
7. Google, Gmail and Calendar
In development: connecting Google isn't possible in current builds yet. This describes how it works once it is.
- You connect by signing in on Google's own page and choosing what to allow. Gmail uses read-only access (
gmail.readonly); Calendar uses read-only access (calendar.readonly). - Mark as read is a separate, optional permission (
gmail.modify) that you'd grant on purpose. Google's permission technically allows more changes than that, but Wren only implements marking a message as read, and only when you choose it for that message. Wren doesn't send, archive, delete or label email. - For your inbox, Wren reads the sender, recipients, subject, date, labels and Gmail's short preview of recent messages. It doesn't download full message bodies or attachments, and it never reads Spam or Trash.
- Sorting mail into categories happens on your Mac, by rules. Instructions written inside an email are treated as text and can never make Wren do anything.
- While Wren is running and you allow it, it checks your inbox every few minutes for new mail (only what changed since the last check), and it doesn't check when Wren isn't running.
- Recent inbox details are kept in a private file (
Mail/mailbox.json, readable only by your macOS user) so the inbox, digest and alerts work. Messages older than 30 days are removed from it. An optional 7-day cache of headers and previews is off unless you turn it on. Neither is part of Wren's database, exports or backups. - Calendar events are read when needed, from Google or from the calendars already on your Mac (with macOS's Calendars permission), and aren't stored by Wren.
8. Notion and Slack
Notion is not yet available. Early support exists in the code: you would sign in on Notion's own page, and Wren would read pages only when you search, open or include one, and create a page only after you confirm. Page content isn't stored, except as part of a GPT request you chose to send with it.
Slack is planned. Nothing has been built, and Wren doesn't connect to Slack.
9. Credentials, authorization and disconnection
- Wren never asks for your passwords or for API keys. Sign-in happens on each provider's own page.
- The tokens each provider issues, and the account email or name they report, are kept as private files in
~/Library/Application Support/Wren/Credentials: the folder is readable only by your macOS user and each file only by you. They are not stored in the macOS Keychain. They're never put in Wren's database, exports, backups or logs, and never shown on screen. - Disconnecting a service asks the provider to revoke Wren's access, deletes the tokens from your Mac, and (for Google) deletes cached mail. If the provider doesn't confirm the revocation, Wren tells you and points to where you can remove it yourself.
- You can also revoke Wren's access from your Google account, ChatGPT settings or Notion settings at any time.
10. Notifications and background operation
- Reminders are scheduled with macOS's notification system, which can show them even if Wren has been quit. Their text (the reminder's title) appears in Notification Centre and, depending on your settings, on your lock screen.
- Other notifications Wren may show: a GPT request finishing (with the start of your request), an email digest or urgent email alert (sender, subject and Wren's reason), and the morning briefing.
- Wren only works in the background while it's running. When you quit it, it stops any recording, stops checking email and sends nothing. It can start at login only if you turn that on.
11. Logging, diagnostics and analytics
- The app has no analytics, telemetry, advertising or crash-reporting SDK, and sends no usage data to the developer.
- Wren writes short technical messages to macOS's system log on your Mac (for example “reminder scheduling failed for 1 request”). These describe states and counts, not your content. Developer test builds log more detail; they aren't the builds offered to users.
- The in-app activity log described in section 4 stays in Wren's database on your Mac.
12. Backups, exports, retention and deletion
- Backups are copies of Wren's database in
Backups/inside Wren's folder: automatic daily backups (the latest 7 are kept), manual backups (10), and a copy before each upgrade, restore or reset (5 of each). They include GPT requests and answers, but not credentials or cached mail. You can delete them in Settings or in Finder. - Export creates a file you save: your items with their history, goals, observations, briefing records, permissions and the activity log. It doesn't include credentials, GPT requests, mail, local AI models or preferences.
- Deleting an item removes it. Remove all Wren data deletes every item, goal, history entry, GPT request and briefing record, resets permissions, revokes and deletes connected sign-ins, and deletes cached mail. Backups are kept unless you delete them.
- Wren keeps your data until you delete it. To remove everything, quit Wren, delete the app, and delete
~/Library/Application Support/Wren.
13. Security practices and limitations
- Connections to providers use HTTPS and are limited to each provider's expected addresses. Sign-ins use the providers' recommended flows for apps (authorization code with PKCE and a check that the response belongs to the request).
- Changes Wren makes go through a permission system: what Wren may do on its own, what needs your confirmation, and what content Wren read (like an email) can never trigger.
- Limitations: sign-in tokens are stored as files protected by your macOS user's file permissions, not in the Keychain, so other software running as your user could read them. Wren's database isn't separately encrypted; it relies on your Mac's security, including FileVault if you've turned it on. Wren is a preview from an independent developer and hasn't had an independent security audit.
14. Third-party provider policies
When you connect a service, that provider handles the data you send it under its own terms and privacy policy:
- OpenAI: openai.com/policies/privacy-policy
- Google: policies.google.com/privacy
- Notion: Notion Privacy Policy
- Apple (speech recognition, notifications, calendars): apple.com/legal/privacy
- Vercel (hosts this website): Vercel Privacy Notice
- GitHub (where the project lives): GitHub Privacy Statement
15. Changes to this policy
This policy will change as Wren does. The date at the top shows the latest version, and every change is visible in the project's history on GitHub. If a change affects what leaves your Mac, it will be called out in the app's release notes.
16. Contact
Questions or concerns about privacy: open an issue at github.com/shibadityadeb/wren/issues, or email the developer at shibadityadeb.official@gmail.com. Please don't post personal data in a public issue.