Privacy Policy

AI Game Dev (ai-game.dev) is a platform that bridges AI-powered coding assistants with game engines through the Model Context Protocol (MCP). This Privacy Policy explains what data we collect, why we collect it, who we share it with, and how we protect it.

1. Who We Are (Data Controller)

The data controller for the Service is Ivan Murzak (trading as Modalith), a sole proprietorship, located at 13205 97th Ave NE, Kirkland, WA 98034. For questions about this policy or to exercise your rights, contact us at privacy@ai-game.dev.

EU/EEA & UK GDPR Representatives (Article 27). If you are in the EU/EEA or the UK and have questions or concerns about your personal data, you may contact our appointed GDPR representative:

• EU Representative — Euverify Ltd (Ireland), Unit 3D North Point House, North Point Business Park, New Mallow Road, Cork, T23 AT2P, Ireland — Email: gdpr@euverify.com
• UK Representative — Euverify Ltd (UK), 3rd Floor, 86-90 Paul Street, London, EC2A 4NE, United Kingdom — Email: gdpr@euverify.com

This representative covers everyone whose personal data we process in the EU/EEA or the UK — including users of our free hosted service — and does not depend on whether paid plans are available in your country.

Submit a data-subject request. You can verify our representative and submit a data-subject request — access, rectification, erasure, restriction, portability, or objection — through our Euverify portal: gdpr.euverify.com/verify/f3d62d85-9dc6-472f-a512-9163bed30352. You can also contact us at privacy@ai-game.dev.

2. Information We Collect

2.1 Account Information

When you create an account, we collect your email address and a hashed version of your password. We never store passwords in plain text. You may optionally provide a display name and timezone. During registration you may also provide profile details (e.g. years of experience, roles, engines, and platforms) to help us tailor the product.

2.2 Waitlist Subscriptions

If you sign up for a game engine waitlist (e.g., Unreal Engine or Godot notifications), we collect your email address and the engine you subscribed to. This data is used solely to notify you when support for that engine becomes available. We process this on the basis of your consent, which you may withdraw at any time — by using the unsubscribe link in any such email or by contacting privacy@ai-game.dev. Withdrawing consent does not affect the lawfulness of any processing carried out before the withdrawal.

2.3 API Tokens

When you generate an API token to authenticate MCP connections, we store a SHA-256 hash of the token along with a user-assigned label, creation timestamp, and last-used timestamp. The raw token value is shown exactly once at creation and is never stored or retrievable afterward.

2.4 Billing and Subscription Information

From the effective date of this Policy, when you purchase a paid subscription or a prepaid-balance top-up, the purchase is sold and the payment taken by Paddle (the Paddle group company that acts as merchant of record for your country — Paddle.com Inc., 3811 Ditmars Blvd #1071, Astoria, New York, NY 11105-1803, USA, for buyers in the United States; Paddle.com (Canada) Ltd, 22 Adelaide Street West, Suite 3400, Toronto, Ontario, M5H 4E3, Canada, for buyers in Canada; and Paddle.com Market Limited, registered in England and Wales, company no. 08172165, 30 Old Bailey, London EC4M 7AU, United Kingdom, for buyers everywhere else. The company that sold to you is named on your Paddle receipt and invoice) acting as merchant of record (see our Terms of Service, Section 1.1). Paddle collects and processes the data needed to sell you the product and take payment — typically your name, email address, billing address and country, IP address, any business tax identifier you enter, and your payment-card or other payment details. Paddle's handling of that data is described in Paddle's privacy notice.

To operate your entitlement we store, on our side, a Paddle customer identifier, the Paddle transaction and subscription identifiers, your plan, billing period, subscription status, and renewal/cancellation timestamps. Where you were shown the pre-payment consent checkboxes required in the EU/UK, we also store an append-only consent record (the transaction identifier, which disclosure version you were shown, and the time) as evidence of that consent.

Card details are entered in the payment provider's hosted checkout and never touch our servers — we do not see, receive, or store full card numbers. We receive back only the limited information needed to operate the subscription (such as the last four digits of the card, card brand, payment status, and tax/invoice metadata).

Legacy subscriptions. Subscriptions bought before the effective date of this Policy were sold with us as merchant of record and payment processed by Stripe. They are not migrated: for as long as such a subscription remains active we continue to store its Stripe customer and subscription identifiers and Stripe continues to process the billing data described above for it.

2.5 Request Metadata

When MCP clients or the engine plugin connect through our server, we log operational metadata to maintain service quality:

• Client IP address
• Timestamp and request duration
• HTTP status code and request path
• Tool name and tool call count
• Request and response size (in bytes)
• Endpoint type (MCP or API) and client type (AI agent or plugin)

In addition, when you sign in we record the IP address and browser/device user-agent associated with that login session, so that you and we can identify and manage active sessions for security purposes.

2.6 MCP Events

We record MCP protocol-level events (tool calls, prompt retrievals, resource access, connection events) including the event type, timing, status, session identifiers, the tool, prompt, or resource referenced, and any error details. These events help us monitor system health and debug issues.

2.7 What We Do NOT Collect

We do not collect, store, or have access to:

• The content of conversations between you and your AI assistant
• Your source code, project files, or game assets
• Scene data, game design documents, or creative content
• Any data from your local project beyond the MCP tool calls you initiate
• Your full payment-card number, which is handled entirely by the payment provider (Paddle, or Stripe for legacy subscriptions)

The MCP server acts as a stateless relay — it routes tool calls between your AI client and the editor without inspecting or persisting the payload contents.

2.8 Proxied AI Usage (Paid Plans Only)

On the free tier the Service is an MCP relay only: you connect your own AI agent, and your AI prompts and completions go directly to the AI provider you chose — they do not pass through us, and we do not send them to any AI provider on your behalf.

On paid plans, our metered AI tools route your AI requests through third-party AI providers to generate completions. For this purpose, the relevant request content is transmitted to the applicable provider:

• Anthropic (United States) — processes paid AI requests routed to Anthropic's models.
• DeepSeek (China) — this is the route currently in use for the DeepSeek-family models we offer. Today, a paid request to one of those models is sent to DeepSeek and processed in China.
• Microsoft (Azure AI Foundry; United States) — an alternative hosting of the same DeepSeek-family models, which we may enable for some or all of that traffic. Where a request is served through that hosting instead, it is processed by Microsoft Corporation in the United States and is not sent to DeepSeek or to any service operated by DeepSeek. If this becomes the default route, we will say so in an updated version of this Policy.

DeepSeek-family models are not available at all to accounts in the EU/EEA, the United Kingdom, or Switzerland — on either of the two routes above. This is enforced server-side from your account country, so no personal data of those data subjects is transferred to China (or to the Microsoft-hosted route) for DeepSeek-family models.

These AI providers apply only to paid, proxied AI usage. We do not send free-tier traffic to them.

2.9 Desktop App Installation Identifier

When you use the AI Game Dev desktop app, it generates a random 128-bit identifier the first time it runs and stores it locally on your device, in the app's local configuration file. We never receive this identifier in that raw form. Instead, each time the app connects, it sends a one-way cryptographic derivation of it — computed together with your account identifier, so the value we receive is different for every account — in a request header. Because of how it is derived, we cannot use it to recognize the same installation across two different accounts, and it does not let us build a profile of your device.

We use this identifier for one purpose: to recognize that a new connection comes from an installation we have seen before, so we can close out sessions left behind when the app crashes or is force-closed, instead of leaving them to expire on their own after several hours. We do not use it for analytics, advertising, attribution, A/B testing, or to track you across other websites or services, and we do not share it with any third party.

This identifier is designed to persist across app restarts and sign-outs, because that is what lets it do its job over time; it is unrelated to the cookies described in Section 10, and nothing like it is set by the ai-game.dev website. You can reset it at any time by deleting the app's local configuration file; resetting it does not affect your account, your projects, or any other locally stored preference.

3. How We Use Your Information, and Our Legal Basis

Where data-protection law (such as the EU/UK GDPR) applies, we rely on the following legal bases for each purpose:

• Provide the Service and process payments (account creation, authentication, running subscriptions, charging and renewing paid plans) — performance of a contract with you.
• Operate and secure the platform (monitoring uptime, diagnosing errors, enforcing rate limits and usage allowances, detecting abuse, preventing fraud, and recognizing and cleaning up stale connections left behind by a crashed or force-closed app instance) — our legitimate interests in running a reliable, secure service.
• Comply with legal obligations (tax, accounting, and invoicing requirements for paid transactions) — compliance with a legal obligation.
• Send service communications (email verification, password resets, billing notices, critical service notifications) — performance of a contract and/or legitimate interests.
• Optional notifications you request (e.g. engine waitlists) — your consent, which you may withdraw at any time.

4. How We Share Your Information (Sub-processors)

We do not sell or rent your personal data, and we do not share it for third-party marketing. We share data only with the service providers (sub-processors) needed to operate the Service, and where required by law:

• Paddle (payment provider and merchant of record; Paddle.com Inc., Paddle.com (Canada) Ltd or Paddle.com Market Limited, depending on your country — see Section 2.4) — from the effective date of this Policy, Paddle sells the purchase, takes payment, prevents fraud, calculates, collects and remits taxes, and issues invoices, receipts and refunds. Paddle acts as our processor for the billing and subscription-management data it handles on our instructions, and as an independent controller for its own merchant-of-record processing — tax determination, invoicing, and fraud, anti-money-laundering and chargeback decisioning. Paddle receives the billing data described in Section 2.4 and is governed by its own privacy notice and data processing addendum.
• Stripe (payment processor; United States) — legacy rail only. Stripe is retained solely to keep subscriptions bought before the effective date of this Policy running; no new purchase is sent to Stripe. For those legacy subscriptions we were the merchant of record, and Stripe acts as our processor for subscription management and as an independent controller for its own fraud-prevention and anti-money-laundering purposes. Stripe receives the billing data described in Section 2.4 for those subscriptions only, and this row falls away once the last legacy subscription ends.
• AI providers — Anthropic (US), DeepSeek (China) and Microsoft (Azure AI Foundry, US) — process paid, proxied AI requests only (see Section 2.8). Free-tier traffic is never sent to them. DeepSeek-family requests are currently processed by DeepSeek in China; the Microsoft-hosted route is an alternative we may enable for that traffic. DeepSeek-family models are not offered to EU/EEA, UK or Swiss accounts on either route.
• Server hosting / infrastructure provider — hosts the application, database, and supporting services strictly as needed to run the platform.
• Email delivery — handled by our self-hosted mail service on our own infrastructure; transactional email is not shared with a third-party email-marketing provider.
• Analytics (Umami) — self-hosted on our own infrastructure; anonymous usage statistics only, not shared with third parties.
• Legal and safety — when required by law or valid legal process, or to protect the security, rights, and integrity of the service and its users.

5. International Data Transfers

Our infrastructure, our payment providers, and our AI providers may process your data in the United States, the United Kingdom, the European Union and other countries outside your own. Where we transfer personal data of EU/UK individuals to a country that has not been recognized as providing an adequate level of protection, we rely on appropriate safeguards — principally the European Commission's Standard Contractual Clauses (SCCs) and, for UK transfers, the UK International Data Transfer Addendum.

• Paddle (merchant of record, from the effective date of this Policy) — Paddle's data processing addendum provides that personal data transferred out of the EEA or the UK is processed either in a jurisdiction recognized as adequate or under the EU SCCs (Module Two: controller to processor), with the UK International Data Transfer Addendum covering the UK leg. We do not rely on the EU–US Data Privacy Framework for this transfer.
• Stripe (legacy subscriptions only) — transfers rely on the EU SCCs and the UK International Data Transfer Addendum incorporated in Stripe's data processing agreement, for as long as any legacy subscription remains active.
• Anthropic (United States) and Microsoft (Azure AI Foundry, United States — where that route is in use for DeepSeek-family models) — transfers rely on the SCCs in their respective data protection terms.

DeepSeek (China). DeepSeek's own service in China is the route currently used for the DeepSeek-family models, so a paid request to one of those models is processed in China today; the Microsoft-hosted route described in Section 2.8 is an alternative we may enable for some or all of that traffic. To avoid transferring EU/EEA, UK or Swiss personal data to China, DeepSeek-family models are not available to accounts in the EU/EEA, the United Kingdom, or Switzerland at all — this is enforced server-side based on your account country, and is not conditional on which of the two routes is in use. As a result, no transfer of EU/EEA, UK or Swiss personal data to China occurs through the Service.

6. Data Storage and Security

Your data is stored in a PostgreSQL database on our server infrastructure. We use industry-standard security practices:

• All connections are encrypted with TLS (HTTPS) via automatically renewed certificates
• Passwords are stored as bcrypt hashes and API tokens are stored as SHA-256 hashes — never in plain text
• Payment-card data is handled by the payment provider (Paddle, or Stripe for legacy subscriptions) and never stored on our servers
• JWT-based session tokens have configurable expiry (15-minute access tokens and 7-day refresh tokens, or 30-day refresh tokens if you choose “remember me”)
• Redis-backed rate limiting protects against brute-force attacks
• Admin endpoints require a separate API key

7. Data Retention

• Account and profile data is retained for as long as your account is active. You can request account deletion at any time, after which we delete or anonymize your account data within a reasonable period, subject to the billing/tax exception below.
• Billing, invoice, and tax records are retained for at least 7 years (and longer where required — for example, approximately 10 years for EU VAT purposes) after the transaction to comply with tax, accounting, and audit obligations, even after account deletion.
• Checkout consent records (Section 2.4) — the evidence that you were shown and accepted the pre-payment disclosures required in the EU/UK — are retained for six years, running from the end of the subscription period that the payment covered (for a prepaid-balance top-up, from the date of the transaction), because they exist precisely to be produced if a charge is disputed long after it was made. This period is separate from, and shorter than, the tax-record period above. Deleting your account does not destroy this evidence; instead the record is de-identified so that it no longer points at your account.
• Operational request logs and MCP events are used primarily within a rolling 90-day window for analytics, monitoring, and reporting in our dashboards. We retain these operational records until they are no longer needed and are purged, and we work to minimize how long identifiable log data is kept. We do not currently guarantee automatic deletion at a fixed age.
• Aggregated admin statistics are stored for approximately 42 days in 30-minute intervals, then aged out.
• Verification and reset tokens expire automatically (48 hours for email verification, 1 hour for password resets).

8. Open Source Transparency

Much of the AI Game Dev ecosystem is open source, and you can read that code yourself. The components that run on your own machine — the per-engine editor plugins, the engine-agnostic MCP server they share, and the .NET MCP framework beneath them — are public repositories. Because those are the components that decide what leaves your computer, you can inspect them to see what the client sends to us, and when:

• Unity-MCP — Unity Editor plugin
• Godot-MCP — Godot Editor plugin
• Unreal-MCP — Unreal Engine plugin
• GameDev-MCP-Server — the engine-agnostic MCP server shared by the plugins above; it runs locally on your own machine
• MCP-Plugin-dotnet — the underlying .NET MCP framework

What is not open source. The hosted service at ai-game.dev — this website and the cloud server that receives your requests, holds your account, and proxies paid AI requests — is proprietary, and its source code is not published. You cannot verify our server-side handling by reading its code. What we do with your data on the server is described in this Policy, and the rights in Section 9 — including access, correction and erasure — are how you can check and control it in practice.

9. Your Rights

Depending on where you live, you may have the right to:

• Access the personal data we hold about you
• Correct inaccurate information in your account
• Request deletion of your account and associated data (subject to legal retention)
• Object to or restrict certain processing, and withdraw consent where we rely on it
• Receive a copy of your data in a portable format. You can export your usage data directly from your dashboard; for a copy of other personal data we hold, contact us and we will handle the request manually
• Revoke any API tokens at any time through your dashboard
• Lodge a complaint with your local data-protection authority

To exercise any of these rights, EU/EEA and UK data subjects can use our Euverify data-subject request portal; you can also email us at privacy@ai-game.dev. Exercising these rights is free of charge. We will respond to your request within one month. Where a request is particularly complex or you have made a number of requests, we may extend this period by up to a further two months, and we will tell you within the first month if we need to do so and why.

10. Cookies and Tracking

We use JSON-based authentication tokens — not cookies — for session management. When you sign in, the Service returns short-lived access and refresh tokens in the login response, and your browser or client stores them and sends them back on each request to keep you signed in. We do not use advertising cookies, tracking pixels, or third-party analytics that track you across websites.

We use Umami, a privacy-focused, open-source analytics tool, to collect anonymous usage statistics (page views, referrers, browser type). Umami is self-hosted on our own infrastructure — no data is shared with third parties. It does not use cookies and does not track individual users across sessions.

The Paddle checkout — which opens over our pricing and account pages for new purchases — may set cookies or equivalent storage necessary for payment security and fraud prevention; these are set by Paddle and governed by Paddle's own privacy notice. The Stripe-hosted checkout and customer portal may likewise set such cookies where they are still reached for a legacy subscription; those are governed by Stripe's own privacy policy.

11. Children's Privacy

The free Service is not directed at children under 13, and paid subscriptions require the subscribing account holder to be at least 18, or a parent or legal guardian acting on behalf of a user who is at least 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, please contact us and we will promptly delete it.

12. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated version number and effective date, consistent with our Terms of Service.

For material changes that affect a paid subscription or that are required by mandatory consumer or data-protection law, we will give you advance notice by email before the change takes effect and a reasonable opportunity to terminate your subscription if you do not accept the change. For non-material changes, continued use of the service after the changes take effect constitutes acceptance of the updated policy. Your mandatory statutory rights as a consumer and data subject are unaffected.