TERMS · LICENSE & BOUNDARIES

The rules for quoting and using BitShovel, in the open.

This page answers three things: how you may use the content, what happens when we get something wrong, and where the service promise ends. It evolves with the site; material changes are announced on the card feed and the status page.

01
LICENSE · CONTENT & DATA

Editorial copy and public data are CC BY 4.0.

The site's editorial content — card summaries, arguments, weekly and monthly digests — plus the public data endpoints (information-pack.json, managed-objects.json, retired-signals.json, historical-signals.json) and the RSS feed are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0): copy, redistribute, adapt, and use commercially, as long as you credit “BitShovel (bitshovel.site)” with a link back.

Third-party source material is outside this license: every card's “view original” link points to the original source, whose rights remain with the original authors. Follow their terms when quoting them — our CC BY does not extend to their content.

The site code and the desktop app are not covered by this license and are governed separately.

02
DISCLAIMER

Information is provided as-is; attention is not endorsement.

BitShovel content is provided “as is”: the editor and the automated pipeline verify what they can (each card carries verification times and an evidence chain), but completeness, accuracy, and timeliness are not guaranteed. For trading, investment, or technical decisions, return to the original sources and judge independently.

GitHub stars, discussion heat, and chart rankings reflect attention only — never an endorsement of a project's quality, security, or commercial viability; each card's caveat states these boundaries explicitly.

03
CORRECTION & SERVICE

Spot an error? Write in. The status page is the promise of record.

For corrections, dead links, or nominations of things worth tracking, write to carywork08@163.com — every message gets read; confirmed factual errors are fixed and leave a trace on the card's timeline.

There are no accounts and no tracking SDKs; your saves, notes, and personal sources stay on your device. Content and code are fully version-controlled, and every pipeline run is published on the status page — when updates stall, the status page says “degraded” honestly rather than pretending everything is fine.