Skip to content

Support

Prepare a useful support report without exposing private data

A useful report gives support a reproducible symptom and its context. More private data does not make a report better.

Source checked · 26 September 2026

What to do

  1. Write the screen name, exact error, approximate time and app version.
  2. Describe the last action and whether a change appeared to save.
  3. Add a cropped screenshot with customer details, account values and credentials removed.
  4. Use the official contact route and retain any case reference returned.

What you should see

The report lets support identify the affected workflow and ask for only the necessary next evidence.

If it does not work

Never send passwords, OTPs, PINs, access tokens or complete bank details. Do not post customer order screenshots publicly. A contact click is not proof that a case was received; follow the channel's actual acknowledgement.

For support, include the screen name, time, app version and a redacted error. Never share passwords, OTPs, payment PINs or secret keys.