Data Processed

This document describes the categories of data Userplay processes, the source of each category, the purpose it serves, and how long it is retained. It is the canonical reference for Subprocessors, the Privacy Policy, and the Data Processing Addendum.

All data is processed in the United States.

Account and Workspace Data#

• Source — studio members at sign-up and through workspace configuration.
• Includes — name, work email, hashed password (when password auth is used), workspace name, billing details, role assignments, workspace settings, and integrations.
• Purpose — provide authenticated access, bill customers, enforce role-based access, surface workspace-scoped configuration.
• Retention — maintained for the lifetime of the workspace; deleted within 30 days of confirmed account closure, except where retention is required by law (for example, financial records).

Playtest Configuration#

• Source — studio members when designing a playtest.
• Includes — playtest title, description, objectives, prompts shown to testers, capture toggles (screen, microphone, webcam), AI processing toggle, tester invite list, expiry date.
• Purpose — define what testers see, what is captured, and how outputs are processed.
• Retention — persists for the lifetime of the playtest. Deleted when the parent workspace or playtest is deleted.

Session Recordings (Screen and Audio)#

• Source — tester clients during a playtest session. Recordings are captured locally and uploaded to Mux.
• Includes — screen video, microphone audio (when the tester consents), webcam video (when the tester consents and the playtest is configured to capture it), basic device metadata (OS, browser, resolution).
• Purpose — allow studios to review what testers did during a session.
• Retention — default 12 months from session completion. Workspace owners can configure shorter retention. Soft-deleted recordings are purged from Mux storage within 30 days.

Audio Transcripts#

• Source — derived from session audio by OpenAI transcription, when AI processing is enabled.
• Includes — time-aligned transcript text, language detection.
• Purpose — make sessions searchable and feed downstream analysis.
• Retention — tied to the parent recording; deleted with the recording.

AI Analysis Output#

• Source — derived from session video and transcripts by Google Gemini, when AI processing is enabled.
• Includes — structured insights: themes, friction points, sentiment markers, notable moments, generated session summary.
• Purpose — help studios surface patterns across large volumes of playtest data without watching every recording.
• Retention — tied to the parent recording; regenerated if the studio re-runs analysis.

Chrome Extension Telemetry#

• Source — the Userplay Chrome extension, when both the studio and the tester opt in. Captures occur after gameplay ends and run locally in the tester’s browser. Credential and token patterns are excluded before submission.
• Includes — in-game events the game itself emits (conversations, model calls, MCP events for web-based games), page-level metadata for playtest pages only.
• Purpose — give studios additional context beyond screen and audio for web-based and AI-driven games.
• Retention — stored alongside the parent recording; follows the same retention schedule.

Support Communications#

• Source — customers and testers when contacting support.
• Includes — email content, support ticket metadata, attached files when included.
• Purpose — provide customer support, troubleshoot issues, improve documentation.
• Retention — retained while the support relationship is active, then deleted within 24 months of last contact.

Web Analytics and Product Telemetry#

• Source — the Userplay web application and marketing site, via Vercel and Cloudflare logs and a privacy-respecting in-product analytics layer.
• Includes — pseudonymous page views, feature usage events, performance metrics, error reports.
• Purpose — operate the service, understand product usage in aggregate, fix bugs.
• Retention — aggregated metrics retained indefinitely; raw event records retained for 90 days.

Out of Scope#

Userplay does not collect, process, or sell:

• Tester credentials, authentication tokens, cookies, or session secrets from games being tested.
• Live in-game telemetry during active gameplay — the Chrome extension activates only post-gameplay.
• Children’s data — Userplay is not intended for users under the age of majority in their jurisdiction. See Use Restrictions.
• Personal data unrelated to operating the service.