Privacy and AI conversations

2026-10-20

Messages and AI processing

The current public site has no PatientVille account registration or file upload. Chat accepts messages up to 1,000 characters. When you start and send a message, your text, a short conversation history and the fictional character’s information are sent to OpenAI to generate and check a reply. Please do not submit personal, medical, financial or third-party information. The application requests store=false, which does not eliminate provider security or abuse-monitoring retention.

Conversation storage and clearing

The visible transcript and signed continuation token remain in the current tab’s memory, not in localStorage or an account database. The token carries a short recent history and is valid for 30 minutes. Clear chat removes the selected room’s transcript and token. End conversation also stops further sends until you restart. Refreshing clears the tab’s conversation history. These actions do not delete records already held by service providers or cancel processing of a request already sent.

Service protection

A necessary chat cookie lasts up to 24 hours. Usage counters contain random session identifiers, counts and daily keyed network hashes, not conversation text or raw network addresses. Counter expiry is at most two days; expired rows are removed during subsequent successful quota checks. Hosting and AI providers may keep their own security records. Provider locations, transfer safeguards and retention details: processing depends on provider configuration; no regional-residency or zero-retention guarantee is made.

Digital purchases

When available, payment happens on Stripe. Stripe collects payment and billing information; no physical gift is shipped. PatientVille does not receive card numbers or wallet credentials. Its order database records an order reference, a hashed browser identifier, item and character choices, currency, amount, payment status and Stripe checkout reference. It does not copy the billing address or email into that database. Purchase-record retention: records currently persist until removed by the operator; a formal retention schedule still needs to be published. Keep your receipt; clearing the shop cookie or changing browser prevents automatic restoration in the current implementation.

Aggregate statistics

Application statistics count selected public-page, conversation and purchase events by UTC day. They do not use analytics cookies, visitor profiles, conversation text, raw IP addresses or arbitrary query values. Approved campaign codes remain in the current tab and may accompany checkout metadata. Do Not Track and Global Privacy Control disable client recording and exclude marked new checkouts from purchase analytics. Aggregate records older than 365 days are removed on subsequent recording. These counts are separate from purchase records and hosting security logs.