Privacy Policy

Last updated 23 September 2026.

1. Scope

This policy covers Pixels AI, operated by pixels.xyz, at gen-ai.chenfengliu.com. It does not cover the Pixels game, the Pixels website, your wallet software, or any model provider’s own site.

2. What we store

Your account. Your Ronin wallet address, the one-time number you signed to prove you hold it, when the account was created and when it was last seen. That address is public information on the Ronin chain, and it is the only identifier we hold for you.

Your sessions. For each sign-in: a hashed copy of the session token (never the token itself), the times it was created, last used and expires, and the browser identification string your browser sends. We do not store your IP address in the application database.

Your chats. Conversation titles, every message you send and every reply you receive, which model produced it, and when. This is what makes your history work. Chat text is stored in one place — the conversation record — and is not copied into our job or billing records.

What you generate. Images, video, music and speech are stored as files in Google Cloud Storage under your wallet address, and are served to your browser through links that expire after an hour.

Your calls. For each call: the model, the provider, the settings you chose (size, length, voice and so on), how many tokens or seconds the provider reported, what it cost, how large the result was, and any error. Chat message text is not stored here.

Your payments. For each deposit: the transaction hash, the sending address, the amount, the block, the price used and the credits issued. Most of that is a copy of information that is already public on the Ronin chain. Every change to your balance is an entry in an append-only ledger.

Support requests. When you write to us through the contact form we keep what you wrote, the topic, the wallet you were signed in as, the email address you gave us, and everything said afterwards on both sides. Staff notes on your request are kept too, and you do not see those.

Service records. Which models are working, the errors providers return (which may quote a fragment of a failed request), and the price of $PIXEL over time. The web server in front of the app also writes ordinary access logs, which do include IP addresses.

Staff. Staff sign in to an internal area with a pixels.online Google account; we store the name and email that Google returns for them. This does not apply to players.

3. Cookies and browser storage

One cookie, pag_session, keeps you signed in. It is a random value with no information in it, and the service will not work without it. A second cookie exists for staff signing in to the internal area. Your theme choice is kept in your browser’s own storage and never reaches us.

There are no advertising cookies, no analytics scripts and no third-party trackers on this site.

4. Who else sees it

To produce a reply we have to send your prompt to the model you chose. The models we route to are run by Anthropic and Google (through Google Cloud Vertex AI), OpenAI, and fal.ai (which hosts the video and music models). They receive the prompt, any settings and the history of that conversation, and they return the result. They do not receive your wallet address, and we do not tell them who you are.

We also rely on:

• Google Cloud — the server, the database and the storage the service runs on. The server and database are in Google Cloud’s Montreal region.
• Ronin network nodes — to read your deposit transaction. Only public chain data is involved.
• CoinMarketCap — the $PIXEL price. No information about you is sent.
• The Pixels data warehouse — our own analytics, in Google BigQuery. It receives sign-ins, deposits and one record per call with the model, provider, usage and cost, identified by your wallet address. It does not receive what you typed or what the model replied.
• Slack — internal operational alerts about the treasury. No player content.

Beyond that we share information only where the law requires it, or to investigate fraud or abuse of the service. We do not sell it and we do not share it for advertising.

5. Training

Your prompts and outputs are not used to train any model. We use each provider on its business terms, under which material sent through the API is not used for training, and we do not train models ourselves.

One model is an exception and is worth stating plainly: Claude Fable 5.1 can only be served when prompts and responses are shared with Anthropic as they happen. It is not offered to players. If that ever changes, this page will say so before the model appears, and the model picker will mark it.

6. How long we keep things

• Chats and generated files — until you remove them (see below) or ask us to erase them.
• Sessions — until they expire (30 days idle, 90 days at most) or you sign out, which revokes the session immediately.
• Deposits, charges and the ledger — kept permanently. These are financial records: we need them to prove what you paid and what you were charged, and to keep our accounts straight. They are not erased on request.
• Support requests — kept for two years after they are resolved, because they are often the reason a balance was adjusted and the ledger entry has to be explainable.
• Service records and web server logs — kept while they are operationally useful, then rotated away.

7. Deleting a chat, and asking us for more

Deleting a chat in the sidebar removes it from the app immediately: it stops appearing in your list and can no longer be opened, by you or by us through the app. The underlying rows stay in the database until they are purged, so if you want a conversation erased outright, say so through the contact form and we will do it.

Through the same form you can ask for a copy of what we hold about your wallet address, ask for corrections, or ask us to close the account. Tell us the wallet address; we may ask you to sign a message with it, because that address is the only proof of ownership we have.

Two limits are worth knowing in advance. We cannot erase anything from the Ronin blockchain — your deposit transaction is public and permanent, and nothing we do changes that. And we keep the financial records described in section 6 even after an account is closed.

8. Security

The site is served over HTTPS. Session tokens are stored hashed, so a copy of our database does not let anyone sign in as you. Generated files are private and reachable only through short-lived signed links. Access to the database and to the internal area is limited to staff who need it. No service is perfectly secure, and we will not pretend otherwise: the single most important protection on your account is control of your wallet keys.

9. Children

Pixels AI is not for anyone under 18. We do not knowingly keep information about children. If you believe a child is using the service, tell us through the contact form and we will close the account.

10. Changes

When this policy changes, the date at the top changes with it and the current version is always here. A change that materially affects what happens to your chats or your prompts will be announced in the app before it takes effect.

11. Getting in touch

Privacy questions and requests go through the contact form. The Terms of Service cover the rest of the relationship.