What Spinback collects

Last updated: June 17, 2026

Information we collect

• Account identifiers for sign-in and attribution.
• Per-install device identifiers generated locally.
• Ad interaction events such as impression, qualified view, and click telemetry.
• Temporary IP-derived abuse checks for fraud prevention.

Local-first demo data

This MVP stores advertiser campaigns and user session data only in the browser's localStorage on the machine where the demo is opened.

Information we do not collect

• Source code contents.
• Prompt or response text.
• Project file names, file contents, or project structure.

The extension telemetry contract is intentionally limited to ad-event and install metadata. It contains no field capable of carrying code, prompts, or AI response content.

Third-party services

Stripe, OAuth, analytics, and country-based payout checks are not active in this MVP. When those services are added later, this page should be replaced with an implementation-accurate policy.

The live `kickbacks.ai` site describes a richer production policy. This page keeps only the subset that is true for the local benchmark.