Privacy policy

Last updated 14 October 2026

The short version

We keep an account for you, a count of what you have run today, and nothing else. Your photos are not written to our disks unless you publish one. They pass through our server in memory, go to whichever AI model you chose, and come back to your browser or your phone, where they are stored on your own device. We do not sell or share personal information. We measure how the site is used so we can improve it, with our own first-party analytics rather than an advertising network, and we never see your card number.

Who we are

PixelFire is operated by Timeslice LLC. For anything in this policy, write to support@pixelfire.ai and a person will answer.

What we hold

Your account

When you sign in with Google or with Apple we receive, and keep, the identifier that provider uses for you, your email address if the provider supplies a verified one, and your display name and profile picture if they are offered. We mint our own random account id and everything else hangs off that, not off your email. Sign in with Apple stops sending your address after the first authorization and Hide My Email gives us a relay alias you can sever at any time — both work fine, because we never treat an email address as your identity.

Your photos

A photo you upload is held in memory for the length of the request, sent to the model or models you selected, and returned to you. It is not written to our databases, our log files or our storage buckets. Finished images are stored by the app in your own browser (IndexedDB) or on your phone; clearing that storage removes them, and we cannot recover them for you because we never had a copy.

There is exactly one exception, and it only happens when you ask for it.

Publishing a result

You can publish a single before-and-after to a page anyone with the link can open. Doing that does copy those two pictures, and the prompt you typed, to our storage — it is the only circumstance in which a photograph of yours is written to our disks. Nothing is published automatically, nothing is published by sharing or saving inside the app, and there is no setting that turns this on in advance. It happens when you press a button that says it will.

A published page has an address that cannot be guessed and is marked so search engines will not index it, but anyone you give the link to can open it and pass it on. Treat it as public.

You can unpublish at any time, from the same place you published. Unpublishing deletes the stored pictures rather than hiding the page. Deleting your account unpublishes everything you have published, for the same reason.

Your prompts

The text of a prompt does appear in our server logs, alongside the model, the quality setting and how many reference images were attached. Those logs live in Google Cloud Logging and are deleted on that service's default schedule, which is thirty days. Photos are never logged. If you would rather your prompt text was not written down at all, say so at support@pixelfire.ai and we will tell you plainly what we can do about it.

What you have run

We store a count of the generations you have run today, split between the fast models and the best ones, and the size of any pack you have bought. Yesterday's count is dropped the next time you run anything. It is a count, not a history: it does not record what you asked for or what came back.

Payment information

On the web, payment is handled entirely by Stripe. On iPhone and iPad it is handled entirely by Apple, with RevenueCat relaying the result to us. We receive the fact of a successful payment, which plan it was for, and an identifier for the subscription. We never receive or store your card number.

Technical records

Our servers log the usual request metadata — IP address, user agent, path, status, timing — for security and debugging, on the same thirty-day schedule.

How the site is used

We keep our own record of how PixelFire is used, because without it we cannot tell which parts work. It is first-party: the data is ours, it stays on our own infrastructure, and it is not sold, shared or used to target advertising.

We set one cookie, pf_v, holding a random identifier and nothing else. It lets us tell one visit from another so we can count people rather than page loads. It lasts a year, it is not readable by JavaScript, and it carries no name, address or anything derived from you. Comparison pages count a view with a one-pixel image, because those pages carry no JavaScript at all.

What we record is a fixed list of moments: a page viewed, an edit started, a picture finished, reaching the day's limit, the prices being looked at, a checkout begun, a payment settling. Each one is stored with the random identifier, your account id if you are signed in, and a small set of labels such as which plan or which model. We do not record the content of your prompts or anything about your photographs in this system, and the list of things we can record is closed — adding to it takes a code change.

Individual records are deleted after ninety days. The daily totals they roll up into are kept, because by then they are counts with nobody in them.

We also send a handful of these moments to PostHog, a product analytics service, so we can see how many people go from signing up to choosing a plan: a page viewed, the prices being shown, a checkout begun, a subscription started or cancelled. They carry your account id if you are signed in, the plan and price, and whether it happened on the web or in the app, never your name, email, prompts or photos. On the web PostHog keeps a random identifier in your browser to tell visits apart. Session recording, heatmaps and surveys are switched off.

We do not use Google Analytics.

What we never do

• We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under California law.
• We run no advertising network. Nothing here is used to target advertising, on this site or anywhere else.
• We do not use your photos to train any model of our own. We do not have one.
• We do not use your photos or prompts to build a profile of you.

Who else sees it

We use a small number of services to run PixelFire. Each one gets only what it needs to do its job:

The model providers' API terms state that content submitted through their APIs is not used to train their models. We rely on those terms, we do not control them, and we will tell you if they change in a way that affects this.

We will also disclose information if the law genuinely requires it, and if PixelFire is ever sold or merged your account would move with it — in which case this policy travels with your data until you are told otherwise.

Where it is processed

PixelFire runs in the United States and the services above process data in the United States. If you use it from elsewhere, you are sending your information to the United States.

How long we keep it

Your account stays until you delete it. Today's count is dropped the next time you run anything. Server logs are deleted after thirty days. Photos are never retained at all, so there is nothing to expire.

Deleting your account

There is a delete button on your account screen. It is immediate and it is real: your account record, everything stored under it, and the links to Google and Apple are removed, and where you signed in with Apple we also revoke the token so Apple stops listing us in your sign-in settings. It cannot be undone, and any pack you have bought goes with it. An active subscription should be cancelled first, or you will keep being billed for an account that no longer exists.

You can also ask us to do it, or to send you a copy of what we hold, at support@pixelfire.ai. We answer within thirty days and we do not charge for it.

Your rights

Depending on where you live you may have the right to see what we hold, correct it, delete it, take a copy elsewhere, or object to some of it. If you are in California you additionally have the right not to be discriminated against for exercising any of that — and since we sell no data and run no advertising, the "do not sell or share" right has nothing to act on here. Every one of these requests goes to the same address: support@pixelfire.ai.

Children

PixelFire is not for children under 13, and we do not knowingly collect anything from them. If you believe a child has an account, write to support@pixelfire.ai and we will remove it.

Security

Traffic is encrypted in transit. Sign-in tokens are verified against Google's and Apple's own keys on every request and are never stored in your browser's localStorage, so a stale token cannot outlive the tab. No system is perfect and we will not claim otherwise; if you find a problem, support@pixelfire.ai reaches us directly.

Changes

If this policy changes materially we will post the new version here with a new date and, where the change affects data we already hold, tell account holders by email before it takes effect.