// Security
Architecture
How data moves through Userplay — what is captured, what touches it, where it lives, and who can read it.
Last updated May 31, 2026
This page describes how data moves through Userplay. The following properties hold across every data path, no matter which flow is involved:
- Hosting region — all Userplay production data is in the United States. Vercel and Render host the application; Mux stores video; Cloudflare fronts traffic globally for delivery only.
- Transport security — all traffic between clients and Userplay (web app, recorder, telemetry agents, API) runs over TLS 1.2 or higher.
- Storage encryption — all data at rest is encrypted using AES-256 or equivalent at the storage layer across Render, Mux, and Cloudflare where used.
- Authentication — every Userplay API call that touches workspace data is authenticated and authorized against the calling principal’s workspace role.
- Tenant isolation — workspace-scoped queries are enforced in the application layer. Data from one workspace is never returned to a principal who does not belong to it.
- No live capture from telemetry agents — optional telemetry agents operate only after gameplay ends. Nothing is read or transmitted during active play.
For security questions during a review, contact security@userplay.io.