Where this applies

General account-security procedure; use the India support route linked by the official FAQ.

What to do

  1. Record player ID, exact app name, version, device model, OS, time and error text. Describe what you expected and what actually happened, including steps to reproduce it.

  2. For a purchase issue, keep the original store receipt and order identifier privately. Never publish payment details in a forum or this site's search field.

  3. Open support from the official app, store listing or Garena FAQ. Check the destination before sending account evidence, and never include passwords, OTPs or recovery codes.

  4. If your linked login may be compromised, secure that provider first through its official settings. Review sessions and recovery details, then report unexplained account changes to game support.

Worked checks & examples

Turn a vague complaint into a reproducible report

Instead of 'my account is broken', write a short sequence such as: opened the official India app; chose the displayed login provider; reached a new profile instead of the expected one; stopped before purchasing. Include the time zone, app version and device model. Identify what still works, such as access to the linked provider, without sending its password. This example is a reporting template, not evidence that India normally creates new profiles or that a particular migration rule exists.

Choose the recipient and reduce private data

A store installation message and an in-game account issue may need different support teams. Start from the official store or India FAQ, explain the stage and include only the evidence relevant to that team. Keep receipts and account identifiers out of public comments. Crop unrelated notifications and redact phone numbers or codes before attaching a screenshot. If an error contains a token, do not paste the entire URL into a forum. Keep an untouched private copy if official support later needs a specific field through its authenticated process.

Stop troubleshooting when preservation matters more

If the proposed next step would unlink a login, delete guest data, overwrite a profile or require recovery secrets, pause until you understand the consequence. Record the current state instead of trying several identities in quick succession. Save the ticket reference, submission date and information already sent so a follow-up adds a new fact rather than contradicting the first report. Never pay a third party for a faster reply or assume that reinstalling will restore missing items. Support outcomes and response times are outside this guide's control.

Choose your next step

Use one clear ticket and keep its reference. Add new evidence to the same case when possible instead of paying a third party to 'speed it up'.

What this does not confirm

This independent guide cannot inspect accounts, issue refunds, remove bans or guarantee response times. There is no contact form collecting player data here.

Sources & evidence