Privacy policy

Account and sign-in data

Email registration stores your email address, a salted scrypt password hash, account role, and session records. We do not store your password in plain text. A member session expires after seven days; a guest session after four hours.

Google sign-in requests only the openid and email scopes. We verify the Google identity token and use its stable subject identifier to sign you in. We read the verified email claim during authentication and a display name if Google supplies one. For ordinary Google members we store an internal pseudonymous account email rather than the Google email; the initial reserved operator account is the exception. We do not request access to Gmail, Google Drive, or YouTube account data. Google authorization codes and tokens are not retained as account data.

Rooms, uploads, and safety

The service processes room participation, character choices, reactions, playback state, imported GLB characters, and media that members upload. Room state and ordinary personal video uploads are temporary. New-upload expiry and behavior after a server restart depend on the active storage configuration; the upload screen shows the latest verified policy for new uploads. Existing uploads keep their recorded expiry, shown for each file in the personal file library. Temporary storage is cleared on restart. Configured persistent storage can retain eligible uploads until expiry and keep rooms for a limited recovery period, but does not guarantee recovery. Keep your original files. Imported account characters remain with the account.

Reports may contain room and participant identifiers, nicknames, a reason, an optional note, and an operator's review history. Operators use them to investigate abuse and protect participants. Please avoid putting sensitive personal information in uploads or reports.

Cookies and connected services

HttpOnly cookies maintain member or guest sessions, a short OAuth sign-in flow, and short-lived abuse protection. HTTPS session cookies use Secure and SameSite protections. When you choose a YouTube video, its embedded player and public video metadata service may process your request under YouTube's own policies.

The live service runs on an operator-controlled 4080 host and uses external network infrastructure for its public HTTPS domain. The operator stores encrypted recovery copies of core account, report, media, and configuration data in an operator-controlled Google Drive account. This backup account is separate from members' Google sign-in.

Retention and requests

Account, imported character, and moderation records are kept while needed to operate the service or review safety issues. The current pilot has no self-service whole-account deletion endpoint or automatic moderation-record purge. Contact us to request access, correction, or deletion; we will verify your request and explain any information that must be retained for safety or legal reasons.

Encrypted backup files older than 14 days are removed only when at least two newer recovery copies exist. Failed backup runs can therefore extend retention. A deletion from the live service may remain in a recovery copy until that copy is rotated out.

YouTube API Services

MingleStage uses YouTube API Services. When a host adds a YouTube link, we send its video ID to the YouTube Data API to read public metadata such as the title and whether the video may be embedded, and we play it in YouTube's embedded player. We do not access your YouTube or Google account data. Video titles are kept only in temporary room state and a short in-memory cache.

By using YouTube features in MingleStage you agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms). Google's handling of data is described in the Google Privacy Policy (https://policies.google.com/privacy).

California privacy rights

In the last 12 months we collected these categories of personal information: identifiers (email address, account and session identifiers), internet or network activity (sign-in, room participation and abuse-protection records), and content you provide (nicknames, characters, uploads and reports). We collect them from you and from Google sign-in if you choose it, and use them only to provide, secure and support the service as described above.

We do not sell personal information and do not share it for cross-context behavioral advertising. We do not use sensitive personal information to infer characteristics about you. California residents may request to know, delete or correct their personal information by emailing the address below; an authorized agent may submit a request with your written permission. We verify requests against the account email, respond within 45 days, and will not discriminate against you for exercising these rights.

Do Not Track, children and security

We do not track you across third-party websites, so we treat Do Not Track and Global Privacy Control signals as consistent with how the service already works. MingleStage is not directed to children under 13 and we do not knowingly collect their personal information; contact us and we will delete it if we learn otherwise. We use encryption in transit, hashed passwords and access controls, but no system is perfectly secure. The service is operated from and processes data in the United States.

Changes and contact

We will update this page and its date when the service or data practices change. Questions and data requests can be sent to the address below. Operator: Soursea LLC, a California limited liability company. If a translation differs from this English version, the English version controls.

Questions and data requests

[email protected]