BitcoinSafe Editorial Policy
This policy explains who is accountable for BitcoinSafe content, how evidence is evaluated, what a review does and does not mean, and how readers can challenge a claim.
Sources and claim verification
BitcoinSafe treats evidence as more important than brand reputation or marketing language. Claims that can change are checked against the most direct current source available before publication or a substantive update.
- Primary sources come first: manufacturer documentation, firmware releases, support notices, public vulnerability disclosures, standards, and original project repositories.
- Independent security research and reputable secondary reporting are used to add context or challenge a first-party claim.
- A source link supports the nearby claim; it is not a blanket endorsement of the source or product.
- Prices, availability, and support status are dated or omitted when they cannot be maintained reliably.
Research, review, and testing boundaries
Most current product profiles are document-based research, not laboratory audits or hands-on product tests. A page states the review scope so readers can distinguish source verification from physical testing.
- Factual review checks claims and citations against the stated sources.
- Editorial review checks clarity, scope, and whether conclusions follow from the evidence.
- Hands-on review is claimed only when the method, reviewer, date, device or software version, and supporting evidence are published.
- BitcoinSafe does not invent a reviewer, score, award, rating count, or security certification.
Updates and freshness
High-risk pages show a last-checked date. That date changes only after the material claims, linked sources, and relevant security notices have been reviewed, not after a cosmetic edit.
- Urgent security guidance is prioritized when a disclosure can change what a reader should do now.
- Product status, firmware guidance, and support windows are rechecked when new first-party information appears.
- Older pages may be retired or redirected when maintaining them would create a misleading impression of freshness.
- Publication and modification dates remain distinct in visible copy and structured data.
Corrections
Readers, researchers, and manufacturers can report a factual error, broken source, or missing advisory through the public issue tracker. Include the page URL, the disputed claim, and a primary source when possible.
- Corrections are evaluated against evidence, regardless of whether the request benefits or harms a manufacturer.
- Accepted material corrections update the page and its last-checked date when the surrounding claims were reverified.
- Do not submit seed phrases, private keys, wallet files, balances, addresses, or exploit details that would put users at immediate risk.
- A correction request does not create emergency support, wallet recovery, legal, or financial-advice services.
Advertising and affiliate independence
BitcoinSafe may earn revenue from display advertising and clearly marked affiliate links. Advertisers, merchants, and wallet manufacturers do not receive approval rights over editorial conclusions.
- Affiliate links are identified in context and use the sponsored link relationship.
- A commission does not establish that a product is secure, supported, or appropriate for a reader.
- Known advisories, discontinued support, and material limitations are not withheld to protect revenue.
- Security-tracker entries and interactive risk tools are kept free of affiliate calls to action.
Material AI assistance
AI tools may assist with research organization, translation drafts, copy editing, code, and automated quality checks. AI output is never treated as a factual source, reviewer, or author.
- A human remains responsible for the published claims, sources, translations, and corrections.
- Material factual claims must be checked against the cited source rather than accepted from a generated answer.
- Automated translation coverage checks detect missing or copied text, but they do not replace human language review.
- Wallet secrets and personal recovery information must never be submitted to an AI tool or to BitcoinSafe.