SpinSponsor app privacy notice
Version 2026-10-19 (version 4). It covers the app, dashboards, Mod and API. The website and waitlist have their own notice.
1. Who we are
SpinSponsor is run by SecAI Ltd, a company registered in England and Wales (number 17387103), registered office Anglo Dal House, 5 Spring Villa Park, Spring Villa Road, Edgware, Middlesex, HA8 7EB. SecAI Ltd is the controller of your data. Contact: [email protected].
2. What the Mod never collects
The SpinSponsor Mod runs inside Claude Code. It never reads or sends your prompts, code, files, or anything Claude says. Ads and keys never enter Claude's context. The only exception is the one-time sign-in code and link that /ads login shows you.
3. What we collect, and why
Your account (everyone). Your email address and sign-in details, handled by our sign-in provider Clerk; whether you are a developer or an advertiser; which version of the terms you accepted, and when; for developers, whether you agreed to what the Mod keeps on your computer (section 5), which version and when; for advertisers, your confirmation that you advertise for a business. You must give an email address to have an account. Why: to run your account. Legal basis: our contract with you.
Developers: machines. A name for each machine you link; a scrambled (hashed) copy of its install key; the Mod version it reports; when it was last seen. While you link a machine, a short-lived sign-in code. Why: to show ads to the right machine and let you revoke it. Basis: contract.
Developers: ads and events. Each ad sent to a machine (whether or not it was shown); for each ad shown or clicked, the machine, the ad, the time, how long it was shown, line or card, and whether it passed our checks. Why: to pay you and charge advertisers correctly. Basis: contract.
Developers: payouts. Stripe collects your identity and bank details to pay you. We don't store your bank details. We keep your Stripe account ID, whether payouts are enabled, the status of your latest bank payout, and our payout records. You only need to give these details if you want to be paid. Basis: contract, and our legal duty to keep accounting records.
Advertisers. Company name, email, top-ups (amount, time, Stripe payment references, and our notes on any dispute or refund; never card details), campaigns, ads and their review history. Basis: contract, and our duty to keep accounting records.
Fraud and abuse checks. When a machine connects, our server briefly sees its full IP address. We store only a keyed hash of the network part of it (the first three blocks of an IPv4 address, or the first three groups of an IPv6 address), once per machine per day, and delete these after 30 days (our daily clean-up runs once a day). The hash is a pseudonymous identifier: without our secret key it can't be turned back into a network. We never store or log full IP addresses ourselves. We use these hashes, and patterns in ad events, to find fake activity, and keep a record of anything flagged. Every event goes through automatic checks, and failures aren't paid. A person reviews any flag before an account is banned. Basis: our legitimate interest in paying only for real views and protecting advertisers and developers.
Rate limits. Short-lived counters per machine, so no one can ask for ads too often; and, for sign-in codes and ad clicks, counters per network address kept only in our server's memory under a scrambled (salted hash) form, for minutes, never stored or logged. Basis: legitimate interest in keeping the service available.
Admin records. A log of admin actions (for example approving an ad, or approving or rejecting a payout), including what changed. Basis: legitimate interest in an accountable, auditable service, and our accounting duties.
Support. If you email us, we keep the conversation to help you. Basis: legitimate interest.
Server logs. When a request is slow or fails, we log its method, path, status and time taken. Errors are logged so we can fix them. We keep keys, click codes and request contents out of logs.
4. Cookies
The app sets only the cookies needed to keep you signed in (set by Clerk). No advertising or analytics cookies. Clicking an ad goes through our redirect, which sets no cookies. The advertiser's own site has its own privacy notice.
5. What the Mod keeps on your computer
Until you have created an account, agreed below and linked the machine, the Mod shows no ads and contacts no server, except when you run /ads login: it then asks our server for a sign-in code and checks every few seconds whether you have approved it on your dashboard.
When you create your developer account, we ask for your consent to the Mod keeping these things in Claude Code's storage on your machine: your install key (if you linked with /ads login), the server address, a few ads ready to show, views waiting to be sent, and its own settings. Basis: your consent. You can withdraw it at any time: run /ads logout or uninstall the Mod, and revoke the machine on your dashboard.
6. Who else handles your data
| Provider | What for | Where |
|---|---|---|
| Clerk, Inc. | sign-in and accounts | United States |
| Stripe | advertiser payments, developer payouts and identity checks | UK, EU and United States |
| Render Services, Inc. | runs the app and API | Frankfurt, Germany |
| Neon | database | London, UK |
| Cloudflare, Inc. | DNS, security and delivery | worldwide network |
| Google (Gmail) | our support inbox | United States |
Transfers outside the UK rely on the UK Extension to the EU-US Data Privacy Framework where the provider is certified, and otherwise on the EU Standard Contractual Clauses with the UK International Data Transfer Addendum. You can ask us for a copy of the safeguards.
Advertisers see only totals (views, clicks, spend), never who saw their ad. We don't sell your data.
7. How long we keep it
- Account, machines and campaigns: while your account is open.
- Network hashes: 30 days.
- Rate-limit counters and sign-in codes: minutes to hours.
- Ad events: 13 months, then only daily totals. A view or click we charged for stays part of the ledger records below: the event keeps only its day, and the ledger entry for its charge keeps the time it was made.
- Ledger, payout and top-up records: 6 years from the end of the financial year they belong to, for accounting and tax.
When you delete your account, we remove straight away your email, your sign-in, your sessions and your install keys, and wipe your machine names and your advertiser company name. Records needed for accounting and fraud prevention stay, linked to an ID that no longer leads to your email: payouts, the ledger, your Stripe account ID, your campaigns and ads, and admin records. These may still contain details you gave us at the time. We also keep a one-way scrambled marker of your sign-in ID, so a deleted account can't sign in again. You can't delete your account while a payout is in progress, or while an advertiser account still has credit or a payment under review.
8. Your rights
You can download your data and delete your account from the dashboard. You can also ask us, by emailing [email protected], to:
- see all the data we hold about you (more than the dashboard download);
- correct it, or receive a copy in a portable format;
- delete it, or limit how we use it;
- object to processing based on our legitimate interests, including fraud checks, or ask for a person to review an automatic decision.
Some decisions are made automatically, for example whether an ad view counts towards your earnings. You can ask a person to review one from your dashboard or advertiser portal (Ask for a review), or by emailing [email protected]. We answer within one month. A review can explain a decision and lift a hold; if a decision was wrong, we may also credit you. We keep review requests and our answers for up to 2 years after we answer, and delete them sooner if you delete your account.
If you're unhappy, you can complain to the Information Commissioner's Office at ico.org.uk.
9. Changes
If we change this notice, we'll update the version and, for important changes, email you first.