Playworlds privacy notice

Direct answer

What information can Playworlds process?

Playworlds can process account information when sign-in is used, basic analytics events, microphone audio when permission is granted, recognized speech or typed input, generated responses, game actions, and saved journey or session state. Operational records may also include ordinary request, error, security, and performance information.

The game should not be used to submit secrets, sensitive personal information, regulated records, or information that a player is not entitled to share. Story input can become part of a transcript or journey context needed to continue the experience.

Direct answer

What happens when I use Google sign-in?

When Google sign-in is configured and a player chooses it, the browser receives a Google credential and sends it to the Playworlds service for verification. The service can use verified account details, such as an account identifier, name, email address, or profile image made available by that flow, to create a signed-in session and associate saved journeys with the account.

Google handles the identity interaction under its own terms and privacy practices. Players who do not complete sign-in may still see parts of the site, but saved-account features can require authentication depending on the active configuration.

Direct answer

How does Playworlds use analytics?

The site uses Google Analytics to measure page views and low-cardinality product events such as selected input mode, connection state, and whether a session action succeeded. The current browser configuration disables Google signals and advertising-personalization signals.

Before analytics parameters are sent, the client filters fields whose names indicate credentials, email addresses, names, messages, session identifiers, text, tokens, or transcripts. Analytics services can still receive standard web information such as an IP-derived location, browser details, page path, and timing according to their own systems and settings.

Direct answer

How are microphone audio and spoken turns processed?

Microphone access begins only after browser permission and an attempt to start a voice-enabled journey. While voice input is active, the browser sends audio frames to the Playworlds voice service. Voice activity detection can identify likely speech, speech recognition can create text, and that text can become input to the game systems that generate the next response.

Audio, recognized text, and generated speech can pass through cloud or AI service providers used by the active deployment. Current public model documentation identifies Google Gemini for selected reasoning tasks, Sherpa-ONNX and SenseVoice for speech recognition, Silero for voice activity detection, and MiniMax for text-to-speech. Configuration can change, so those model pages should be treated as the current product record rather than a permanent provider guarantee.

Direct answer

Where are journey and browser preferences stored?

Saved journeys and their game state are handled by the Playworlds service so an authenticated player can list and resume them. The browser also uses local storage for limited device-side values such as the active session identifier for a world, a display-language preference, and a readout cursor used to continue updates.

Authentication may use an HTTP-only browser cookie. Hosting, content-delivery, API, identity, analytics, and AI-processing providers can process technical data needed to deliver their part of the service. The exact infrastructure can vary by deployment.

Direct answer

What retention statements and controls apply?

Playworlds does not publish a fixed retention period on this page because retention can vary by data type, provider, backup, security need, and active deployment. This notice does not promise automatic deletion on a particular schedule or claim rights beyond those that apply under relevant law.

A player can deny or revoke microphone permission, use text instead of voice, sign out, and clear this site’s cookies or local browser storage. Clearing browser data does not necessarily remove server-side journeys or provider records. A dedicated public data-request channel is not currently published; the contact page records the current contact status.