Skip to main content

/ TRUST

Seven commitments we publish so you can hold us to them.

If we break any of these, call us out in Discord or open an issue on GitHub. Silence is not an option.

/ live anti-cheat artifact
Real Discord screenshot: NuroBot CLV captured event in #dev-updates: NBA Philadelphia 76ers @ New York Knicks, sharp:NBA surface, posted -290 to closed -290 to CLV +0.00%, pick id 438, closing hash ff17da407e188564...

Every sharp-tier pick gets its closing line captured by an in-process tick 2 minutes after kickoff. The bot posts the posted-vs-closed delta + cryptographic closing-hash to #dev-updates in real time. Hash recomputable from the public /api/record/[id] response; backdating breaks the hash.

Public CLV records

Every capper and every model on NuroPicks publishes their closing line value against sharp reference books. We do not use a house book as the reference. Sample size is published. Cappers with under 25 tracked picks do not appear on the leaderboard. The closing line is captured by an in-process service 2 minutes after each game's kickoff and written to an append-only row on the picks table. See migration 0020 and src/bot/services/closing-line-capture.js for the exact implementation.

See the live ledger \u2192

50/50 affiliate rev-share with cappers

Every sportsbook affiliate dollar tied to a capper-sourced signup is split 50/50 with the capper. Not tiered, not throttled, not time-limited. The industry standard is 10 to 20 percent. We believe the cappers are the business.

Read the rev-share post \u2192

No cherry-picking

You cannot delete a pick. You cannot edit a losing pick to look like a winner. You cannot backfill. These rules are enforced by a Postgres trigger (picks_immutable_guard) that rejects any UPDATE or DELETE of a locked row. Only grading fields (result, graded_at, closing_odds) may mutate after post time. The weekly_snapshots table is enforced identically: stat corrections land in the next week's row, never the frozen one. See /api/record/1 for a JSON receipt per pick.

Subscribe to the RSS feed (audit us) \u2192

Plain-English capper agreement

The agreement you sign when you apply to cap is written in plain English and published publicly. The legally binding version comes later from counsel and will track this document's commitments.

Read the agreement \u2192

Responsible gambling posture

Every user surface includes self-exclude and report escape hatches. 1-800-GAMBLER appears on every embed that references wagering. Cappers who encourage bet-chasing behavior have their revenue share frozen pending review.

RG resources \u2192

Tools, not a book

We do not accept wagers, hold balances, or pay out winnings. We are analytics and community. Your real-money account lives at a licensed sportsbook; we route you there via affiliate links marked as such per FTC rules.

No surprise billing

You cancel in one click from your account billing page, effective at the end of the paid period, with no retention maze and no email-support gate. We never auto-upgrade a monthly plan to an annual one, and we do not silently re-bill a card that lapsed. Duplicate charges and obvious payment errors are refunded within 7 days. The full policy is public, plain-English, and versioned so you can diff any change.

Read the cancel and refund policy \u2192

How to hold us accountable

Public issue tracker
github.com/davidolverson/nuropicks. File an issue if you see us breaking our own rules.
#dev-chat
Dev updates post in real time. Anyone can call out drift.
Capper dashboard transparency
Cappers see per-book rev-share rates and an audit log of any adjustment.

What we will not promise

Three things we will never say, because anyone who says them is selling you something:

  • "Guaranteed winners." Variance is real. A +3 percent edge model can go 18-32 over 50 bets.
  • "Cracked the code." Sharp markets are cracked by thousands of quants with more capital than us.
  • "Insider information." If it is insider information it is illegal to act on. Full stop.
Questions: hello@nuropicks.com · Tools · Blog