Skip to main content

Account integration

Funox player accounts are optional. Use them when your game benefits from cross-device progression, leaderboards, friends, or social features.

When to integrate accounts​

Integrate accounts if your game has any of:

  • Progress that should follow the player across devices
  • Leaderboards or competitive scoring
  • Friends, parties, or co-op
  • Cosmetics, inventory, or purchases tied to a player identity

Skip account integration if your game is a quick single-session experience with no persistent state.

Guest vs. signed-in​

  • Guests can still save up to 1 MB of data via the data SDK. Data is kept in localStorage.
  • When a guest signs in, their guest data is automatically migrated to their account.
  • Don't gate any single-session gameplay behind a sign-in prompt.

Sign-in UX rules​

  • Offer sign-in on screens where it makes sense (main menu, leaderboard, profile).
  • Never block gameplay or rewards behind a sign-in.
  • Show the player's avatar and username when signed in — confirm the connection visually.
  • Provide a clear sign-out option in the settings.

Server-side verification​

If your game has a backend (multiplayer, anti-cheat, etc.), always verify the Funox user token server-side. Never trust the client.

See the User SDK for the token verification flow.

  • Use only the user data the SDK provides (username, profilePictureUrl).
  • Do not request a user's email, real name, or other PII through your own form.
  • If you store user-generated content, make it possible for the user to delete their data on request.

Linking your own accounts​

If your game already has its own account system (e.g., a Photon login, an external publisher account), use showAccountLinkPrompt() to request the player's permission before connecting the two identities.

On this page