Privacy Policy

In this beta, each participant operates Forge on their own Mac or Macs and chooses their own coding providers. The developer does not provide a shared hosting service for participants. Forge Pro connects to the Forge server you select. It sends that server the information needed to authenticate, including a random installation identifier. When you pair a device, it also sends a device label. It also sends content and actions you choose to submit, including prompts, approvals, terminal input and attachments. The server returns and may store conversations, project and thread information, code, diffs, agent and tool output, and terminal output.

Your server and coding providers

Your server can forward prompts, attachments and relevant project content to the coding providers its operator configures. The server operator's and provider's access, retention and deletion practices apply. Your provider account is separate from Forge Pro. The mobile app does not include a coding server.

What's stored on your device

On your device, Forge Pro stores connection addresses and labels, preferences, a random installation identifier, cached conversations and thread content, workflow and queue state and queued submissions. Queued submissions may include text and attachments until delivered. Server credentials are stored using Apple's Keychain. Deleting the app does not delete conversations or files retained by a server or coding provider; contact the server operator about those records. Keychain credentials may outlive an app installation.

Camera, photos and attachments

Camera access lets you scan a Forge pairing code or take a photo to attach. Photo and file access lets you choose content to attach. Sending a message sends its selected attachments to your configured Forge server.

Diagnostics and support

Forge Pro keeps bounded diagnostic information locally, including app/build/platform information, connection and thread identifiers, binary names, file paths, and crash, hang and performance information when available. You can export a report or use Send to this thread to upload it to your selected server. Review reports before sharing them. Information you email to support, including your email address and any attached report, is received by the developer for support.

Built-in preview browser

The built-in preview browser connects to addresses you open. It uses a nonpersistent WebKit data store; those sites receive requests and apply their own privacy practices. Opening links in an external browser uses that browser's settings.

Connections and encryption

HTTPS and WSS connections use operating-system encryption. Forge also permits HTTP and WS for local/private-network connections; those protocols do not add TLS at the app layer. Use the server address and protected network supplied by your server operator.

TestFlight

When you participate through TestFlight, Apple provides the developer with build/test metrics and automatically shared crash logs. Feedback you submit through TestFlight may include comments, screenshots, contact information when available, and app/device details. Apple processes this information through TestFlight under Apple's policies. See Apple's build metrics and crash-log information and tester feedback information.

Scope

These are factual privacy disclosures describing observed app data flows for the friends beta — not a liability waiver, a legally reviewed beta agreement, or a completed App Store privacy declaration. Invite-only distribution does not establish an exemption from applicable obligations. Questions? Email [email protected].