Repository contents
FlowTree reads local repositories and worktree directories to show status, diffs, and files. It does not copy those repositories into a FlowTree-hosted service.
Product privacy
Your repositories stay under your control.
FlowTree is designed without a product backend that receives your code. This page describes the application’s current data boundaries in plain language.
FlowTree does not upload your repositories to a FlowTree server.
Your code is read and changed through ordinary files and local Git operations on your Mac.
Application data
What stays on your Mac.
Configuration and cached state
Added projects, worktree metadata, terminal profiles, linked paths, cached Git state, review state, and command logs are stored locally as application data.
Terminal sessions
Terminal processes and tmux sessions run on your machine. Any external CLI you start inside a terminal has its own behaviour and privacy terms, separate from FlowTree.
Authentication
FlowTree does not require custom Git authentication. Local Git uses the SSH keys, credential helpers, tokens, and remote configuration already available in your environment.
Remote operations
When information can leave your Mac.
Local-first is a boundary, not a claim that every command is offline.
Git remotes
If you run fetch, pull, push, remote branch deletion, or background remote synchronisation, your local Git process communicates with the host configured for that repository.
External CLIs
AI coding tools and other commands launched in FlowTree terminals may contact their own providers. FlowTree does not change or proxy those tools’ networking behaviour.
A formal legal privacy policy, company identity, support contact, analytics statement, and any future licensing-provider disclosures must be completed before commercial release.
Coming to macOS
Local tools. Visible boundaries.
FlowTree is coming to macOS. See the current release status and requirements.