Privacy Policy
Flame is built local-first. Choose between the Desktop IDE or Website policy below.
Flame IDE Summary: Flame is a local-first desktop application. Connected AI providers and tools can receive prompts, code, browser data, and other tool results. Secured Access encrypts the connection to paired phones. Telemetry is optional and off by default.
Looking for companion app disclosures? Read the Flame Mobile Privacy Policy or the Flame Browser Bridge Privacy Policy.
1. Desktop scope and local storage
This policy covers Flame IDE for macOS, Windows, and Linux. You do not need a Flame account to edit local projects, run terminals, or manage Git repositories.
For local projects, source files, settings, conversation history, terminal state, device pairings, and diagnostic logs are stored on your computer. Connected features can transfer this information as described below. When you use SSH remote development, project files, terminals, tools, and AI tasks run on the SSH host.
2. AI providers and developer integrations
AI requests are sent from the machine running the Flame backend to the provider or endpoint you configure. Prompts, conversation context, file contents, images, diffs, and tool results can be included. Agents may obtain additional context through the tools and permissions you grant, including terminal output, browser content, API responses, and database information.
Supported connections include Anthropic, OpenAI, Google Gemini, GitHub Copilot, OpenRouter, Anthropic through Amazon Bedrock or Google Vertex AI, and compatible endpoints. Claude Code, Codex, Copilot, and Antigravity use their respective runtime and sign-in systems. The provider or gateway you select governs processing, retention, and model-training practices under your account and its terms. Flame does not operate a prompt or source-code proxy for these requests.
Ollama, LM Studio, and other compatible endpoints can keep model requests on your computer when hosted locally. A remotely hosted compatible endpoint receives your requests over the network. Choosing a local model does not make separate integrations or network-capable tools offline.
Git hosts, issue trackers, CI systems, databases, package registries, and other configured services receive the credentials and request data needed for their features. The update service receives standard request metadata during update checks and downloads, and records download counts by channel, version, platform, and architecture.
3. Browser data and AI context
The optional Flame Browser Bridge extension sends browser data to Flame through a local loopback connection. Flame may subsequently include browser tool results in requests to your chosen AI provider. Local transfer from Chrome to Flame does not mean later AI processing stays local.
Approved tools can process page text, HTML, screenshots, console output, network metadata or headers, cookies, and JavaScript results. These can contain personal or sensitive information. Passive activity records exclude typed values, while explicitly approved actions can enter or read them. Tool results can remain in local conversation history and, if transmitted, under the provider's retention rules. Read the Browser Bridge Privacy Policy for storage, permissions, and pause or revocation controls.
4. Secured Access and Flame Mobile
Remote Access defaults to Off. Enabling Secured Access connects the desktop outbound to Flame Secure Relay while the desktop backend stays on loopback. The native Flame Mobile companion for iOS and Android is available soon; the desktop pairing support is implemented.
Generate a short-lived, single-use QR code on the desktop and scan it inside Flame Mobile. The QR pins the desktop identity key. Enter the two-digit confirmation number shown on the phone into the desktop, then select a device access duration. Scanning the QR alone does not authorize a device.
The desktop and phone encrypt workspace traffic end to end using Noise IK and AES-256-GCM. The relay routes encrypted traffic without receiving the session keys or plaintext workspace content. It can observe connection metadata, including online registration, rendezvous identifiers, IP addresses, timing, and byte volume. This protection concerns traffic through the relay; data sent from Flame to a configured AI provider is processed by that provider.
Authorized phones can access the supported device API, including files, Git, AI conversations, terminals, tasks, and shared todos. Pairing records and credentials are kept on the desktop and phone. Turning access Off closes active relay sessions and cancels pending pairing; a previously paired device can reconnect when you enable access again. Revoking a device or allowing its access to expire also ends its active sessions. Your desktop must be running and connected.
Mobile camera, selected attachments, and optional speech recognition have their own handling. Speech services may process audio according to your device settings. See the Flame Mobile Privacy Policy and pairing documentation.
5. Credentials
Flame-managed API keys and integration tokens are encrypted at rest. Packaged builds use operating-system credential protection when available. Standalone or headless backends can use a local encryption-key file protected by filesystem permissions. Agent runtimes can also maintain credentials through their own authentication systems.
Encryption of credentials does not encrypt all project files, conversation history, or local diagnostic logs. Protect access to your computer, remote hosts, and backups.
6. Optional telemetry, diagnostics, and support
Usage statistics are optional and off by default. They require your affirmative consent to the current notice, even if you previously enabled statistics. You can preview both payload formats and change your choice in Settings → Diagnostics. This choice is separate from website cookies. Installation counting remains unavailable until the privacy release review, operational verification, and publication are complete.
One setting covers two operations. Independent software and feature reports contain version, release channel, coarse operating-system information, architecture, distribution channel, and rounded counts of launches, focused minutes, and built-in panel and tool selections. These reports contain no installation identifier, work content, names, or project paths. Reports are sent at most hourly and stored as separate daily totals for up to 90 days. Those totals cannot be retrieved or deleted by installation.
With fresh consent, installation counting uses a random installation identifier and a separate private credential, neither derived from hardware, accounts, or network addresses. They and the consent record are held in OS-backed encrypted storage; sharing stays off if protected storage is unavailable. After a desktop window stays in the foreground for five continuous seconds, Flame records at most one activity date per UTC day. The activity payload contains the identifier, date, schema version, and consent version. It does not measure content or input. Counts represent participating application-data profiles, not people or every installation; copied profiles can affect the count.
Flame's first-party, self-hosted reports service is in Germany, EU. Installation activity is pseudonymous personal data, even when hashed. HTTPS requests expose the connection IP to receiving infrastructure, but the usage endpoint does not persist it. Hosting providers may process network metadata, and short-lived in-memory counters prevent abuse. Usage statistics are not used for advertising or individual profiling. No server backups of usage statistics are kept.
Activity expires within 35 days of its UTC date; the installation registry and consent evidence expire after 35 days without accepted activity. The device queues at most seven UTC dates. Turning sharing off clears pending activity and requests deletion of linked records. A minimal revocation record remains for 35 days to reject stale requests. If offline, deletion stays pending until acknowledged; if the app is not reopened it cannot deliver the request. After 70 days without confirmation, local deletion credentials are erased and the status remains unverified. Server expiry still applies.
Use Settings → Diagnostics → Manage usage data to view or export this installation's records, delete them, and turn sharing off. A private recovery code can help with a support request when the installation is inaccessible; treat it as a secret and share it only through an agreed secure channel. Renewed consent creates a fresh identity. Settings exports and app-level profile transfers do not include consent or credentials, but OS backups and manually copied app-data directories can preserve them.
Crash reports require a manual send action. Detailed reports are saved locally and can be reviewed. Local reports redact home-directory and operating-system username details. The upload is a separate, restricted diagnostic payload containing app and runtime versions, coarse system information, error classifications, and allowed diagnostic summaries. Raw error messages, raw stacks, free-form context, project paths, terminal output, source code, and native minidumps are excluded from that upload.
If you submit feedback or a support request, the information you enter and any attachments you choose are sent to Flame's reports service. Review submissions for sensitive information before sending.
7. Retention and your controls
Local files and app data remain until removed by you or the application's retention controls. Uninstalling the application may leave its data directory and project files in place. You can delete conversations and reports, remove configured providers, revoke paired devices, and turn off optional telemetry. Providers, SSH hosts, integrations, and backups maintain their own copies under their own retention rules.
The relay transports encrypted workspace traffic; it does not serve as a workspace backup. Local encryption and relay encryption do not control retention by an AI provider after you send data to it.
8. Privacy requests and contact
Daniel Amenou, Brazil Street 20, Tel Aviv, Israel, is the data controller and privacy requests owner. For questions or requests for access, correction, deletion, or other applicable rights, contact support@flame-ide.com. Tell us which service or submission your request concerns, using the subject Data Privacy Request. Requests about information held by a provider you selected should also be directed to that provider.