Privacy Policy

1. What we do not collect

You can play without signing in. We never receive your Google password, do not sell personal data, and do not run advertising or third-party advertising trackers on the site.

2. What stays in your browser

Your progress in each story, continued Contact conversations, the women/men filter and small interface preferences are written to local storage on your device. Conversation history is not stored in your account, and clearing browser data erases it for good.

3. What reaches our servers

• Story play: the messages you type or pick are sent to our servers and on to an AI model provider so the character can answer. We keep the current story's turns for as long as needed to continue it and to debug failures, and we do not attach them to any identity.
• Character creation: photos and descriptions you upload are stored so the character can be generated and then played. If you publish a character it appears on the public wall for anyone.
• Contacts: when a signed-in player unlocks a character, we store the account id, story id, character id, final-scene id and unlock date. We do not store the Contact conversation history.
• Server logs: like any website, our servers record request data such as IP address, timestamp, requested URL, referrer and user agent. We use it to keep the site up, to stop abuse and to measure load. Logs are kept for a short retention window and then discarded.
• Play statistics for signed-out players: the first time you play a story without signing in, we set a cookie holding a random id. Against that id we keep how many story scenes that browser has reached, the dates of its first and most recent play, and the IP address, country, region and city of its most recent turn as reported by our network provider. If a browser plays without that cookie from an IP address that played without signing in during the previous two hours, we reuse that address's id and set the cookie again instead of starting a new record. Separately, for each story that browser plays we keep the story id, how many of its scenes the browser reached and the dates of its first and most recent play there, so the public wall can rank stories by how much each player plays them. We do not record what was said. These records can be read only by our administrators. When you sign in from that browser, the overall scene count moves to your account and the browser's record, including the IP address and location, is deleted along with the cookie; its per-story records stay under the random id and are no longer linked to anything else.
• Play statistics for signed-in players: we keep the total number of story scenes your account has reached and, for each story you play, the story id, how many of its scenes you reached and the dates of your first and most recent play there, used only to rank stories on the public wall. We do not record what was said.
• Cookies: a sign-in session cookie, a language preference cookie, the random play id described above and, after you open a shared link, the share code described above. We do not set advertising or cross-site tracking cookies.
• Purchases: when a signed-in player starts a purchase, we create an order record holding the account id and username, the email on the account, the product bought and its price, the payment channel and method chosen, the IP address and the country and region reported by our network provider at that moment, our order number and the payment provider's reference, the amount and currency the provider reports as paid, and the order's status history. The account email, and for methods that require one a phone number you enter, are passed to the payment provider to start the payment; the order record keeps only the last four digits of that phone number. Payment itself happens on the provider's page: we never receive card numbers, bank details or wallet credentials. Order records can be read only by our administrators.
• 💵: for signed-in players we keep a 💵 balance. Each daily claim, purchase and share-link reward is logged with the account id, the kind of event, the change, the balance after it and the time; these log entries are deleted after 90 days.
• Share links: a story link shared by a signed-in player carries a short code taken from that player's account id. If you open such a link, your browser keeps the code in a cookie for up to one day. If you then play without signing in for the first time, your signed-out play record notes which player's link brought you, and that player receives a 💵 reward; if you later sign in, that note moves to your account. The code is cleared from your browser once it has been used.

4. Why we process it

To deliver the story you asked for, to generate the character you created, to understand how much the Service is played and from where, to keep the Service secure and available, to detect abuse and content that breaks our Terms of Use, and to comply with the law. Where the GDPR applies, our legal bases are performance of a contract with you and our legitimate interest in running a safe service.

5. Who else sees it

We share the minimum needed with service providers who run parts of the Service on our behalf: cloud hosting and storage, and the AI model providers that generate text and images. They act on our instructions and may not use your content for their own purposes beyond what their own terms allow for providing the service. We may also disclose data where the law requires it, or to protect people from harm.

6. International transfers

Our providers operate in several countries, so your data may be processed outside the country you are in, including the United States. Where required, we rely on standard contractual clauses or equivalent safeguards for those transfers.

7. Retention

Published characters and their generated assets are kept while they remain published. Contact unlock records are kept with the signed-in account. Order records are kept with the account for as long as it exists, as a record of what was bought and refunded; the payment provider's event notifications are kept for 180 days. Story turns are kept only as long as needed to answer and diagnose failures; conversation history remains in the browser. The play record of a signed-out browser, including its IP address and location, is deleted when that browser signs in, and otherwise 180 days after its last play. Logs are kept for a short period.

8. Security

We use transport encryption and access controls proportionate to a service that holds optional sign-in profiles and order records but no card or bank details. No system is perfectly secure, so do not upload anything you would be harmed by seeing published.

9. Children

peachi.ai is an adults-only service and is not directed to anyone under 18. We do not knowingly collect data from children. If you believe a child has sent us data, write to us and we will delete it.

10. Your choices and rights

You can clear your local story progress at any time from your browser's site-data settings. Clearing cookies also removes the random play id, so the signed-out play record can no longer be linked to your browser and expires on its own. Depending on where you live, you may have rights to access, correct, delete or restrict processing of personal data, or to object to it, and to complain to a supervisory authority.

To exercise rights over an optional account or its Contact records, write to [email protected] from the account email. For other material, include the character or story URL so we can locate it.

11. Changes to this policy

We will update this page when our practices change, and the effective date at the top will tell you when the current version took effect.

12. Contact

Privacy questions, deletion requests and takedown reports go to [email protected].