Crypto Safety Research Built Around Evidence

Why this research matters

Crypto users often have to make decisions with incomplete information. Platform websites usually explain how to deposit or create an account, but they may say much less about account reviews, failed transactions, later-stage verification, complaint handling, or what happens when a user wants to leave.

Marketing claims, licence badges, review scores, and one successful test can all provide useful information. None of them should be treated as complete proof that every user will have the same experience.

Our research tries to make the underlying evidence visible so readers can judge the limits for themselves.

Current research areas

These projects form the research layer behind TrendCrypt safety guides, casino reviews, platform analysis, and scam warnings. Larger public trackers will be released only when there is enough consistent data to make them useful.

How we label evidence

Not all information carries the same weight. A statement written in official terms is different from a marketing claim, and a user complaint is different from a transaction we tested ourselves.

Where possible, our published work should tell readers which of these labels applies to a material claim.

Our research process

1. Define the question We begin with a specific issue, such as withdrawal processing, later-stage KYC, failed self-exclusion, or unsupported network recovery.
2. Collect relevant records Depending on the project, this may include official terms, licence records, transaction data, support messages, archived pages, test results, and public complaints.
3. Separate evidence types We distinguish direct testing, official documents, platform claims, user reports, and editorial interpretation.
4. Look for patterns A single experience may be useful, but recurring behaviour across several cases usually carries more weight.
5. Request clarification where appropriate When a platform is connected to a material concern, we may ask it to explain the policy or respond to the evidence.
6. Publish with limitations Research should explain what the data supports, what it does not prove, and where uncertainty remains.
7. Update the record We revisit findings when policies change, new evidence appears, an issue is resolved, or an earlier conclusion needs correction.

Withdrawal testing

Withdrawal tests can reveal processing steps that are not obvious from a platform’s marketing. Where appropriate, we record the request time, account status, verification requirements, platform fee, blockchain submission, network confirmation, and final amount received.

A withdrawal record may include:

• Platform and test date
• Asset and blockchain network
• Approximate test amount
• Whether a bonus was active
• Whether KYC was requested
• Internal approval time
• Time until a transaction hash appeared
• Blockchain confirmation time
• Platform and network fees
• Final amount received
• Relevant support communication

KYC and verification tracking

We compare the way a platform markets its verification process with the rights it reserves in its terms. A service may not request documents during registration but may still require them before withdrawal or after an account review.

Relevant details include:

• Whether KYC is required at registration
• Whether deposits are accepted before verification
• When later verification may be triggered
• Which documents the platform may request
• Whether proof of address or source of funds is possible
• How long the review took in observed cases
• Whether requests changed during the process
• What happened to funds when verification failed or remained incomplete

A KYC request is not automatically evidence of wrongdoing. The concern is stronger when the process conflicts with published rules, changes without explanation, or is combined with additional payment demands.

Complaint response monitoring

Complaint counts alone can be misleading. Larger platforms naturally attract more public reports, while smaller or newer services may have very little searchable history.

Our analysis looks at:

• The type of complaint
• The amount or account impact where disclosed
• Whether supporting evidence was provided
• Whether the operator responded
• How long the response took
• Whether the explanation cited a specific rule
• Whether the reported issue was resolved
• Whether similar reports appear repeatedly
• Whether the policy involved has since changed

Public complaints remain allegations unless the underlying facts can be independently verified. Our reporting should preserve that distinction.

Responsible gambling audits

A responsible gambling page is not enough by itself. We look at whether account controls can actually be found and used before a player is already in distress.

Relevant checks include:

• Deposit limits
• Loss or spending limits
• Time and session reminders
• Cooling-off periods
• Temporary and permanent self-exclusion
• Account closure
• Marketing and bonus opt-outs
• Access to account and transaction history
• Whether excluded users can reopen or create another account
• How support responds to player-protection requests

A failed or ignored self-exclusion request can carry more weight in a safety assessment than a large game catalogue or generous promotion.

Policy and ownership tracking

Platform rules can change without receiving much public attention. A review written six months earlier may no longer reflect the current withdrawal, VPN, country, bonus, or KYC policy.

We aim to track meaningful changes involving:

• Operating company and ownership
• Licence status and covered domains
• Restricted countries
• VPN and proxy rules
• KYC and source-of-funds clauses
• Withdrawal limits and fees
• Bonus terms and maximum cash-out rules
• Responsible gambling controls
• Complaint procedures
• Supported assets and networks

Where a change materially affects users, existing reviews and safety guides should be updated rather than leaving the old statement in place.

What we do not claim

Research can reduce uncertainty, but it cannot remove all risk. We do not claim that a platform is permanently safe, that every complaint is accurate, or that a successful test predicts every future outcome.

• A licence does not guarantee reimbursement.
• An audit does not guarantee that software remains secure.
• A successful withdrawal does not guarantee all withdrawals.
• A public complaint is not proof without supporting evidence.
• A lack of complaints does not prove that a platform is safe.
• A review score is an editorial assessment, not a guarantee.
• Blockchain visibility does not always reveal who controls an address.

Independence and commercial relationships

TrendCrypt may earn commission from some platforms mentioned on the site. Commercial relationships should not decide which evidence is included, how a complaint is described, or whether a score is raised or lowered.

A partner platform may receive a request to comment on a material issue, but it should not receive control over the conclusion or the removal of supported criticism.

Research involving a commercial partner should follow the same evidence standards used for a platform with no affiliate relationship.

Submit evidence or suggest an investigation

If you have evidence of a withdrawal issue, policy mismatch, repeated verification problem, failed self-exclusion, suspicious wallet request, or another safety concern, contact [email protected].

Useful material may include transaction hashes, relevant terms, platform messages, licence records, policy links, dates, and redacted screenshots. Explain what you observed directly and which parts came from another person.

Submitting information does not guarantee publication, a platform response, fund recovery, or dispute resolution. TrendCrypt may need additional evidence before treating a report as verified.

Corrections and updates

If you believe a TrendCrypt research finding contains a factual error or no longer reflects the current platform policy, email [email protected] with the page address and supporting evidence.

Material corrections should be made clearly. When a finding changes because a platform resolved a case or updated a policy, the page should explain what changed rather than quietly removing the earlier context.