Privacy Policy

Effective September 16, 2026

Pixel Engine turns prompts and images into pixel art and animations for games. This page says what we collect to do that, why, who processes it on our behalf, how long we keep it, and what you can do about it. It is written to be read, not skimmed past.

Who we are

Pixel Engine (pixelengine.ai) is operated by Pixel Engine, an independent developer. For anything in this policy, write to hello@pixelengine.ai.

What we collect

Account. Your email address and a password you choose, or, if you sign in with Google, the email and name Google shares with us. We do not see your Google password.

Your content. The prompts you write, the images you upload, and the images and animations we generate for you. We also keep a record of each generation job: what was requested, when, which model ran it, and what it cost.

Payments. Purchases and subscriptions are handled by Stripe. We store your Stripe customer and subscription identifiers and your credit balance and history. We never see or store your card number.

Usage. Which features you use and when, page views inside the app, and events such as a completed signup or a submitted job. This is tied to your account so we can understand how the product is used. We do not record your screen or your keystrokes.

Technical. Ordinary server logs: request times, error messages, and the identifier of the API key or connected agent that made a request.

Anti-abuse signals. A small amount of information about the browser and device used to create an account, so that we can tell when one person is creating many accounts to claim free credits repeatedly. This is a first-party cookie, a coarsened version of your network address that identifies your network rather than you, and a short code calculated from ordinary device characteristics such as screen size, time zone, language, and how your graphics hardware draws a test image. That code cannot be turned back into any of those details and is not used to identify you personally, to build a profile, or to track you across other websites. We use it only to count accounts per device, and we do not share it.

How we use it

  • To run the service: generate what you asked for, show you your library, and keep your balance right.
  • To operate your account: sign you in, send the emails the account needs (confirmation, password reset, receipts), and answer support requests.
  • To improve the product: see which features get used and where people get stuck.
  • To keep the service safe: detect abuse, enforce credit limits, and debug failures.

We do not sell your data, and we do not use your prompts, uploads or generations to train models.

Who processes it for us

Running Pixel Engine means passing some of your data to services that do a job for us. Each one receives only what its job needs.

  • Supabase — our database, sign-in, and file storage. Holds your account, job records, and media.
  • Vercel — hosts the website and app.
  • Modal — runs the models that generate images and animations. Receives your prompt and input image for each job.
  • Google (Gemini) — used to rewrite short prompts into the style our animation models expect, and, when you choose a Nano Banana model, to generate images. Receives the prompt and the image involved in that step.
  • OpenAI — generates images when you choose a GPT image model. Receives the prompt and any reference image.
  • Stripe — payments and subscriptions.
  • PostHog — product analytics, as described under Usage above.
  • Resend — sends account email.

These providers process data in the United States. We do not share your data with anyone else, except if the law requires it.

Connected agents

You can let an AI agent you use elsewhere (for example in a chat assistant or a coding tool) work with your Pixel Engine account. When you approve one, it can generate and animate on your account, spend your credits, and see your balance and the jobs it created. It never sees your password. Each connected agent is listed under Account → Connect an agent, and disconnecting it takes effect immediately. What the agent does with the images it receives is governed by that agent's own privacy policy, not this one.

The API

If you use the API, we store only a hashed form of your API keys; the key itself is shown once. Output files from API jobs are deleted 24 hours after the job is created. The job record itself is kept for billing and support.

How long we keep things

  • Images and animations you make in the app stay in your library until you delete them or your account.
  • API job outputs are deleted 24 hours after the job. Uploaded API inputs are kept only as long as the job needs them.
  • Job and credit records are kept while your account exists, because they are your billing history.
  • Deleting your account removes your account and its media, cancels any active subscription, and ends analytics tied to you. Payment records stay with Stripe as the law requires. Routine backups age out over the following weeks.

Your choices

We use cookies only to keep you signed in, for the analytics described above, and for the anti-abuse signals described above. There is no advertising on Pixel Engine and no advertising cookies.

Age

Pixel Engine is not directed at children under 13, and we do not knowingly collect data from them. If you believe a child has created an account, contact us and we will remove it.

Changes

If this policy changes in a way that matters, we will update the date at the top and, for significant changes, tell signed-in users in the app.