Privacy and Data

1. Local project operations

Your project files, .engineforgeignore processing, local project index, Code Graph source data, and Unity/Godot editor bridges operate on the development machine. The bridge connects EngineForge to the local game editor.

2. Remote model inference

When you submit a Crew task, EngineForge sends the selected model, system instructions, conversation messages, tool definitions, and selected project or engine context through the EngineForge gateway. The gateway authenticates the account and routes the request to the third-party AI model provider that serves the model you select, which may process it outside your country. Request and usage metadata can include user, conversation and session IDs, model, token usage, tool and bridge labels, tool errors, EngineForge/plugin/engine versions, and operating-system platform.

Web search and web pages

When an agent searches the web, the search request goes through the EngineForge gateway to an AI model provider that runs the search with Parallel, a web search service. When an agent reads a web page, EngineForge’s servers fetch that page, so the website sees a request from EngineForge rather than from your computer. The search query and the page address are recorded in service records for billing and fault diagnosis.

Generated media

Sound effects and music are generated by fal.ai from the description the agent writes; fal.ai runs the generation with its model partners. Character voice lines and game icons are generated by third-party AI model providers through the EngineForge gateway. The resulting files are downloaded into your project. Each generation is recorded for billing, with the account, the kind of asset and its cost. Character voices come from a fixed set of synthetic stock voices. EngineForge does not clone voices and does not accept recordings, photos or other media of a person as input for generation.

Downloads from your computer

Managed Godot and Godot export templates are downloaded by EngineForge on your computer directly from the official Godot release on GitHub, then checked against published checksums. GitHub sees that download request.

Asset Store

Asset Store searches and downloads go through EngineForge’s servers to the asset source you browse, such as Poly Haven, Kenney or OpenGameArt.

3. Automatic service telemetry

• Bridge command telemetry: engine, command labels, success/failure, a shortened error message, and optional session/conversation IDs.
• Search quality telemetry: the search query, result and candidate counts, score statistics, redirect state, latency, engine, and optional session/conversation IDs.
• Index health telemetry: engine type and aggregate class, function, edge, embedding, coverage, parse-error, and duration statistics.
• Anonymous error reports: on a hard agent failure, EngineForge sends versions, OS platform, model, agent, the failing tool, an error class and code, a scrubbed and capped error message, run timing flags, and a sequence of internal event names, keyed by a random installation ID never linked to the account. Preview in-app with "EngineForge: Show Last Error Report"; disable via the engineforge.diagnostics.autoReport setting or by setting the telemetry level to off.

4. User-submitted reports and feedback

• Session feedback sends like/dislike, optional text, session/conversation IDs, prompt count, model, engine, and EngineForge version when you submit it.
• A diagnostic report can include the capped conversation, log buffer, tool timeline, agent state, memory use, versions, identifiers, engine/model data, and your note. Diagnostic blobs are uploaded to EngineForge-managed Supabase Storage; report metadata is stored separately.

Website analytics

The website loads Vercel Analytics globally in production for page-view and route-path measurement. EngineForge does not send custom analytics events from the website.

Authentication and account data

Website and platform service requests use account authentication backed by Supabase. GitHub and Google sign-in use their OAuth flows and return to the EngineForge authentication callback. EngineForge reads the resulting user identifier, email, session, and available profile metadata such as display name and avatar for account UI, access checks, and authenticated service requests.

Service storage

The data described above is stored in EngineForge service tables, storage and logs. OAuth providers and Supabase are separate service destinations in the authentication path.

Questions about your data

This page describes where data goes. It does not set retention periods, deletion timing or where data is stored; the Privacy notice is the policy. For privacy questions, contact support@engineforge.ai.

Related documentation