Overview
spinshare.dev (“we”, “us”, “our”) operates the SpinShare VS Code extension, the spinshare CLI wrapper, and the spinshare.dev website. SpinShare is a developer-first ad exchange that displays short text advertisements in place of the loading spinners and progress indicators that appear while AI coding agents are generating output. This policy describes what information we collect, how we use it, and the choices you have.
Information We Collect
- Account information. When you sign in with Google or GitHub, we receive your email address, display name (where available), and a stable provider-side identifier (such as the OAuth
subclaim) so we can identify your account, credit earnings, and prevent duplicate accounts. - Device identifier. A per-installation client identifier is generated locally to associate impression events with your account. It is pseudonymous: it does not identify you on its own, but for signed-in users it is linked to your account so we can credit earnings.
- Ad interaction events.For each ad served we record event telemetry: the event type (impression rendered, viewable, view-duration ticks, clicks), the ad/campaign/creative identifiers, the surface it appeared on (spinner, status line, progress notification, or overlay), on-screen visibility metrics, a per-event ID used to deduplicate events, timestamps, and the client and host application versions (for example, the SpinShare extension version and the VS Code or Claude Code version). In signed-out preview (“demo”) mode, this telemetry is not attributed to any user account.
- IP address. We process your IP address on a transient basis for rate-limiting, abuse-detection, and fraud-prevention purposes.
- Payment information. If you purchase ad inventory, payment is processed by Stripe. We do not store your full card details.
Information We Do Not Collect
- Your source code, file contents, file names, or project structure.
- Your prompts, AI responses, chat history, or tool invocations.
- Your browsing activity outside of our extension, CLI wrapper, and website.
- The extension’s and CLI wrapper’s telemetry is structurally limited to the ad-event metrics described above — the data they transmit contains no field capable of carrying your code, prompts, or AI interactions.
Local Processing (Never Transmitted)
To detect when an AI coding agent is actively running and which session is on screen, the SpinShare extension reads Claude Code’s local session transcript files (~/.claude/projects/**/*.jsonl) on your machine. From those files it parses only a small set of signals — for example, the session’s entrypoint tag (which distinguishes a VS Code panel session from a terminal session), the name of the most recent tool invocation, and whether the current turn has finished. This is used solely to time ad display and to stop the billing clock when activity ends.
This processing happens entirely on your device. No transcript content — no prompt, response, code, or tool name — is ever transmitted to our servers, and our telemetry schema contains no field capable of carrying it. The extension’s source is open source and publicly mirrored so you can verify this yourself.
Website Analytics & Cookies
The spinshare.dev website (not the extension or CLI wrapper) may use a usage-analytics service that records how visitors interact with our pages (clicks, scrolling, and page navigation) and sets cookies to distinguish visitors. We use this to understand and improve the website. See the third-party provider’s privacy statement for details. Our pages may also load fonts from a third-party font service, which receives your IP address when the font files are fetched.
How We Use Information
- Credit earnings to your account based on ad impressions and clicks.
- Serve relevant ads in the extension spinner slot.
- Improve our service and detect fraud or abuse.
- Communicate important account or service updates.
Google & GitHub User Data
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Our use of information received from GitHub adheres to the GitHub Developer Terms and the GitHub Privacy Statement. Specifically, we:
- Only use your provider email, display name, and stable identifier to identify your account and credit earnings.
- Do not use provider user data for advertising, retargeting, or profiling.
- Do not sell, rent, or share provider user data with data brokers.
- Do not use provider user data to train AI or machine learning models.
Data Sharing
We do not sell your personal information. We may share data with:
- Stripe. For payment processing and, when payouts open, payout processing and related tax-information collection.
- Google Cloud / Firebase. For infrastructure hosting, authentication, and data storage.
- Twilio SendGrid (or a comparable transactional email provider). For transactional email (sign-in links and account notices).
- Analytics provider. For website usage analytics, as described above.
- Advertisers. Only aggregate, anonymized impression and click counts.
Data Retention & Deletion
Account data is retained while your account is active, and may be retained for up to 7 years after termination or last activity where needed for fraud prevention, financial reconciliation, and legal compliance. You may request deletion by contacting us at support@spinshare.dev; upon deletion, personal identifiers are removed or anonymized within 30 days, while aggregated or anonymized data and financial records required by law may be retained.
Your Privacy Rights
Depending on where you live (including California, Virginia, Colorado, Connecticut, Utah, and other U.S. states with privacy laws, as well as the EU/UK under the GDPR and Canada under PIPEDA), you may have the right to request access to, correction of, or deletion of your personal information, and to opt out of any sale or sharing of personal information (which we do not do). To exercise any of these rights, email support@spinshare.dev.
Security
We use industry-standard measures including encrypted connections (TLS), secure authentication tokens, and access controls to protect your data. No method of transmission or electronic storage is completely secure, however, and we cannot and do not guarantee absolute security.
Changes
We may update this policy from time to time. Material changes will be communicated via the extension or email.
Contact
Questions about this policy? Email support@spinshare.dev.