Support

Lexcade help and account support

Include the device type, app version, course, and a short description when reporting a problem. Do not send your password or session token.

Sign-in problems

Check the spelling of the account name and password. Existing passwords may be shorter, while new accounts require at least eight characters. Repeated failed attempts are temporarily rate-limited.

Recover an account

Choose Recover account on the sign-in screen and use one unused recovery code. A successful recovery signs out every old session, replaces the password, and shows a fresh set of ten codes once. Keep the codes private: support will never ask you to send one.

Audio problems

Check device volume and silent-mode settings, then replay the prompt. Include the exact word and selected course when reporting a missing or incorrect pronunciation.

Progress did not sync

Keep the app open briefly after reconnecting. If the score remains incorrect, report the approximate time, game mode, and course.

Player safety

Lexcade has no public chat. You can block a player from Friends to remove any connection and prevent either account from finding the other. Use Report to send a private fixed-category safety report; the other player is not notified. Reports are reviewed by the Lexcade support owner at support@e-cormerce.com. For an immediate safety risk, contact local emergency services rather than waiting for an in-app response.

Delete an account

Open Settings, choose Delete account, and confirm the password. This removes the profile, progress, friend connections, and active sessions.

Download account data

Open Settings and choose Download my data. Lexcade creates a portable JSON file with your profile, onboarding timestamps, recovery-code confirmation timing, learning history and state, preferences, activity, and friendships. Password hashes, session tokens, and recovery-code secrets are never included.

Privacy requests

Send privacy and data questions to support@e-cormerce.com. Include the account name and the request, but never a password, session token, or recovery code. If you cannot sign in, recover the account first so ownership can be verified safely.