FAQ & Fraud Ground Rules

Spinback pays developers a share of ad revenue for sponsored lines shown during AI wait states. This page mirrors the trust surface on `kickbacks.ai`, while keeping this repo's local-demo caveats explicit.

How do I earn?

Install the extension, sign in once, and keep coding. When a real wait state is active, the sponsored line becomes a qualified impression only after five seconds of visible time. The product target is a 50% developer revenue share on attributable ad revenue.

Which editors and assistants are supported?

• The VS Code extension flow in this repository.
• The local terminal-style install story represented on the install page.
• Claude Code and Codex are the intended benchmark surfaces.

What counts as a real impression?

• The ad is visible on screen for at least five seconds during an actual AI wait state.
• The session comes from normal human tool use, not automation.
• The install is signed in, connected, and within platform limits.
• The event is not excluded by fraud review or spacing rules.

When do payouts happen?

The intended production flow is monthly payouts through Stripe Connect once a balance crosses a $10 threshold. This MVP stops before that point and labels all balances as demo balances.

Fraud ground rules

• One earning account per person.
• No prompt loops, bots, or scripted impression farming.
• No telemetry replay, spoofing, or event tampering.
• No account networks, payout collusion, or device pooling.
• No circumvention of caps, spacing rules, or review controls.

What do we collect and what do we not collect?

We collect only the telemetry needed to credit earnings, bill advertisers, and limit abuse: install identifiers, event types, timestamps, ad metadata, host versions, and temporary IP-derived abuse signals. We do not collect code contents, prompts, responses, file names, or project structure.