The editorial standard
No Logs should answer the reader's decision directly and state the limits of the available evidence. Strong wording does not replace a source. A provider's marketing claim is not an independent finding simply because it appears in a public interface or policy.
Content should remain useful without promising anonymity, safety, legality, compliance, or a specific transaction result. Public ledgers, issuer controls, third parties, and user behavior remain relevant even when a route reduces direct wallet linkage.
Three evidence levels
A dated detail visible in a public interface, document, route list, or current site implementation.
A statement made by the external provider about its policy, product, retention, or operating model.
A claim that cannot be confirmed from outside the relevant infrastructure or without stronger evidence.
These labels should stay close to the claim they qualify. A disclaimer at the bottom of a page does not correct an absolute promise made earlier.
Dates and changing facts
Fees, minimums, supported networks, timing windows, and service terms can change. When a page reports one of those details, it should show when the source was checked and direct the reader to verify the current interface before acting.
A review date is not proof that every sentence was re-tested on that date. Where the scope differs, the page should identify the exact observation or source that was refreshed.
Comparisons and recommendations
A comparison should name the criteria that affect the reader's decision and show the evidence behind a conclusion. No Logs should not invent competitors, scores, review counts, audits, or verification status to make a shortlist look broader than it is.
If only one route has enough current public evidence to discuss, the page should say so. A generic category or alternative should not be presented as a tested provider.
Claim boundaries
- No claim of no logs should be described as independently proven without an appropriate independent record.
- Network activity or token supply does not prove the depth of a private service pool.
- A delay can reduce one timing signal; it cannot guarantee that events cannot be correlated.
- Educational content does not decide a reader's legal, tax, compliance, or security position.
Corrections
Send a correction with the affected URL, the sentence or data point in question, and a public source when available. The issue tracker is public. Never post wallet addresses, order IDs, personal data, or private correspondence there.
No response time is promised. Accepted corrections should be reflected in the relevant page and its review date when the change is material.