The short answer
No registration does not prove no logging. No logging does not prove no public transaction history.
What does “no logs” actually cover?
“No logs” is a claim about the records an operator retains. It does not describe the public blockchain or establish anonymity.
For example, an operator could delete an order reference while its hosting provider retains access records. That is a hypothetical difference in scope, not a finding about a named service.
Ask which application, hosting, CDN, support, analytics, backup and processor systems were inspected, by whom and when. A written policy is not evidence of the deployed configuration.
| Layer | Question | Do not infer |
|---|---|---|
| Application | Which order and transaction fields are stored? | That deletion of one record deletes every copy. |
| Infrastructure | What access, security and backup logs exist? | That a privacy policy describes actual configuration. |
| Support and analytics | What contact and event data is retained? | That no account means no related records. |
| Public chain | What transfers remain visible? | That an operator can erase historical transactions. |
Ask which records exist
| Record | Question to ask |
|---|---|
| Application activity | Are requests or transaction references stored? For how long? |
| Infrastructure | Do the host, CDN or security services keep access logs? |
| Support | Are emails, attachments and conversation histories retained? |
| Analytics | Which scripts and processors receive usage data? |
| Public ledger | Which transactions remain visible independently of the website? |
An audit only proves what it examined
Look for a named reviewer, an inspection date, the systems included and the report's limitations. A smart-contract audit is not automatically an infrastructure-log audit. A review of a policy document is not an inspection of deployed systems.
An old report can be relevant history, but it is not proof that the present deployment has the same configuration. Compare the report's scope with the specific promise being made.
What to do with missing evidence
Classify an unsupported claim as unverified. Do not turn the absence of a public breach report into positive evidence that no records exist.
StableMatrix uses no-logs language only to discuss claims and evidence. It does not certify a third party's internal data practices.
No KYC, no registration and no wallet connection are different
| Claim | It does not establish |
|---|---|
| No registration | That the service cannot request identity information later or associate an order with a transaction. |
| No KYC | That requests, IP addresses, analytics or support records are absent; that screening or issuer controls do not apply. |
| No wallet connection | That the site receives no browser data or that the receiving service has no records. |
| No transaction logs | That infrastructure, support, backups and third-party processors keep no related information. |
Does “no logs” change for USDT, USDC, TRC20 or BEP20?
The token standard does not determine a website's retention policy. A no-logs USDT or USDC claim must identify the operator, the systems and the records covered. TRC20, ERC20 and BEP20 labels cannot supply that evidence.
To assess a zero-logs claim, compare the policy with a dated inspection of the relevant deployed systems, including infrastructure and processors. Record exclusions and configuration changes since the inspection. Without that evidence the answer to “does this mixer keep logs?” is unknown, not no.
The reviewed blockchain record remains a separate source of information. Deleting an operator's records cannot delete historical public transactions. StableMatrix has not inspected a mixer's backend and does not certify any provider as no-logs.
A no-logs review needs a dated scope
- Name the systems inspected: application, host, CDN, security layer, support and analytics.
- Record the inspection date, retention settings, exclusions and processors.
- Separate policy text from observed deployment configuration.
- Keep public blockchain visibility outside the operator's deletion promise.
Source notes
Each reference has its own last-check date. That is not its publication date. Follow the live document for current terms and identifiers.
- Ethereum.orgBlock explorersPublic transaction, block and address data, rather than proof of a person's identity. Document date not recorded. Checked: 2026-09-20.
- CircleUSDC contract addressesIssuer-listed mainnet identifiers. A token listing is not a service endorsement. Document date not recorded. Checked: 2026-09-21.
- TetherSupported protocols and integration guidelinesExact issuer-listed asset/network combinations, including discontinued protocols. Document date not recorded. Checked: 2026-09-21.
- CircleUSDC TermsRedemption conditions, blocked addresses, third-party platform boundaries and transfer risks. Document date not recorded. Checked: 2026-09-20.
- U.S. Treasury / OFACFAQ 560: digital currency obligationsSanctions obligations for U.S. persons and others subject to OFAC jurisdiction. Document date: 2018-03-19. Checked: 2026-09-20.