Made with
floot.com
JEZ AIGetInstantResolveYOUR NEXT STEP · CLEARLY ORGANISED
Build my resolution plan
GET INSTANT COMPLETELaw + Proof + Resolve · A$124.85 separatelyA$99.95 one timeSee the complete journey →

GetInstantResolve guide

What information should you avoid sending?

Share only information relevant to the issue. Remove unnecessary identifiers, passwords, full card or bank details, unrelated health information and third-party personal data. Keep an untouched original and create a redacted sharing copy where appropriate.

General information only — not legal advice · Reviewed 2 October 2026

General resolution guideChoose country and region before relying on jurisdiction-specific legal steps, deadlines or escalation routes.
Choose location
VISUAL DECISION PATH

Use the lightest suitable route first — then review.

Not every dispute should jump straight to formal escalation. The route changes with the response, urgency and jurisdiction.

1 · DIRECTNever send credentials
2 · REVIEWMinimise financial identifiers
3 · FORMALProtect third parties
Direct requestComplaint / reviewFormal route only if needed
01

Never send credentials

Passwords, one-time codes, recovery keys and security answers should never be included in a dispute letter or upload unless a verified secure system specifically requires something different.

02

Minimise financial identifiers

Use only the transaction or account reference needed to identify the issue; avoid full card and bank details in ordinary communications.

03

Protect third parties

Remove unrelated names, addresses, children's information, employee data or customer data where it is not needed.

04

Use redacted sharing copies

Keep the original secure and create a clearly labelled redacted copy for sharing when appropriate.

Important limitation

Privacy and disclosure duties vary. This page gives general information-minimisation guidance, not legal disclosure advice.

Continue the journey

Use the right tool for the next job

Common questions

FAQs