Privacy policy

Information handled in the browser

Session storage remembers three temporary preferences: whether the adult notice has been passed, which fictional editorial persona is selected, and which comparison lens is active. These values stay in the browser session and are used only to keep the interface consistent while pages are open.

The prompt workshop assembles a draft from predefined scene, signal, and boundary choices. The generated text is displayed locally. It is not submitted to AI Chat XXX, added to the commercial redirect, or included in publisher analytics.

Commercial handoff data

When a commercial button is submitted, the server receives one opaque offer ID. It validates the request method, origin, content type, field count, identifier format, and allowlist membership. Valid requests are redirected to a server-configured HTTPS destination. Invalid requests fail without a destination header.

The application event design excludes prompt text, intimate preferences, typed names, email addresses, raw IP addresses, user-agent strings, and destination tokens. Infrastructure providers may still process network information needed to deliver and secure the site under their own terms.

External services

After a redirect, the destination service may request an account, set cookies, process subscription details, or store conversations according to its own privacy policy. Those activities occur outside this domain. Review the destination’s current privacy, deletion, export, retention, and payment terms before supplying personal information.

Your practical choices

• Close the browser session to clear the temporary session-storage selections.
• Avoid entering real names, addresses, workplaces, contact details, account identifiers, or sensitive personal facts into roleplay prompts.
• Use invented settings and character details when specificity is useful.
• Do not submit a commercial button if you do not want to leave this site.

Contact and policy changes

A public privacy-contact route will be published only when a monitored recipient is configured and tested. Until then, this local release candidate does not invent an address or display an unmonitored form. Material changes to the data flow require a new policy version and updated effective date.