AppsinityAPPSINITY
Store accounts

Account recovery

One recovery path exists: a password reset email. Everything else — a lost email address, a wrong address typed at sign-up, a forgotten username — needs a human.

Open Appsinity Studio

Password reset

Forgot password? on the sign-in page posts to /api/user-auth/password-reset. On success the page reports Password reset email sent. Please check your inbox. If the field is empty it refuses locally with Enter your email first, then tap forgot password.

  1. Enter the address. Exactly the one on the account.
  2. Request the reset. Then wait, checking spam before requesting again.
  3. Set a new password. Minimum six characters, and no complexity rule.
  4. Sign in. The old session token stays valid for its 30 days unless the reset revokes it, so sign out everywhere you still hold a session.
Watch out: A six-character minimum means a recovered password can still be weak. Because the account can publish and delete builds, replace a recovered password with a long unique one immediately.

What self-service cannot do

None of these have a dashboard control. They are all support cases.

SituationSelf-service?
Forgot the password, email still worksYes
Forgot the password, no access to the emailNo
Email address misspelled at sign-upNo
Want to change the addressNo
Want to change the username or avatarNo
Account suspended or bannedNo — Appeals

Opening a support case

Email [email protected] for a player account, [email protected] for a developer account. To be resolvable in one round, the message needs:

  • The address currently on the account, and the address you can prove you own.
  • The display name and, if set, the username.
  • For a developer account: the listing slug(s) you publish, which is the only reliable proof of ownership.
  • What changed when — the last successful sign-in date if you know it.
  • For anything that smells like a compromise: state plainly that you believe the account was accessed by someone else.
Important: Requests to move an account to a new address are identity claims. Expect to be asked to write from both the old and the new address; a request from one of them is unverifiable.

Preventing the recovery case

  • Register with an address you control permanently, not a temporary or work address.
  • Store the password in a manager. The 30-day session means you will not type it often, so you will forget it.
  • For a team: use an alias that survives one person leaving, and add members instead of sharing a login.
  • Note your listing slugs somewhere. They are the proof you will be asked for.

Frequently asked questions

Is there an authenticator app or a recovery code?

No. See Two-factor authentication for what exists and what is only a settings row.

Can support unlock an account locked by failed attempts?

There is no lockout counter described in the account routes, so "locked" usually means "wrong password". Reset it.

What happens to a developer account's apps if it is unrecoverable?

They stay published with no one able to edit them. That is why team seats matter more than a shared password.

Need help?

Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]