support preparation
Share the symptom, not control of the account
A support request should include enough context to reproduce the problem while excluding passwords, OTPs, recovery codes and payment credentials.
practical review
What to check on this route
On this support checklist page, treat useful context, redaction and channel validation as separate evidence checks. Compare their results before deciding what the next action should be.
Useful context
Date, time zone, device, route and exact message.
Redaction
Remove names, balances, tokens, QR codes and full identifiers.
Channel validation
Confirm the support route independently before submitting anything.
five-step method
A reversible checklist
For support checklist, begin with this first check: Write a one-sentence symptom. Keep the sequence intact through the final check: Record the support reference for follow-up. Record what changed before moving on.
- Write a one-sentence symptom.
- Add the last successful and first failed step.
- Attach only redacted evidence.
- Keep credentials and codes private.
- Record the support reference for follow-up.
quick answers
Common questions
Does support need my password?
No legitimate diagnostic explanation requires you to send your password.
What if the channel cannot be verified?
Do not submit sensitive information; find a route you can independently confirm.
18+ and responsible use
This troubleshooting guide is for adults aged 18 and over. Protect personal data during support contact, keep time and spending boundaries visible and stop when a helper asks for account control.