What to put in a support email
The team can only look things up if you name them. Include:- Your studio name.
- The playtest, session, or vault it concerns, as a link or an ID.
- What you expected, and what happened instead.
- The player’s email, if it is about one specific player.
Reporting a security issue
Send security reports to [email protected], not to support. Include a description of the issue, the URL or component it affects, a reproducer where possible, and the impact you observed. Reports are acknowledged within two business days. Userplay does not pursue researchers who act in good faith, avoid harm to customers and testers, and follow coordinated disclosure. There is no bug bounty. The full policy, architecture notes, and subprocessor list are at userplay.io/security.Before you write
Two pages answer most questions faster than an email round trip:- Studio troubleshooting covers a depleted key vault, a blocked publish, a missing transcript, and a refund that came back smaller than expected.
- The FAQ covers what counts against your plan, what players have to install, and why screen capture has no off switch.
Related articles
Player troubleshooting
Identify the exact screen a player is stuck on before you describe it.
Billing
Plans, metering, and who in your studio can change them.
Roles and permissions
Only Owners can act on billing, which is a common reason a teammate cannot find a control.
FAQ
The questions support answers most often.