Privacy Policy

What we collect when you use Pixelfork, why, who helps us, and the rights you have. No surprises.

Draft for review · not in effect yet Effective 1 November 2026 Last updated 11 October 2026

The short version

  • We collect what Pixelfork needs: your email, an optional name, and what you make: requests, chats, files and games.
  • AI providers build your games. Your requests and game files are sent to them to do that, and they can't train their models on it.
  • Our team may look at prompts and results to fix problems, keep Pixelfork safe and make it better. We don't sell your data or show ads.
  • Published games are public, with your profile name on them.
  • No ad cookies. Analytics cookies only if you say yes.
  • You're in control: ask us for a copy of your data or to delete it at any time.

This summary helps you read the page. The full text below is what counts.

1.Who we are

Pixelfork is made by CoRemote OÜ, a company registered in Estonia (registry code 17085354, Liikuri tn 16, 13618 Tallinn). We decide how your personal data is used for Pixelfork, which makes us the “controller” under the EU General Data Protection Regulation (GDPR).

This policy covers pixelfork.ai, the Pixelfork app and the games published on Pixelfork. For questions or requests about your data, write to dev@pixelfork.ai.

2.What we collect

Your account

Your email address, and the name you give us (optional; it shows on games you publish). If you sign in with Google, we get your name, email and profile picture from Google. We also keep how you signed up, your plan and credits, and when you were last active.

What you make

Your requests and chat messages, the files you upload (images, sounds, 3D models, fonts, videos), images generated for you and the prompts behind them, your games with every version, their Game notes, what you enter when you publish (name, description, thumbnail), feedback you send us, and reports you make about published games.

How you use Pixelfork

Records of the work Pixelfork does for you (what was asked, the steps, the AI's input and output, time and credits used), the days you were active, and plays of published games.

To count visitors to our website, we turn your IP address and browser into a code that changes every day and can't be turned back; we don't store the IP address itself. Our hosting providers keep short-term technical logs, including IP addresses, to run and protect the service.

Analytics, only if you accept analytics cookies: PostHog and Google Analytics record the pages you open, what you click and how long you stay, with your browser, device and approximate location. When you're signed in, PostHog links this to your account's email, so we see one history per person. More in Cookies and browser storage.

Errors: when something breaks in Pixelfork, we record the error with technical details (the page, your browser, and your account's ID and plan, never your name or email) to fix it.

Google Search Console shows us, in totals, how often pixelfork.ai appears and is clicked in Google Search. It doesn't run on our pages and gives us nothing that identifies you.

Payments

Payments are processed by Stripe, which collects your card and billing details for us. We receive only what we need to give you what you bought and keep our accounts: which plan or pack, the amount, your billing country and the last digits of your card; never your full card number. Stripe also uses some payment data itself to prevent fraud and meet its legal duties, under Stripe's privacy policy.

3.How we use it, and why we're allowed to

Under the GDPR we need a legal reason for each use. Here's ours:

What forWhat we doLegal reason
Running PixelforkYour account, building and changing games with AI, saving versions, publishing, remixing, exports, creditsOur contract with you
Sign-in emailsSending the link that signs you inOur contract with you
SafetyBlocking throwaway emails, preventing abuse and fraud, reviewing reports, taking games downLegitimate interest, and legal duties
Improving PixelforkOur team looking at prompts, chats and results to fix problems and improve how games are madeLegitimate interest (you can object)
Counting visitsDaily visitor and play counts, from codes that can't identify youLegitimate interest
AnalyticsSeeing how Pixelfork is used, with PostHog and Google Analytics, only if you accept analytics cookiesYour consent
Fixing errorsRecording what broke, with technical detailsLegitimate interest
Product newsEmails about new features, only if you've agreedYour consent
PurchasesGiving you the plan or credits you boughtOur contract with you
The lawKeeping records of purchases, answering authoritiesLegal duties

We don't sell your data, we don't show ads, and we don't use your data to make decisions about you that have legal or similar effects.

4.AI and your content

To build and change your games, Pixelfork sends your request, the files and pictures involved, your game's code, its Game notes, recent chat and screenshots of the game to AI model providers. They process it on our behalf to give us the result.

No training on your content. We use these providers under their terms for business customers, which don't let them use what we send to train their models. We don't train AI models on your content either.

People can see it. A small team at Pixelfork, with access limited by role, can look at chats, games and the AI's work to answer support requests, fix problems, review reports and improve Pixelfork. When we study requests in bulk to improve Pixelfork, we first remove email addresses, phone numbers and links.

Don't put sensitive personal data (like health information or someone else's private details) into your requests or files.

5.Who we share it with

We share personal data only with the service providers who help us run Pixelfork, bound by contracts to protect it and use it only for us:

WhoWhat they doWhere
Hosting and databaseStore your account, games and files; run the websiteEU
Job serversBuild and check gamesEU (Belgium)
AI model providersBuild and change games, make imagesUS and EU
Email deliverySend sign-in emailsUS and EU
StripeProcess payments for plans and credit packs, and prevent fraudEU and US
PostHogProduct analytics, only if you accept analytics cookiesEU
Google AnalyticsWebsite analytics, only if you accept analytics cookiesEU and US
DatadogError logsEU

The current list of these companies is available on request: write to dev@pixelfork.ai.

We also share data when you choose to (publishing a game makes it public; remixes show who they came from), when the law requires it, to protect people's safety or our rights, and with a company that takes over Pixelfork, which must follow this policy.

6.International transfers

We keep your data in the EU where we can. Some providers process data outside the EU and EEA, for example in the United States. When they do, we rely on an adequacy decision (such as the EU-U.S. Data Privacy Framework) or the European Commission's Standard Contractual Clauses, with extra safeguards where needed. Ask us for a copy of the safeguards.

7.How long we keep it

  • Your account and games: as long as your account exists. When you delete a game, it's removed for good after 30 days.
  • After you close your account: we delete your personal data within 30 days, except what the law makes us keep (like payment records, usually 7 years in Estonia).
  • Records of the AI's work: up to 24 months, then deleted or made anonymous.
  • Reports and feedback: 12 months after they're handled.
  • Visit and play counts: kept as totals that can't identify you.
  • Analytics: up to 14 months in PostHog and Google Analytics.
  • Error logs: up to 30 days.

Draft: automatic deletion on these periods needs to be built before launch (today Pixelfork keeps everything), and the analytics and error-log periods set in PostHog, Google Analytics and Datadog.

8.Cookies and browser storage

Some cookies and storage are needed for Pixelfork to work, so they're always on:

  • Sign-in cookies that keep you signed in.
  • Your analytics answer (pf-analytics), kept for 6 months so we don't ask on every page.
  • Browser storage for things like the idea you typed before signing up (kept for a day), Phone or Desktop, messages waiting to send, and layout preferences.
  • A once-per-visit marker so a visit is counted once.

Analytics cookies are optional. We only use them if you choose Accept when Pixelfork asks:

ToolWhat it's forCookies, and how long
PostHogWhich pages and features people use, so we can make Pixelfork better. Sent through pixelfork.ai and kept in the EU.ph_…_posthog for 1 year, and browser storage
Google AnalyticsHow many people visit and where they come from_ga and _ga_… for 2 years

You can change your answer at any time with Cookie settings, also at the bottom of every page. If you reject after accepting, we stop and delete these cookies.

We don't use advertising cookies. Published games may use your browser's storage to save things like your best score.

9.Your rights

Under the GDPR you can:

  • get a copy of your personal data, and have it in a format you can take elsewhere
  • have wrong data corrected
  • have your data deleted
  • object to uses based on our legitimate interest, like improving Pixelfork from your prompts
  • limit how we use your data in some cases
  • withdraw consent (for example, to product emails) at any time

Write to dev@pixelfork.ai from the email you sign in with. We'll answer within one month.

You can also complain to a data protection authority: in Estonia, the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee), or the authority where you live or work.

10.Children

Pixelfork isn't for anyone under 16, and we don't knowingly collect their data. If you think someone under 16 has given us personal data, write to us and we'll delete it.

11.Security

Everything travels encrypted (HTTPS). Games and files are kept in private storage, and each game's Android signing key is encrypted. Access for our team is limited by role and every admin action is logged. Signing in uses one-time links or Google, so there's no password to steal.

No system is perfectly secure. If something happens that puts your data at risk, we'll tell you and the authorities as the law requires.

12.Changes to this policy

We'll update this policy as Pixelfork changes. We'll change the date at the top, and if a change is important we'll tell you by email or in the app before it takes effect.

13.Contact

CoRemote OÜ, Liikuri tn 16, 13618 Tallinn, Estonia. Registry code 17085354, VAT number EE102879919.

Email: dev@pixelfork.ai

Questions about this page?

Write to us at dev@pixelfork.ai. A person reads every message.

Email us