Privacy
EngineForge is operated by A & Y, licensed dealer no. 558553418, Nahshol 4, Rosh HaAyin, Israel. A & Y is the controller of the personal data described below, and privacy questions go to support@engineforge.ai.
Last updated 24 October 2026.
Who controls this data
A & Y is the data controller for everything described in this notice: account, service, telemetry, diagnostic and billing-record data. Our merchant of record, the authorised reseller named at checkout and on your receipt, is a separate, independent controller for the payment data it collects at its checkout. That payment data is covered by its own privacy notice, not by this one.
Payments and the merchant of record
EngineForge plans and usage top-ups are sold by our authorised reseller, which acts as merchant of record and is named at checkout and on your receipt. For purchases through Polar, Polar Software, Inc. acts as our authorised reseller and merchant of record. It is the legal seller of the purchase, issues the invoice, and is responsible for sales tax and VAT on it. Payment details, including card numbers, are entered on its checkout and go to it. They never reach our systems and we never store them. When a checkout is opened, we send the merchant of record the email address on your account plus enough detail to attribute the resulting payment to the right account: your EngineForge user identifier, and with it the plan on a subscription, or, for a usage top-up, the fact that it is a top-up and how many credits it grants. If your receipt names Paddle.com Market Ltd, Paddle is the merchant of record for that purchase, and its own privacy notice covers the payment data it holds.
Billing records EngineForge keeps
We store what the merchant of record returns to us so that your account receives what you paid for. That is a billing customer identifier and the provider that issued it, your current plan, its status and its billing period, the credits included for the current month and how many have been spent, and, for each usage top-up you buy, the amount paid and the credits it granted.
Billing notifications are stored exactly as received
We keep an unaltered copy of every billing notification the merchant of record sends us, so that a payment can be reconstructed and audited if it is ever questioned. Those records carry the subscription, transaction, plan and amounts, the identifiers described above, and whatever else the merchant of record includes, which can include your email address and the country and postcode it used to calculate tax. They do not carry card numbers.
Website analytics
The public website uses Vercel Analytics, which records page views and the pages visited so that we can measure how the site is used. We do not send it any custom events, and it is not used to profile you or to target advertising.
Account and authentication
We use Supabase for account sessions and authenticated service requests. Sign-in is OAuth only: choosing Continue with GitHub or Continue with Google sends you through that provider's OAuth flow and back to the EngineForge authentication callback, so we never receive or store a password. We read the resulting user identifier, email address, and any profile details the provider returns, such as your display name and avatar, to show your account and to check your access.
Cookies
The website sets Supabase authentication cookies, which are what keep you signed in between requests. There are no advertising cookies and no cross-site tracking cookies, and Vercel Analytics measures page views without setting one. Clearing the authentication cookies signs you out.
Local development data
Your project files, the local search index, Code Graph source data, ignore-rule processing, and Unity and Godot bridge operations all run on your own machine. We never copy your project wholesale to our servers. What leaves your machine is the working context you send with a model request, the service, usage and telemetry records described under Service and usage records and Automatic platform telemetry, and anything you choose to attach to a diagnostic report.
Model requests
When you ask the Crew to use a model, we send the prompt, the conversation, the available tools and the working context you selected through our gateway to the third-party AI model provider that serves the model you chose, using AI infrastructure providers that relay the request. Which provider receives a given request follows the model you picked.
Web search and web pages
When an agent searches the web for you, the search request is sent through our gateway to a third-party AI model provider that runs the search using Parallel, a web search service. When an agent reads a web page, our servers fetch that page for it, so the website sees a request from EngineForge rather than from your computer. We record the search query or page address with the other service records described below.
Generated sound, voice lines, music and images
When you or an agent generate a sound effect or music, the description of the sound is sent to fal.ai, which produces it using its model partners. Character voice lines and game icons are produced by third-party AI model providers through our gateway. The resulting files are delivered to your project, and each generation is recorded, with the account, the kind of asset and its cost, so it can be charged to your credits. 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.
Engine downloads
If EngineForge sets up Godot for you, or downloads Godot export templates when you export a game, your computer downloads them directly from the official Godot releases on GitHub. GitHub receives that download request under its own privacy terms. These downloads do not send your project to us or to GitHub.
Service and usage records
We record the request and usage information needed to operate the gateway, meter your plan, and diagnose faults. For each model call that includes the model used, token counts by billing class, the cost of the call, timing, tool and error activity, session and conversation identifiers, and the application version and platform the call came from.
Automatic platform telemetry
The application sends us the outcome of editor bridge commands, search quality data including search queries and result scores, and aggregate metrics about the health of your local index. This is used to keep the product working correctly and is not used to profile you.
Automatic error reports
When the AI agent hits a hard failure, the application sends us a small anonymous error report so we can find and fix the problem: application, plugin and engine versions, operating system, the model and agent in use, the failing tool, an error class and code, a short error message that is scrubbed of file paths, secrets and email addresses before it leaves your machine, timing information, and a sequence of internal event names. These reports never contain your code, prompts, conversation content, project names or your account identity; they carry only a random installation identifier that is not linked to your account. You can preview the exact payload in the application ("EngineForge: Show Last Error Report") and turn reporting off in the settings at any time; turning the editor's telemetry level off also turns it off.
Feedback and diagnostics
Feedback about a session is sent to us only when you submit it. Diagnostic reports, which are richer than automatic error reports, are sent only when you choose to send one, and can contain conversation content including code the agent read or wrote, logs, a timeline of the tools that ran, agent state, system and version details, and any note you add. Please remove anything confidential from a report before you send it.
Who this data is shared with
Supabase hosts our database and account sessions. Vercel hosts the website and the gateway and provides the website analytics. Axiom receives our server-side logs. Third-party AI model providers, and the AI infrastructure providers that relay requests to them, receive the prompt and working context of a model request at the moment you make it, to serve that request. Parallel receives web search queries, and fal.ai receives descriptions of sound effects and music to generate. Asset sources you browse in the Asset Store, such as Poly Haven, Kenney and OpenGameArt, receive the search or download request from our servers. Our merchant of record receives the checkout data described above and holds it as its own controller. Personal data is not sold, and it is not shared for advertising.
Why this processing is allowed
Account, gateway, model-request and billing data are processed to perform the contract between you and A & Y. Service records, telemetry, automatic error reports and other error data are processed on the legitimate interest of keeping the platform working, correct, and correctly paid for; automatic error reports are additionally anonymised before they reach us and can be switched off in the application. Session feedback and diagnostic reports are processed on your consent, because each is sent only when you choose to send it. Billing and accounting records are also processed to meet the record-keeping obligations that apply to a licensed dealer in Israel.
How long it is kept
Account and profile data are kept while your account exists and are deleted when the account is deleted. Billing and accounting records outlive the account: they are kept for as long as Israeli accounting and tax rules require a licensed dealer to keep them, and the usage periods and top-up records that justify a charge are kept with them. Service logs, telemetry, and diagnostic reports are kept on rolling operational retention and are not used to build a profile of you.
Your rights
You can ask for a copy of the personal data held about you, ask for it to be corrected or deleted, ask for it in a portable form, object to the processing that rests on legitimate interests, and withdraw consent for anything that rests on consent. Write to support@engineforge.ai and we will respond within one month. If you are in the UK or the EEA you may also complain to your national supervisory authority. Requests about payments, invoices, or the card on file belong to the merchant of record named on your receipt, which holds that data as its own controller; the billing portal linked from your account settings opens it directly.
Where data is processed
We operate from Israel. Our hosting, database, logging and AI providers may process personal data in other countries, including the United States, so personal data is transferred internationally. Israel is recognised by the European Commission as providing an adequate level of protection, and transfers onward to providers rely on the data protection terms in those providers' own agreements.
Security
Requests are authenticated before account data is returned, and an account is served only its own records. The website and the gateway are served over TLS. Provider credentials are held server side and are never sent to the browser. Billing notifications are accepted only when they carry a valid signature from the payment provider, so a forged payment event cannot change what an account is owed. No system can be completely secure, and we do not claim otherwise. If a breach affects your personal data and the law requires us to tell you, we will do so without undue delay.
Children
EngineForge is a professional development tool and is not directed at children. You must be at least 18, or the age of majority where you live if that is higher, to use EngineForge. We do not knowingly collect personal data from anyone below that age. If you believe a child has given us personal data, write to support@engineforge.ai and we will delete it.
If you are in the United States
We do not sell personal data and we do not share it for cross-context behavioural advertising, in the sense those terms are given by California law, and we have not done so in the past twelve months. Residents of California and of other states with comparable laws can exercise their rights of access, correction, deletion and portability using the same address below, and we will not treat you differently for doing so.
Changes to this notice
We update this notice when the way we handle personal data changes. The current version always lives at this address, and the date it last changed is shown at the top of the page. Where a change materially affects you, we will give notice by email or in the application before it takes effect.
What this notice does not cover
It does not cover the payment details you enter at checkout. The merchant of record collects those as its own controller and describes them in its own privacy notice. It also does not cover third-party services you choose to use alongside EngineForge, which are governed by their own notices.
Questions or requests
Contact support@engineforge.ai. See the technical Privacy & Data guide for payload-level detail, or use the Contact page for support and policy requests.
Purchases are sold by our authorised reseller, which acts as Merchant of Record and is named at checkout and on your receipt. Its buyer terms, which you accept at checkout, govern the payment. For purchases through Polar, see the Polar Privacy Policy for how Polar handles your payment data.
Read the EngineForge Terms.