CLG Recovery brings together case support, digital investigation, blockchain analysis, cybercrime research, compliance, and operations. The goal is to turn a confusing scam incident into an organized case with clear next steps and realistic expectations.
James oversees CLG Recovery’s direction and service standards, with a focus on responsible case handling, clear client communication, and evidence-based recovery work.
Daniel coordinates day-to-day operations, case workflows, internal quality controls, and the handoff between client support and investigation functions.
Robert supports the technical systems used for digital evidence review, secure case handling, transaction analysis, and internal research.
Michael reviews cryptocurrency transactions, wallet activity, exchange touchpoints, and other public blockchain data that may be relevant to a fraud case.
Andrew researches scam infrastructure, websites, domains, impersonation patterns, payment routes, and other indicators that can help place a case in context.
David focuses on phishing, account compromise, remote access fraud, business email compromise, social engineering, and related cyber-enabled scam methods.
Sarah works on mapping digital asset movement across public blockchains and documenting the transaction trail for case review and escalation.
Emily supports privacy, case-handling standards, record management, escalation controls, and the responsible treatment of sensitive client information.
Priya helps organize timelines, transaction records, screenshots, correspondence, identifiers, and other materials into clear case documentation.
Laura helps clients organize immediate post-scam actions, including evidence preservation, account security, institution notifications, and steps intended to reduce further loss.
Mark works directly with clients at the first-contact stage, gathers the initial case summary, explains what information is useful, and helps keep communication clear throughout the review process.
Send a short description of what happened, how payment was made, and when it happened. Never send passwords, private keys, seed phrases, PINs, or one time authentication codes.
