Skip to content

Privacy and data

ffgit is a desktop app: your repositories, drafts and settings stay on your computer.

  • Git runs through the git installed on your computer. ffgit reads and writes your repositories the way Git is configured, with your hooks, filters and signing.
  • Provider tokens for GitHub and GitLab, from a browser sign-in or pasted, are stored locally in an encrypted file.
  • Agent activity — the journal of agent runs, read state, measured chat sizes, review notes and, if you turn on Usage…, token sums per model and day — is kept encrypted beside the settings.
  • Agent sessions stay where the agents keep them. ffgit reads Claude Code’s session status file (~/.claude/sessions/<pid>.json) and nothing else in that folder, never its token files; it reads a transcript only while you open, resume or search that chat, and keeps nothing it read.
  • Other agent logins you add in Agent accounts… live in folders of their own; ffgit never reads the login itself.
  • Recovery copies are stored in the project’s .ffgit/backups folder until you delete them.

Some things run only after you allow them, such as drafts by your agent in a project, Restore files to before this message, searching chats’ messages in Jump, reading other logins, Usage…, keeping the default branch current and resuming a chat at a limit reset. The answer is kept for that chat, the project or only that time.

Privacy… in the main menu switches crash reports and lists every kept answer with Take back.

On macOS, Computer use… lets a chat’s agent list running apps. Reading a window requires permission for that app. Its visible controls and text, and a screenshot if requested, go to the agent’s provider with the chat. The provider’s retention policy applies there. Computer Use results are excluded from the paired phone feed and crash reports.

Granting access to ffgit includes the window that runs the chat. With permission to act, the agent can answer its own approval cards, change Privacy… settings and start other chats. Review saved decisions in Privacy… and choose Take back to revoke one. Computer Use setup and limits.

  • GitHub and GitLab, only when you act on them: signing in, listing and reviewing requests, reading CI, downloading artifacts, and fetch, pull, push or clone. With Keep the default branch current on, ffgit fetches the default branch’s remote every 15 minutes; with Watch and wake, it reads a watched request every two minutes.
  • Update checks against the feed at install.aso.dev, at launch and then hourly, naming ffgit’s version and your operating system. Like downloads, these requests are logged with your IP address: ASO.dev counts downloads, updates and copies in use from those logs and keeps them for 400 days.
  • Agent versions: to tell whether Claude Code or Codex is the latest release, ffgit asks npm for the package’s tags, one anonymous request per agent, kept for six hours.
  • Crash reports go to ASO.dev’s own Sentry only after you agree: the first launch asks once. They carry crashes and errors only, with the home folder written as ~ and credentials removed. Debug builds and test runs never send them.

Agents use your login to communicate with their providers.