Help

The six things people do here, described the way the software actually behaves. Piracy enforcement is adversarial and no outcome can be guaranteed; what we can promise is that nothing is sent in your name without your sworn approval.

Register a book

  1. Go to Books and add the title and author (both required); the ISBN is optional but improves matching. A trial or Pro account protects one book, Premium protects five.
  2. Tick the ownership attestation. It is required: you confirm you own the copyright or are the authorised agent, and the record is written with the registration. If it cannot be written, the registration is discarded and you are asked to try again — no book can be protected without it.
  3. Optionally add a notification email (or several, comma-separated) to be copied on activity for this book, and the contact details a takedown form may require.

Source: application/services/book.service.ts, backend attestation.record_ownership_attestation.

Run your first scan

  1. Open the book and start a scan. A scan searches the piracy ecosystem, fetches each candidate page, and asks a classifier whether the page actually offers your book. Only classified hits become evidence; pages that could not be fetched are left for the next scan rather than recorded as anything.
  2. A confirmed match needs one more step: the evidence gate renders the page and checks that your title and author are really on it. Only gate-confirmed pages count as confirmed piracy and can be drafted into a notice; everything else stays a lead for you to review.
  3. Scans are metered in SC (scan credit). The trial starts with 500 SC; paid plans reset a monthly allowance. If a scan reaches its time budget before every candidate is verified, it is reported as partial with the unverified count — never as a clean completion.
  4. Books with confirmed piracy are re-scanned automatically on your plan’s cadence by the daily routine.

Source: execution/claude_orchestrator.py (verification phase, evidence gate, coverage), plan_service.ACTION_COSTS, main_api.run_daily_routine auto-rescan.

Attest and send a DMCA notice

  1. Nothing is sent automatically. Verdicts that qualify for a notice wait in your Review Queue; approving one records a sworn statement under penalty of perjury (17 U.S.C. § 512(c)(3)) in your name, with the time, your IP address and browser.
  2. The wording you attest to is exactly the wording that goes out: the app shows the current attestation text and sends its hash back with your approval. If the text has changed since the page loaded, the approval is refused and you are asked to reload — you never swear to text you did not see.
  3. After the attestation is recorded the notice is dispatched from protection@thebookcare.com to the host’s abuse contact, with a forensic packet attached. Every send is logged; a notice that cannot be delivered is reported back to you by email.
  4. Rejecting a queued verdict dismisses it. Nothing is sent, and the evidence stays in your library.

Source: execution/review_queue.approve, execution/attestation.py, EnforcementEngine.dispatch (the single fail-closed gate), legal_event_notify.

Read a reply from a host

  1. Replies to your notices arrive at protection@thebookcare.com and are stored under Replies, marked pending review. No automated action is taken on a reply.
  2. You are emailed when a reply arrives. If it looks like a counter-notice, the email says so: under § 512(g) the host may restore the material in 10–14 business days unless you file a court action and notify them, so the clock matters.
  3. A counter-notice automatically places a dispute hold on the exhibits it concerns (below). Read the reply, decide with counsel, and release or keep the hold from the same page.

Source: main_api postmark_inbound_webhook, execution/legal_event_notify.notify_dmca_reply, execution/dispute_hold.

What a dispute hold means

  1. A hold marks the evidence a disputed notice covers — every exhibit for that book on that host when the reply is linked to one, or the single exhibit otherwise. Held exhibits are excluded from further notices and from automatic escalation until the hold is released.
  2. Holds are placed when a counter-notice is received and can be placed or released by you from the reply’s Dispute hold panel. Releasing a hold does not send anything by itself; the next notice still goes through the review queue and your attestation.
  3. An unlinked reply (one we could not match to a notice) holds nothing; the page tells you so you can link it by hand.

Source: execution/dispute_hold.place_hold / release_hold, GET/POST /api/enforcement/dispute-hold.

Billing, credits and lapses

  1. Trial: 7 days, 500 SC, one book. Pro: $250/month, 25,000 SC, one book. Premium: $500/month, 80,000 SC, five books. Annual plans are twelve months for the price of ten.
  2. Plans are charged as a one-time payment (PayPal or Razorpay, whichever is offered for your region) for a 35-day term — 30 days plus 5 days’ grace. Buying again re-stamps the term. There is no automatic renewal.
  3. Each term resets the plan allowance to the tier amount; allowance unspent at the end of a term does not carry over. Credit you buy separately goes to your wallet and is spent after the allowance; it survives renewals and lapses.
  4. When a term ends without renewal the account returns to trial limits and is marked past due: scheduled re-scans, automatic follow-up notices and chat automation stop; your books, evidence and the record of every notice already sent remain. Purchases are non-refundable except where required by law.

Source: execution/plan_service (PLAN_PRICE_USD, UPGRADE_CONFIGS, expire_lapsed_plans), migration 074 set_plan_allowance, /terms.

Still stuck?

Email support@thebookcare.com for billing, account access, data requests and product questions; we aim to reply within one business day. Correspondence about a specific notice goes to protection@thebookcare.com. Is the platform itself running? See the status page.