Write a chronology
List the first contact, promises made, each payment, withdrawal attempts, later demands, reports filed, and responses received.
Tell us what happened, how the payment was made, and what evidence you still have. The first review is designed to identify urgent protections, missing records, and realistic next steps—not to promise an outcome.
Never send: passwords, one-time codes, private keys, or wallet seed phrases.
You do not need a perfect file before contacting the team. Begin with the facts you know and preserve the original records.
List the first contact, promises made, each payment, withdrawal attempts, later demands, reports filed, and responses received.
Include the bank, card, wire, payment app, exchange, wallet address, transaction hash, amount, currency, date, and recipient.
Keep statements, receipts, chat exports, emails with headers, screenshots, support tickets, contracts, advertisements, and platform URLs.
Record case numbers, complaints, recalls, disputes, police reports, exchange tickets, and any written decision already received.
The review moves from intake to evidence assessment before any service recommendation is discussed.
You receive an email reference confirming that the website accepted your request.
The team checks the incident type, timing, payment method, current risk, evidence, and apparent jurisdiction.
You may be asked for specific records or given urgent actions, realistic routes, limitations, and likely dependencies.
Fields marked with an asterisk are required. Give an honest summary and avoid sharing account secrets.
The form intentionally does not accept file uploads. A specialist can explain a safer evidence-transfer method if documents are needed.
2nd Floor, Ste 210, First Security Building, City Creek Center, S Main St, Salt Lake City, Utah 84111
Subscribe our newsletter to get the latest news and updates!
Copyright . All Rights Reserved.
