Privacy Policy

Local credentials and workspace data

The Electron desktop app stores GitHub access tokens, backend session tokens, and BYOK API keys in local files using OS-backed encryption through Electron safeStorage when secure storage is available. BYOK key persistence is refused if secure storage is unavailable. Workspace state and chat history are stored separately in local renderer-state JSON; that file does not have the credential encryption layer.

GitHub data

With your consent, we access GitHub on your behalf to search issues, fork repositories, and manage pull requests. OAuth scopes are limited to what the workflow requires.

AI requests and backend synchronization

In BYOK mode, the main process sends prompts directly to your selected provider and uses your API key to authenticate there. The key is not sent to the FocusFork backend. Prompt context can include issue descriptions, file paths, open code, attached content, and diffs. Provider retention and training policies depend on your provider and account settings; model inference does not run locally in FocusFork.

When backend sync is enabled and connected, GitHub identity and access tokens, workflow events, contribution records, and chat history can be sent to the FocusFork backend. Subscription mode routes AI requests through that backend. BYOK mode does not itself disable backend synchronization.

Optional install telemetry

Install telemetry is enabled by default and can be disabled in Settings. A startup ping and a daily ping send a random install ID, app version, operating system, and AI mode to the backend. The telemetry record does not include GitHub identity, source code, or provider API keys.

Contact

Questions about privacy? Reach us through the contact form on the home page.