Casino complaint evidence: show what happened without exposing your private information

Evidence should help another person follow the disputed decision. More files are not automatically better. A withdrawal confirmation, the relevant support reply and a clear timeline can answer more than twenty cropped screenshots with no dates. Before uploading anything, identify the question each record answers and whether it belongs in a public discussion or a private verification channel.

Start with the questions your case needs to answer

For a delayed withdrawal, the questions might be when it was requested, whether it was approved and whether payment reached you. For a bonus deduction, they might concern the accepted terms and the transaction said to breach them. For an account closure, they may concern the notice and the decision about the remaining balance. Use those questions as headings in your own notes.

Under each heading, list what you have and what is missing. Be honest about gaps. An email saying a payment was initiated does not replace a receipt, and a screenshot of a balance does not show how every part of that balance was earned. Naming the missing record lets the casino or case manager request it directly.

Keep originals and public copies separate

Retain original emails, downloaded statements and screenshots in a private folder. Create a second folder for public copies. Give each copy a descriptive filename such as “withdrawal-request-2026-10-03” without your email, full account number or document number. Record which original it came from so you can supply an intact version through an appropriate private channel if needed.

Do not edit an amount, date or message to make the case look clearer. If you add a visual label, make it obvious that the label is your annotation. Preserve enough of the surrounding conversation to show what the reply refers to. A tightly cropped sentence can reverse the apparent meaning of a support exchange even if the sentence itself is authentic.

Remove private information from the public copy

Check names, email addresses, postal addresses, phone numbers, bank and card details, identity numbers and unrelated transactions. Consider other people's details as well as your own. A chat screenshot can include an agent's personal contact information or another customer's data accidentally displayed by the sender. Public readers generally need the role and relevant reply, not private identifiers.

Redaction must remove information, not merely cover its appearance. The ICO's guidance explains the risks of hidden personal information in documents and the need to check files before disclosure. A coloured rectangle in a PDF may leave selectable text underneath. After exporting the public copy, reopen it, try selecting or searching the removed text, and inspect document properties. If you cannot establish that a file is safely redacted, do not publish it.

Check the whole file, not only its first page or preview. A PDF can include additional pages, attachments or comments. An image may show browser tabs, account menus or notification banners. Review at a readable size and ask whether a stranger could use the remaining details to identify your private account.

Write a timeline that makes the attachments understandable

Use dates and short descriptions of actions: request submitted, document accepted, deadline given, deadline passed, final response received. Include the time zone when the precise timing matters. Distinguish what you did from what support said and what you inferred. “Support said payment was sent” is more accurate than “the bank lost my money” if no trace has confirmed that conclusion.

Connect each important event to one public attachment or a private record you can provide. You do not need to upload every conversation. Summarise routine follow-ups and preserve the full exchange privately. Explain any correction openly: if the original claimed amount included a payment already received, update the remaining amount rather than removing that part of the story.

Describe the strength and limits of each record

A payment screenshot may establish a displayed status. A bank credit may establish receipt. A representative's reply may explain a decision without independently proving it. Say what the record shows and avoid claiming more. Where a casino disputes the authenticity or interpretation of an attachment, retain the original and ask what part is challenged.

Keep currencies separate. If your claim is in euros and an eventual payment arrives in another currency, record both and the conversion explanation. Do not add unrelated balances or treat a proposed settlement as recovered money. Outcomes are easier to assess when “offered,” “sent” and “received” remain distinct words.

Submit a focused account of your own dispute

Open with the problem, the disputed amount if known and the remedy requested. Then provide the timeline and the few records needed to understand it. The MGA's complaint form asks for clear, truthful information and warns against fabricated details and abusive threats. Whatever route you use, a precise account of your own experience gives the recipient something concrete to investigate.

Review the public text one last time before posting. Remove passwords, payment credentials and identity documents even if they seem to support the story. Check how the complaints process works and use the escalation guide when you need an external route. Keep a copy of the final submission so later replies can be read against the same starting point.