Skip to content
Godot MCP Studioby Coadite

Privacy Policy

Last updated 2026-10-12

Coadite is the data controller for Godot MCP Studio. This policy explains exactly what we collect, what we don't, why, how long we keep it, and the rights you have over your data (including under the EU and UK GDPR).

What we collect

  • Account data: your email, a display name, and authentication details (a hashed password and session tokens), to run your account.
  • Purchase & license data: your plan, license status, and activated devices. For each activation we store an opaque identifier derived on your computer, the device name you enter, operating system, architecture, app version, activation and last-check dates, country/region, and a masked network prefix. We do not store the machine identifier used to derive that opaque ID, a MAC address, a full IP address, or precise location. Polar acts as the Merchant of Record and authorized reseller for purchases. Polar processes payment, billing, tax, invoice, and receipt information. We receive the customer and order details needed to provision and support your license, but never see or store your full card details.
  • Basic operational logs: standard server request logs from our hosting provider, used to keep the service running and secure.
  • Privacy-preserving website analytics: anonymous page views and successful installer-download events, including aggregate country, browser, device type, and operating system. Vercel Web Analytics does not use analytics cookies or tie these events to an identifiable visitor or IP address.
  • Google Analytics and Google Ads measurement: we use one Google tag to understand how visitors find and use the site and whether an advertisement led to a sale. Besides page views, it receives these site events: account created, signed in, checkout started, purchase completed, newsletter signup, app download (edition and platform), and the first message of a support chat. Checkout and purchase events include the product, its price, and the currency; purchase events also include an opaque checkout identifier so a purchase is not counted twice. Events never include your email, name, license key, or anything you type. Google Analytics receives purchases of licenses and image credit packs; Google Ads receives license purchases only. The Google tag loads on every page and works through Google Consent Mode. In the EEA, the UK, Switzerland, and Turkey, Google analytics and advertising cookies stay off unless you allow optional cookies; elsewhere they are on until you choose only necessary cookies or your browser sends Global Privacy Control (see Cookies and local storage). While they are off, Google may still receive cookieless pings with ad click identifiers removed. We disable personalized Google ad signals. The tag is served through our own domain under /metrics: our server relays those requests to Google, so Google receives our server's IP address instead of yours. Besides what the tag itself collects, the relay passes on only your browser's user agent and language, the page address without its query string, your approximate country and region, and Google's own cookies, the last only while Google cookies are allowed for you. Your sign-in cookie never leaves our site. If that path fails to load, the tag falls back to loading directly from Google.
  • Purchase confirmation from our server: when a payment completes, our server can also report the purchase to Google Analytics, from where Google Ads can count it, so a sale is still measured when a browser blocks the Google tag. It carries the same product, price, currency, and checkout identifier, plus the Google Analytics cookie identifiers, but never your email. If the purchase followed a Google ad click, Google Ads also receives it with that ad's click identifier (see Cookies and local storage), the purchase time, value, currency, and checkout identifier. Both are only sent while optional cookies are on for you, as described in Cookies and local storage.
  • How you found us: when you create an account and with each order, we record a coarse traffic channel, for example "Google search" or "X", worked out from the link or site that brought you here, with no identifier, so we understand which channels bring customers.
  • Meta ads measurement: only while optional cookies are on for you, the Meta Pixel loads and receives page views, account creation, checkout starts, purchases (product, price, currency, and an opaque checkout identifier), newsletter signups, app downloads, and the first message of a support chat. When you buy while optional cookies are on, our server also sends that purchase to Meta with a one-way hash of your email address, the Meta click and browser identifiers, and your browser's user agent, so Meta can match it to an ad. The browser and server reports share one identifier, so a purchase counts once. Nothing is sent to Meta while optional cookies are off.
  • X Ads measurement: while optional cookies are on for you, the X pixel loads and receives license purchases (product, order value, currency, and an opaque checkout identifier) and Lite downloads, so we can measure our X ads. It does not load while optional cookies are off.
  • Service request records: when the desktop app checks or downloads rules and skills, we record the edition, app version, operating system, architecture, request time, and approximate country/region. Pro requests are linked to the account and opaque activated-device identifier used to verify access. We do not store an IP address, network prefix, or selected AI agent in these records.
  • Agent feedback: in Pro, the AI agent can send us a short feedback report when an MCP tool fails or misbehaves, when a tool it needed is missing, or with an idea or praise. This is always on, because it is how we find and fix broken tools. A report holds the kind of feedback, a short generic message, the tool or skill name it concerns, app edition and version, skill bundle version, AI client name and version, and an opaque project identifier. It never includes your code, prompts, project details, file content, file paths, credentials, usernames, emails, or URLs: agents are instructed to leave them out, both the local MCP server and our API reject messages that look like they contain them, and a message is limited to 800 characters. Reports require Pro license authentication, are linked to your licensed account and activated-device identifier, and are rate limited per install and per account. Lite does not send agent feedback.
  • Optional skill usage insights: on by default in Pro. While Share skill usage insights is on in desktop settings, the local MCP server reports which bundled skill the agent loaded, with the same version, client, and opaque project fields as feedback and no message. You can turn this off at any time to stop future reports. Lite does not send usage insights.
  • Image Studio jobs: when you approve hosted generation, we process the prompt, selected source images or masks, requested operation, provider, dimensions, job state, credit amount, and provider request identifier. The images are held in private temporary storage to deliver the result and are removed within seven days. We keep the job and credit transaction record without the prompt or image contents so we can prevent duplicate charges and resolve support requests.
  • Support messages: our support chat and tickets are our own system, not a separate chat company. If you start a chat or open a ticket, we store the conversation in our own database, together with the email you choose to share, your country, the IP address the chat came from (used only to stop spam and abuse), and basic technical details such as your browser, browser language, and the page you started the chat from, so we can answer you. Files and images you attach are stored with UploadThing and shown to you and our team through our own site. When you are signed in, the conversation is linked to your account so you can find it again on your dashboard. While a chat is open, your browser keeps a connection to our realtime service on Railway, which only tells the page that something changed; it never carries the content of your messages. When our team replies while you are away, we email you a notice through Resend.
  • AI support assistant: an AI assistant may answer your chat first, and it hands the conversation to a person when it is unsure or when you ask. To write a reply it sends your message, earlier messages in the same chat (including images you shared there and replies from our team), and matching parts of our public docs through the Vercel AI Gateway to an AI model, using only providers with zero data retention, so they do not keep or train on it. The same route is used to sort new conversations by topic and urgency and to spot spam or abuse. When you are signed in, it also uses a short summary of your account (first name, email, edition, purchases, devices in use, and Image Studio credits) so it can answer questions about your own account. We keep a log of each question, its answer, and that summary so we can check and improve the answers, and delete this log automatically after 90 days. The conversation itself is kept separately.

Why we collect it (legal basis)

Under the GDPR we rely on these legal bases:

  • Performance of a contract: account data, license, and device activations are needed to give you the product you bought and to keep your license working. Approved Image Studio jobs and their credit ledger are needed to provide hosted generation that you request.
  • Legal obligation: we keep the minimum purchase and tax records the law requires.
  • Legitimate interests: basic operational logs, coarse activation metadata, service request records, privacy-limited agent feedback, and optional skill usage insights are used to keep the service secure and reliable, find and fix broken MCP tools, improve bundled skills, prevent fraud and license abuse, and enforce the three-device limit. We keep this data minimal and masked, and you can turn off skill usage insights at any time.
  • Consent: where we ask for it, for example for optional analytics and advertising cookies or a non-essential communication, you can withdraw it at any time.

Emails we send

Account emails such as verification and password resets are part of the service. If you buy a license, we also send product update emails about what you bought: new releases, license and security notices, your Image Studio credits, and price changes for a plan you own. We send these to customers by default on the basis of our legitimate interests, never to people who have not bought. Every product update email has an unsubscribe link, and you can turn them off on your account page. Our marketing newsletter is separate and only goes to people who opt in. We use Resend to manage these email preferences.

What we do NOT collect

  • We do not collect general desktop-product analytics. Pro sends only the privacy-limited agent feedback listed above, plus skill usage insights while that setting is on. We do not receive a project name or path, tool arguments, prompt, or project content through either of them.
  • We do not collect MAC addresses, raw hardware serial numbers, or GPS location, and we store a full IP address only on support conversations, as described above.
  • We do not read, upload, or store your Godot projects, scenes, or scripts. Image Studio uploads only the images and masks you explicitly select for an approved hosted job.
  • We do not sell or rent your data, and we share nothing with advertising platforms beyond the measurement described above.

What stays on your machine

Godot MCP Studio is local-first. Your project files and everything the AI does to them are processed on your computer by the local MCP server. The locally stored, signed activation token includes your account display name and email so the desktop app can show who the license belongs to.

Image Studio projects, edits, frames, and permanent exports stay in the local library you choose. Only an approved hosted generation job sends its prompt and selected inputs to our service and the selected generation provider.

Cookies and local storage

We keep cookies to the minimum needed to run the site.

  • When optional cookies are on: in the EEA, the UK, Switzerland, and Turkey, optional cookies stay off until you allow them in the banner. Elsewhere they are on by default. You can turn them off at any time with Privacy choices in the website footer. If your browser sends Global Privacy Control, we treat it as turning them off, wherever you are, unless you later allow them yourself. Either way, we never show you personalized ads and never sell your data.
  • Strictly necessary cookies: the website sets a secure session cookie when you sign in, so you stay logged in and your account is protected. These are essential and cannot be turned off without breaking sign-in.
  • Optional advertising measurement: Google Analytics and Google Ads share one Google tag. Advertising storage, advertising user data, and analytics storage follow the rule above. Personalization is always denied. A purchase conversion event can still be sent as a cookieless ping. The Meta Pixel and the X pixel do not load while optional cookies are off. Choosing only necessary cookies deletes the Google cookies our domain can reach. A choice you make is kept in your browser's local storage and in a first-party cookie, gms_ad_consent, for one year, so our server can respect it too. Your choice is not stored until you make one, so until then the default for where you are applies.
  • Ad click identifiers: when you arrive from an ad, we keep its click identifier (Google gclid, gbraid or wbraid, Meta fbclid, X twclid) in your browser's local storage for up to 90 days and attach it to a checkout you start, so the purchase can be credited to that ad. We only keep it while optional cookies are on for you, and choosing only necessary cookies deletes it.
  • Live chat: our support chat is our own system, and the messages you send go through our own site. Once you use the chat, we set one functional cookie, gms_support_visitor, that keeps your conversations available when you come back, for up to 180 days. Only our server can read it. The chat also keeps a few flags in your browser's local storage (whether you have chatted before, closed the greeting, skipped or saved the email prompt, and which announcements you dismissed). Once you have a conversation, your browser also connects to our realtime service so new replies show up without reloading. After you sign out, the chat starts a new conversation instead of showing your signed-in one. These run the chat only; they are not advertising or cross-site tracking.
  • Checkout: when you buy, Polar, as Merchant of Record, may set its own cookies on its checkout and customer-portal pages under its own privacy policy.
  • On your computer: the desktop app stores a signed activation token and your settings locally so it works offline. That stays on your machine and is not a website cookie.

International data transfers

Our hosting, email, payment, queue, storage, and generation providers may process data on servers outside your country, including outside the EU. Where that happens we rely on the providers' standard contractual clauses and equivalent safeguards to protect your data.

Data retention

We keep account, license, and activation records for as long as your account exists, so your license keeps working. If you delete your account, we remove your personal data within 30 days, except records we must keep for legal, tax, or fraud-prevention reasons. Operational logs are rotated on a short schedule. Turning off skill usage insights stops future usage reports. Agent feedback and usage insight records are deleted automatically after 90 days and are deleted when the linked account is deleted. You can also request access to or deletion of existing account-linked feedback and usage records through the contact process below.

Third parties

We use Polar as the Merchant of Record and authorized reseller for purchases, Vercel for hosting, anonymous website analytics, and routing support assistant requests to zero data retention AI providers, Railway for queued Image Studio work, short-lived coordination, and the realtime service that tells the support chat when something changed, UploadThing for private temporary image storage and support chat attachments, and fal and OpenAI for the generation operations you select, Google, Meta, and X for consent-controlled analytics and advertising conversion measurement, and Resend for sending email and managing email preferences. They process data to provide those services under their respective terms and privacy policies.

Your privacy rights

Wherever you live, you can ask us to show you the personal data we hold and to correct or delete it. If you are in the EU, the UK, or a region with similar laws, you also have the right to:

  • access a copy of your data;
  • rectify data that is wrong or incomplete;
  • erase your data ("right to be forgotten"), subject to records we must keep by law;
  • restrict or object to certain processing;
  • portability: receive your data in a portable format;
  • withdraw consent at any time where processing was based on consent.

To exercise any of these, contact Coadite and we will respond within the timeframe the law requires. You also have the right to complain to your local data protection supervisory authority, though we hope you will contact us first so we can help.

Changes

We may update this policy at any time. The "Last updated" date above always reflects the current version; material changes will be noted on this page.

Contact

For privacy questions, to exercise your rights, or to request deletion of your data, contact Coadite at the address on our website.