BTCintel
nodeok
mempool68,781 tx
node next1.08 sat/vB
retarget40 blocks
chainmainnet

Docs

Takedown and correction

How to ask btcintel to remove community content, to correct or retract a Curated claim, or to stop showing something about you, and what happens next. btcintel is operated by Satsboard LLC, 1021 E Lincolnway 10076, Cheyenne, WY 82001, United States.

in forceEffective 2026-09-24. Adopted by the operator on 2026-09-24 (decision P54 in the btcintel codex); the account terms were added on 2026-09-29 (S5.5), approved by the operator on 2026-09-30 (P61) and apply once accounts open (features.accounts); a lawyer's review is on the launch checklist. Changes are published here with their date.

How to ask

  • E-mail [email protected] (the channel for legal notices, including notices under copyright law).
  • The feedback channel: the feedback button on the page in question, or POST /v1/feedback on the API, with the text starting takedown:. Include a Nostr pubkey or an API key as contact if you want an answer through them.
  • A Nostr contact will be listed here when the ops team publishes a key; a public issue template follows when the tracker opens.

What we need

  • What: the event id (note1… or 64 hex) or the pubkey for community content; the claim id (ann_…, att_…) for a Curated claim; the page URL always helps.
  • Why: the legal basis or the factual error — your own personal data published without a basis, a court order, an infringement, a defamatory statement, a claim whose source has been corrected — and the jurisdiction you rely on.
  • Who: a way to reach you for the answer and for one round of appeal. We do not need your identity documents for content you signed yourself: a NIP-09 deletion from your own key removes your own note without asking us.

Timelines

We acknowledge within 72 hours and decide within 14 days. Orders from a competent court or authority are acted on as they require.

Outcomes

  • Hide the community event from the site, the API and our relay, recorded with the reason legal:<reference>; the event stays in our store, invisible, for 90 days, then it is purged. Other relays keep their copies; we say so.
  • Ban the pubkey at our relay when the content or the behaviour warrants it.
  • Retract or expire a Curated claim: the claim keeps its history and citation, marked retracted with the reason; a source correction is applied at the next import.
  • Refuse, with our reasons in writing.

Appeal

One round, decided by a human operator who did not make the first decision, within 14 days of your appeal.

Record

Every action leaves an entry in our audit log (actor, action, reason, date) and a line in the public incidents log without personal data. We publish the count of takedowns received and acted on with each status update.

Copyright notices

Notices under the US Digital Millennium Copyright Act may be sent to [email protected] with the elements the Act requires (identification of the work, of the material and its location, your contact details, the good-faith and accuracy statements, your signature). Registration of a designated agent with the US Copyright Office is on the launch checklist.