Privacy Policy

Last updated: 2026-11-19

quine runs as an Android app and in your web browser (the browser version is served from this website). This policy explains what happens to your data in both. It is written to be plain and honest, not to be exhaustive legalese.

An account for your apps, no analytics

Apps you open by link play without an account. Creating apps needs a quine account (see "Your quine account" below); a device can be set to "Apps without an account" in the Developer settings, which lets you create apps without an account and sends nothing to a server until you log in. The app contains no analytics and no third-party tracking. The "worlds" you create and your conversations with the assistant are stored on your device:

This website is served by Cloudflare. Like any web server, Cloudflare receives your IP address when your browser loads it; see the Cloudflare Privacy Policy. The quine developer keeps no log of your requests.

Your quine account (optional)

"Log in" in the Android app's Settings or in the web app creates or opens a quine account, which keeps your apps in sync across your devices and lets you share an app by link. Logging in happens on a page of WorkOS (api.workos.com), our login provider: you enter your email address and a one-time code that WorkOS emails you, or you choose Google. WorkOS receives your email address (and, if you choose Google, the name and picture Google passes on) and quine never sees a password. After logging in, quine keeps a login token on your device (in this website's storage in your browser, encrypted in the Android keystore) and sends a short-lived access token only to quinegames.com, our server on Cloudflare (Android app versions from before the move to quinegames.com send it to quine.felx.me, the same server), when you sync an app, share an app by link or delete your account. The tokens are never written to your worlds, conversations or logs. "Log out" forgets the login on your device and ends it at WorkOS.

For each account, quine's server stores only an internal account number, the account's WorkOS user ID, when the account was created and, only if you pick one, your public name for the community (see Showing an app in the community): no email address, no other name and no log of your requests. It keeps them until you delete the account; "Delete account" deletes them at once, and the account at WorkOS with them (see Deleting your data).

Apps synced with your account

While you are logged in, quine syncs each of your apps with your account: the whole app exactly as your device holds it, with its conversation with the assistant, its data and everything the app stored (for example photos and recordings). It is compressed, uploaded to quinegames.com, our server on Cloudflare (Workers and R2 storage), and stored with your internal account number. quine's server can read it; it reads it only to give it back to you, and nobody else gets it. Only the newest synced version of each app is kept, up to 1 GiB per account. Logging in on another device brings your apps there. Deleting an app in quine deletes its synced copy at the server, so it does not come back on your other devices; "Delete account" deletes all synced copies.

The community link

The landing page loads an online member count image directly from Discord. Discord receives your IP address when that image loads, but no quine app data or OpenRouter key. The image request sends no referrer. If you follow the community link, Discord's privacy policy applies.

Email updates

The website's Subscribe link opens a signup page hosted by EmailOctopus, which may use Google's reCAPTCHA to prevent automated submissions. Only that page, on EmailOctopus's own website, receives network information such as your IP address and browser information; Google may use cookies for this protection. The quine website itself loads no EmailOctopus or Google scripts, so they cannot reach the quine apps, conversations or OpenRouter key stored in your browser.

If you subscribe, your email address and subscription information are stored by EmailOctopus for the developer to send occasional quine releases and examples. Signing up is optional and is not required to use quine. You can stop receiving updates using the unsubscribe link in an email. To request deletion of your subscription data, write to quine@felx.me.

Your OpenRouter key

The assistant runs on an AI service reached through OpenRouter, using your own OpenRouter API key. You get it by signing in with your OpenRouter account, or you paste a key you created yourself. Signing in happens in your browser on openrouter.ai; OpenRouter then hands quine an API key that belongs to your account, and quine never sees your OpenRouter password. You can revoke the key at any time in your OpenRouter account. To show the list of available models, quine also loads OpenRouter's public model list, without sending your key.

The quine app sends the key only to OpenRouter. It is never written to your worlds, your conversations or logs. Removing the key in quine's Settings deletes it from your device only; it stays valid until you revoke it in your OpenRouter account.

AI credit

Instead of your own key you can buy AI credit in the web app, after logging in. The checkout opens in a new tab on Stripe's website. Stripe sells you the credit as merchant of record ("Sold through Link") and collects your payment details, email and country under Link's privacy policy; quine's website loads none of Stripe's scripts. Stripe tells quine's server about each purchase, refund and payment dispute: its payment number, the pack bought, the amount paid and your internal account number. The server keeps for each purchase, refund and dispute its payment number, the credit it added or took back, the amount it stands for and when.

For your credit, quine's server creates an OpenRouter API key in quine's own OpenRouter account, named with your internal account number, whose spending limit is your credit. The server keeps it encrypted; your browser stores it in this website's local storage, like your own key, and sends it only to OpenRouter. Logging out removes it from the browser. With credit, your requests to the AI go from your browser to OpenRouter as described below, and OpenRouter bills them to quine; quine sees how much of the key's limit is used, not what you sent.

Your ChatGPT sign-in

Instead of an OpenRouter key you can sign in with your ChatGPT account in the Android app's Settings ("Continue with ChatGPT"). Signing in happens on openai.com in your browser; quine never sees your ChatGPT password. If you choose it, the assistant's requests, and the text requests of the apps you build, go from your device directly to OpenAI, never through a server of ours, and use your ChatGPT plan, under OpenAI's privacy policy. When you sign in, quine sends OpenAI a random identifier of this installation; it stays on the device after you sign out. Pictures the apps draw still go to OpenRouter with your key.

Signing out in quine's Settings revokes the sign-in at OpenAI and deletes it from your device. You can also disconnect quine in your ChatGPT settings.

What is sent to the AI service

When you use the assistant, the following are sent to OpenRouter (or to OpenAI, if you signed in with ChatGPT) and the AI model provider you selected, so they can generate a response:

Along with your messages quine tells the assistant which device it runs on (device model, Android version and quine version). Each app also has a random identifier that is sent to OpenRouter (or OpenAI) with every request, so that the requests of one app belong together; it is not tied to you or your device. Apps you build can ask the AI themselves, for example to write text or draw a picture, and their content goes to the same AI service the same way.

In the browser, these requests go directly from your browser to OpenRouter. This data is handled under the privacy policies of OpenRouter and the respective model provider; see OpenRouter's privacy policy. The quine developer does not receive or store it.

Attachments and voice messages

A photo, audio file or voice message you attach is stored inside that app on your device, as part of its conversation with the assistant. It is sent to the AI service with the request it belongs to, and again with later requests while it is part of the conversation the assistant reads, so the assistant keeps seeing what you showed it. Deleting that app in quine, or uninstalling quine, deletes it.

Camera and microphone inside your apps

An app you build can take a photo or record sound, but only when you tap or press a key to start it. The photo or recording is stored inside that app on your device, and it is sent to the AI service only if the app or the assistant includes it in a request. Taking photos uses your device's camera app; recording sound needs the microphone permission.

An app you build can also open a file or save one, but only when you tap or press a key, and only through your device's own file dialog, in which you choose the file or the place. The app receives just the file you picked (its name and content), never access to your other files. What it opened is stored inside that app like its other content: it is sent to the AI service only if the app or the assistant includes it in a request, and it is part of the app when you share or export it.

Speech recognition

Dictation, and an app that asks you to speak, use your device's speech recognition service. It needs the microphone permission and may process the audio on your device or on the servers of its provider (usually Google), under that provider's privacy policy. quine receives only the recognised text, and it listens only while that world is visible on your screen.

Web access

The assistant and the apps it builds can load web pages and call web services on your behalf, for example to look something up. Those websites receive the request and your IP address, under their own privacy policies. An app can also send data you put into it to public websites; quine only makes such requests over encrypted (https) connections. Web searches are sent through OpenRouter, using your key, to the search engine it uses (currently Exa). In the Android app web access can be switched off in Settings. In the browser, such requests are sent by your browser and only reach sites that allow it.

Sharing an app

When you back up an app, the file contains the whole app: its content, everything stored inside it (for example photos or recordings it took) and its conversation with the assistant, including the photos, audio files and voice messages you attached. The file also names the device it was made on (model and Android version). When you share an app, quine sends the app as a new person receives it: without what you stored while using it (your entries, progress, photos it took) and never with its conversation. Before you share, quine shows what comes with the app and what stays with you. Whoever receives a file can read all of it. Nothing is shared unless you choose to.

When someone opens your shared app from its link and that makes a new copy on their device, their device tells quine's server, without any identifier of the person or the device; the server only adds one to a count for that app and stores no IP address and no time. quine shows that count, and how many other shared apps were copied from yours, only to you. "Stop sharing" and "Delete account" delete the count.

Showing an app in the community

"Show in community" on an app you shared by link lists it on quinegames.com for everyone, without a login. It needs a public name, which you pick in Settings (3 to 24 of a-z, 0-9 and _) and can change there; quine's server stores it with your internal account number. A listed app's card shows its name and preview picture (read from its newest shared version), your public name, the tags you picked for it from quine's fixed list, the number and average of its ratings (below) and, if the app was copied from another app that is listed, that app's name and link. Anyone can then find the app and open it and every earlier version of it, as anyone with its link already can. The server also stores when you first showed it, whether it is shown now and its tags. "Hide from community" takes it out of the list and keeps its tags and ratings; "Stop sharing" and "Delete account" delete its listing with its tags and ratings. If we clear a public name that breaks the Terms of Use, the reason is stored with your account number and shown to you in Settings until you pick another name; the cleared name itself stays stored so that nobody can pick it again, and it is kept when you delete your account (without anything that links it to you).

"Rate" (after logging in) gives an app listed in the community one to five stars; you cannot rate your own apps. Quine's server stores your stars with your internal account number, the app's listing and the time you last rated it, and keeps them when the app is updated, hidden or shown again; rating again replaces them. Nobody but you is shown your stars: the community page shows only how many ratings an app has and their average, and your public name is never shown with a rating. Your ratings are deleted when you delete your account, and an app's ratings when its author stops sharing it or deletes their account.

Reporting AI content

In the Android app and in the browser app you can report a message from the assistant, or an app's AI-generated content, to the quine developer. Only when you send a report, quine transmits: what you reported (a message or an app), the reason you picked, your optional note, the text of the reported assistant message, the name of the AI model in use, quine's version number and, for an app you opened from a share link, that link, so the developer can find the app. Your messages, attachments, apps and keys are never included, except what you write in the note and what the reported assistant message itself quotes. Reports are delivered through Google Forms, so Google also receives your IP address, under the Google Privacy Policy. Each app card on the landing page has a Report link. It opens the same Google Form in a new tab, with the app's link already filled in. That form is Google's own page, so Google sees your IP address and, if you are logged in to Google, your Google account. A report sent from inside the app does not reveal this. We receive only what you enter in the form. The developer uses reports only to improve how quine prevents harmful content. A reported assistant message is hidden in its conversation on your device.

Permissions

The Android app asks for: internet access, to reach OpenRouter, OpenAI and the web; the microphone, only when you record a voice message, dictate, or start a recording in an app; and notifications, to show "Agent is generating…" while the assistant answers. While it answers, the app keeps running briefly in the background (an Android foreground service) so the answer arrives; it stops when the answer is done. quine does not ask for the camera permission: photos are taken by your device's camera app. quine never reads your location, contacts or files, except those you pick yourself to attach, import or open in an app.

Deleting your data

Children

quine is not directed at children.

Changes to this policy

This policy may change. The "Last updated" date above reflects the current version.

Contact

Questions about this policy: quine@felx.me