Draft for review
Privacy Policy
How the current VirtualSex app handles account information, conversations and browser storage.
1. Account information
Accounts store your email, display name, a hashed password, account identifier, creation time and the time of your adult-age confirmation. They also store your membership tier, credit balance, daily credit claims, free top-up records and unlocked media. These records support sign-in, account security and access to features. Authentication throttling also stores attempt counts and secret-key hashes derived from network addresses and submitted email addresses. Counters expire after their short sign-in or registration window; automatic database cleanup may run shortly after expiry. Raw addresses and emails are not stored in these counters.
Account records use the configured database. A local development installation can use a local account file. The age confirmation records your declaration; the current account flow does not request identity documents.
2. Conversations and AI providers
When you send a message, the app processes its text, the selected character and recent conversation history to produce a reply. When external AI is enabled, your message and recent history are sent to the configured AI provider with character instructions. Messages can contain personal information even if you do not include your name.
When database logging is configured and available, successful user messages and character replies are also stored on the server, together with the character, reply source, conversation scoring and timestamp. Safety logs store the category, reason, matched phrase, direction and time of a blocked interaction rather than the complete blocked message.
The deployment-specific provider identities, processing locations, retention practices and any model-training use still need confirmation. This draft does not promise that a provider never retains messages or uses them for training.
3. Cookies and storage on your device
Sign-in uses session cookies. The browser also remembers adult-age confirmation and character preferences, and stores conversation history locally for continuity across visits. The remembered age confirmation is checked for a 90-day validity period; that does not set the retention period for your account record.
Local conversation history is limited to the latest 200 messages per conversation and up to 50 conversations, and older entries may be removed as those limits or browser storage limits are reached. Browser history is specific to your device and browser, and is not a guaranteed backup.
You can delete saved conversations from My AI or clear this site’s browser data. Clearing local data does not delete account information, server chat logs or copies already processed by an AI provider. Blocking necessary browser storage may prevent sign-in or saved preferences from working.
4. Optional analytics
If Google Analytics is configured, it loads only after you opt in. It measures visits to eligible public pages to help understand site use. Chat, account and administration pages are excluded from page tracking, and URL query strings and fragments are removed from the page addresses sent. The app does not intentionally send conversation text, email addresses or account identifiers as analytics events.
Google Analytics can process online identifiers and device or browser information using its own technology. You can change your choice using Analytics preferences in the footer. Withdrawing permission stops future analytics collection through this integration; it does not automatically delete data already received by Google.
5. Service providers and security
Hosting, database, media delivery and configured AI providers process information needed to operate the service. Optional analytics uses Google when enabled and accepted. Infrastructure providers may process technical request information under their own service arrangements; the final policy must identify the relevant providers and any international-transfer safeguards.
Passwords are hashed before account storage and access to account features requires authentication. No system can guarantee complete security. Do not submit passwords, payment details or private information belonging to other people in conversations. The current complimentary credit and VIP flows do not collect payment-card details.
6. Retention and your choices
The current application does not define automatic deletion periods for account, server chat or safety records. Retention periods or criteria, including handling of backups and provider-held data, must be established before this draft is finalized. Do not assume that signing out or deleting a local conversation removes server records.
Depending on applicable law, you may have rights to access, correct, delete or receive a copy of your personal information, restrict its use or object to processing. Where processing depends on consent, you may be able to withdraw it. You may also be able to complain to a relevant data protection authority.
A verified operator identity, public privacy contact and a working process for account deletion and privacy requests have not yet been published. The lawful bases for processing and any additional conditions for sensitive information also remain to be confirmed. This draft is incomplete until those details are supplied.