CONTACT / OPEN BETA

Get help where the work lives.

Account access starts with Discord. Signed-in release rooms include private report, leave, and block controls so incidents retain the relevant build, message, and case context.

Use the scoped route

Restart Discord from the account page for sign-in failures. Use the controls inside a shared release room for safety incidents. Settings shows your blocks and submitted report history.

BEFORE YOU REPORT

Do not send passwords, access tokens, keys, or executable files.
Keep the mission, room, message, or build identifier attached when possible.
Use room controls for incidents so private evidence stays scoped.
01

Account access

Patchloop uses Discord for account creation and returning sign-in. If the sign-in configuration cannot be loaded, retry from the account page. Your work remains stored on the private workspace, not in the demo.

Join the exchange Sign in

Account recovery

Checking this browser's verified account state

No appeal is submitted while this check runs.

02

Room safety

Open the relevant release room to submit a private report, leave the room, or block the collaborator. Leaving and blocking stop future access without deleting the permanent work record. Review submitted reports and blocked collaborators under Workspace Settings.

03

Legacy application withdrawal

If you submitted a launch application before public account creation opened, its reference and submission email can still be used to withdraw contactable application data. Open the legacy withdrawal form.

This legacy form is only for stored launch applications. Profile correction and safety controls are available in the signed-in workspace.