Privacy policy

BackSpin may collect account identifiers, Clerk authentication identifiers, campaign ownership data, wait-state timestamps, AI tool or editor type, active session signals, attention-window duration, discovery card delivery records, user ratings, saved discoveries, and aggregate attribution events such as later visits or signups.

Each attention window also carries a coarse diagnostic label of the producer and host, kept as small as possible: the producer build (e.g. the CLI or extension version) and a low-cardinality host bucket such as "Chrome 126 · macOS · desktop". BackSpin never stores the raw browser user-agent, device model, OS version, or locale. The label exists only to correlate a detection regression to a release, and is too coarse to single out a person.

For fraud prevention BackSpin records the install origin as a one-way keyed hash of the IP address (the raw IP is never stored) and an optional opaque client fingerprint. These signals are kept to the smallest set that still lets BackSpin detect account farms, and are not used to track individuals across the web.

BackSpin does not need source code contents to price attention. Product logic should treat code, prompts, secrets, terminal output, and private files as out of scope unless a user explicitly submits them to support.

We use data to operate AI wait-state discovery, calculate quality-adjusted attention seconds, estimate TrustRank, detect fraud, allocate share of voice, show public aggregate market data, report campaign performance, and credit rewards.

Public surfaces show aggregate stats, campaign names, bid weights, categories, market price, and reputation. They do not expose individual user browsing sessions or private developer activity.

When you run `backspin install`, BackSpin writes small, reversible configuration files under your own tool directories (for example a hook file, an MCP server entry, and an auto-discovered plugin for the Cline CLI). These are removed by `backspin restore`. BackSpin does not read your source code, prompts, or terminal output as part of this.

For the Cline CLI only, BackSpin offers an optional feature that shows a small static “BackSpin” label in Cline’s spinner. Enabling it modifies and re-signs the local Cline program file on your machine. This step is OFF BY DEFAULT: a normal install never touches the program file and there is no prompt. It runs only when you explicitly opt in (the `--patch-binary` flag), and even then it is skipped automatically on managed/corporate (MDM) devices, on program files not owned by you, on hardened-runtime or developer-signed binaries, and on Windows. It is fully reversible — `backspin restore` restores the original program file — and it can be disabled everywhere by setting BACKSPIN_NO_BINARY_PATCH=1. Because modifying and re-signing an executable can be flagged by some antivirus or endpoint-security tools, this feature is opt-in and disclosed here so it is never a surprise.

BackSpin uses Clerk for authentication. Clerk account data is used to identify users, advertisers, admins, and payout or campaign ownership boundaries.

BackSpin uses NOWPayments for crypto and PayPal (Orders v2) for card or PayPal-login checkout. Payment providers process payment data under their own policies; BackSpin stores only the records needed for reconciliation, receipts, refunds, and fraud review, never raw card numbers. Transactional email (receipts, account codes, payout and campaign notifications) is sent over the configured SMTP transport.

Attention-window and market records are retained as long as needed for ledger integrity, fraud analysis, tax, accounting, chargeback, and product analytics obligations.

Users can contact BackSpin to request account deletion or data review. Some aggregate ledger records may remain because the exchange needs auditable historical totals.