Privacy Policy

Last updated September 28, 2026

flow is an open-source personal assistant that runs on your Mac. There is no flow account and no flow server. This policy explains what flow stores, what leaves your Mac and where it goes, and what this website collects.

The short version

  • Your conversation, memory, profile and settings are stored in a folder on your Mac.
  • The developer of flow does not receive, store or have access to any of it.
  • flow sends data only to services you choose to connect, such as your model provider or Google account, and only to do what you ask.
  • flow does not sell your data, show ads or include analytics or tracking.

Data stored on your Mac

flow keeps its data in a local folder on your Mac. That includes your conversation history, the things it learns about you (listed with their sources under Your Profile), scheduled and background tasks, files you share with it, and the settings for services you connect. Passwords, API keys and sign-in tokens are kept in your macOS Keychain or in this local folder. You can view, correct or delete anything flow has learned from inside the app, and you can delete all of flow’s data by removing its folder.

Data that leaves your Mac

flow talks to other services only when you set them up and only for the task at hand:

  • Your model provider. When flow needs to think, it sends the provider you chose (for example ChatGPT, OpenAI, OpenRouter, or a model running on your own Mac) the context that request needs, such as your message and relevant memory. That provider’s own privacy policy governs how it handles the data.
  • Google (Gmail and Google Calendar), if you connect it. See the next section.
  • iMessage, if you turn it on. Messages you exchange with flow travel through Apple’s iMessage service and, if you choose it, through the messaging relay you configure.
  • Websites and apps you ask flow to use. When flow browses or operates an app on your behalf, those sites and apps receive what any visitor or user would.
  • Other connections you add, such as MCP servers or skills, receive what they need to perform the actions you request.
  • Update checks. flow checks flow.nisarg.me for new versions. Like any web request, this reveals your IP address and app version to the website host.

Google user data

If you connect a Google account, flow requests access to Gmail and Google Calendar. Every request goes directly from your Mac to Google; nothing passes through a server run by the developer.

  • What flow reads: email messages and metadata, calendar lists and events, so it can learn what matters to you, answer your questions and notice things worth your attention.
  • What flow can change: when you enable those actions, it can draft, label, archive and send email, and create or update calendar events. Anything that sends or books is shown to you first and waits for your approval, unless you have set up an automatic workflow for it yourself.
  • Where it goes: Google data is stored only on your Mac. Parts of it are sent to the model provider you chose when a request needs them. It is never sent to the developer, sold, used for advertising, or used to train models by flow.
  • Removing access: disconnect Google in flow, or revoke access at myaccount.google.com/permissions. Delete flow’s folder to remove data it already stored.

flow’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

This website

flow.nisarg.me is hosted on Vercel and runs no analytics. Vercel may keep standard server logs, such as IP addresses and requested pages, to operate and secure the site, as described in its own privacy policy.

Downloads are invite-only for now. If you enter your email on the download page, it is stored with Clerk, which keeps the waitlist, and download links are emailed to you through Resend. Your address is used only for the waitlist and those links. The form uses Vercel BotID to screen out automated sign-ups. The site sets no cookies. To be removed from the waitlist, open an issue on the project’s tracker without posting your address, and you’ll get a private way to confirm it.

Children

flow is not directed at children under 13, and the developer does not knowingly collect their data.

Changes

If this policy changes, the updated version will be posted here with a new date. The history of changes is visible in the project’s public source repository.

Contact

Questions about privacy can be raised on the project’s issue tracker. See also the Terms of Service.