Privacy policy
Last updated: 18 October 2026
This policy explains what personal data Clickback collects, why, who else gets it and what you can do about it. It covers the website at clickback.dev, the Clickback plugin for Claude Code, and the account tools the plugin can sign in to.
Who we are
Clickback is run by sinoperro, S.L., a Spanish company. We decide how your personal data is used, which makes us the controller under the EU General Data Protection Regulation (GDPR).
- Company
- sinoperro, S.L.
- CIF
- B26722488
- Registered
- Inscrita en el Registro Mercantil de Las Palmas el 6 de marzo de 2026, hoja GC-00065975, folio electrónico IRUS 1000468307879
- Address
- 89b Carretera de Chile, A, 3A, Las Palmas de Gran Canaria, 35010, Spain
- [email protected]
- Website
- https://clickback.dev
For anything about your data, email [email protected].
What we collect
Your account
- Your name and email address, and whether and when you verified the address.
- Your password, stored only as a hash, so nobody can read it. If you add passkeys, we keep each one's public key, its name and when it was last used.
- If you turn on two-factor authentication, its secret and recovery codes, stored encrypted.
- Your sign-in sessions: the IP address and browser each one came from, and when it was last active.
Your viewer profile (optional)
If you fill it in: what you mostly work on, your years of experience, the languages and frameworks you use, the size of your company and your country. Every field is optional. We use it only to match you with campaigns that target those things.
Connected computers and account tools
- When you connect a computer, the plugin gets an ad token. The token stays on your computer and we keep only a hash of it, plus which app it's for (Claude Code in a terminal, or the Claude Desktop app), when you connected it and when it was last used.
- While a connection waits for you to press Connect, we keep the code it shows, which app asked, and which account approved it.
- If you sign Claude Code in to the account tools, we keep a record of that sign-in (OAuth tokens and the name the app gave itself) so it works and so you can disconnect it.
What the plugin sends us
The plugin runs inside Claude Code on your computer. It sends us:
- which app you're in, when it connects your computer;
- with each request for an ad: your ad token, which app you're in and the Claude Code session id;
- a confirmation when it has drawn an ad on your screen.
It never sends your prompts, Claude's replies, your transcript, your code or the folder you're working in. Like any request over the internet, these requests also reach us from your IP address. The plugin's source code is public on GitHub, so you can check.
Ads, clicks and reports
- For each ad we serve you: which campaign it was, when we served it, when the plugin confirmed it was shown, the session id, which app, and the IP address the request came from.
- For each click: when it happened, your IP address and your browser's user agent. Clicks go through clickback.dev so we can count them, then straight on to the advertiser's site. We don't add anything to the advertiser's link that identifies you. Once you're on their site, their own privacy policy applies.
- Your earnings and their status.
- Ads you report: which ad, the reason you picked and any details you wrote.
Referrals
- Your referral code.
- If you signed up through someone's referral link, who referred you.
- When you first connected a computer, and when your referral was settled, so a referral is paid once at most.
Payouts
We pay viewers through Stripe Connect. When you set up payouts, Stripe collects your identity and bank details directly, under its own privacy policy. We never see your bank details. We keep your Stripe account id, the country you chose, whether Stripe has enabled transfers and payouts for you (and Stripe's reason if not), when you accepted our payout terms, and a record of each payout.
Advertisers
- Your advertiser name, which is printed in every ad, and your billing email, where we send your invoices.
- Your campaigns: the ads, links, targeting, budgets, bids and dates, their review history, and any note you send when you ask for a human review.
- Top-ups go through Stripe Checkout, which takes your card details. We never see your card number. We keep Stripe's ids for your customer record, payments and invoices, the amounts, Stripe's fees and any refunds.
- Stripe Checkout also asks for your name and billing address and, if you buy as a business, your company name and tax ID or VAT number. Stripe keeps them on your customer record, and we copy them, with your billing email, into our accounting records to issue the invoice for each top-up.
- If you use auto top-up: the saved card's brand and last four digits, your settings, and the exact consent text you agreed to and when.
- Each time you top up or save auto top-up, that you accepted our terms of service, when, and which versions of the terms and this policy were in force.
- Your balance and what you've spent.
Emails with us
If you email us, we keep your email and our reply.
Where it comes from
- You, when you sign up, fill in your profile, create campaigns, report ads or email us.
- The plugin on your computer, as described above.
- Your browser: IP address, user agent and cookies.
- Stripe: the status of your payout account, details of payments, invoices and refunds, and the billing details you enter on Stripe's payment page.
- Other users: if someone invited you, their referral link tells us who.
- TypeSafe, our moderation provider: its verdict on each ad (see below).
- Cloudflare: when you sign up, whether its check thinks you're a person.
Why we use it, and our legal basis
The GDPR says every use of personal data needs a legal basis. Ours are:
- Our contract with you (the Terms of service): to run your account, connect your computers, show you ads, count and pay your earnings and referrals, run and bill advertisers' campaigns, and send you emails about your account.
- Your consent: to target ads using your optional profile. You give it by filling in the profile and can take it back at any time by clearing the fields.
- Our legitimate interests, and advertisers', in paying only for real people seeing real ads: holding earnings, checking IP addresses on ads, clicks and referrals, limiting requests and banning accounts that cheat.
- Our legitimate interest in keeping ads honest and safe: reviewing ads and their landing pages, and handling reports.
- Our legitimate interest in keeping Clickback secure: sign-in sessions, limits on login attempts, the check on the sign-up page that you're a person, and server logs.
- A legal obligation: issuing invoices and keeping accounting and tax records.
- Our legitimate interest in making or defending legal claims.
Where we rely on legitimate interests, you can object (see Your rights). We don't sell your personal data, and we don't use it to show you ads anywhere else.
How ads are chosen
Our server picks each ad from the campaigns running, what your profile says (if you filled it in), how many ads you've already seen, and ads you've reported. We never get your prompts or your code, so they play no part.
Automated decisions
- Ad review. TypeSafe's Jev model reviews every ad and its landing page and decides whether it can run. After viewers report an ad, it also decides whether to suspend it. Suspensions count towards blocking an advertiser account.
- Bans for abuse. An account that sends more than 60 requests for ads within 10 minutes is banned automatically.
- The check at sign-up. Cloudflare's Turnstile decides whether whoever is signing up is a person. If it says no, the account isn't created, and you can try again.
You can ask a person to look at any of these decisions by emailing us. For a rejected ad, there's also a button on the campaign page.
Who we share it with
These providers handle personal data for us, under contracts that limit what they can do with it:
- Laravel Cloud runs the website and the database on Amazon Web Services in Frankfurt, Germany, and keeps our server logs.
- Mailgun, in its EU region, sends our emails, such as email verification, password resets and billing notices. It gets your email address and the email.
- Stripe takes advertisers' payments and sends viewers' payouts. For payout accounts, Stripe also collects identity and bank details as a controller in its own right, under its own privacy policy.
- TypeSafe reviews ads with its Jev model. It gets the ad (advertiser name, headline, text and link) and the landing page's title, description and text. When it assesses reports, it also gets each report's reason and details, but not who made it.
- Anthropic. Our admins decide human reviews of rejected ads by asking an AI assistant (Claude, made by Anthropic) that is connected to our admin tools. For those reviews it reads the ad, the advertiser's name and account email, and the reasons and details of any reports involved, but not who made them.
- Cloudflare runs Turnstile, a check on the sign-up page, and only there, that whoever is signing up is a person and not a bot. It gets your IP address and signals from your browser and device, such as its user agent, and tells us whether you passed. Cloudflare says it uses these signals to detect and block bots and to improve its bot detection, not to identify, profile or target anyone, and that for improving its bot detection it's a controller in its own right. Its Turnstile Privacy Addendum has the details.
Other people see a little too:
- Advertisers see totals for their campaigns: impressions, clicks and spend. They never see who saw or clicked their ads.
- Viewers see the advertiser name printed in each ad.
- If you invited people, you see how many signed up through your link and how many qualified, never who they are.
- Courts, police or authorities, when the law requires us to share something.
International transfers
Our servers and database are in the EU. Some of the providers above, or companies they use, are based outside the European Economic Area, for example in the United States. When your data goes outside the EEA, it's protected the way the GDPR requires: by a European Commission adequacy decision (for the United States, the EU-US Data Privacy Framework, for companies certified under it) or by the Commission's standard contractual clauses. Email us if you'd like more detail.
How long we keep it
- Your account, profile, connected computers, ad history, reports and campaigns: while your account exists. You can clear your profile at any time.
- Sign-in sessions end after 2 hours without activity, unless you ticked "Remember me".
- When you delete your account (Settings, then Delete account), we delete it straight away, along with your profile, passkeys, connected computers, ad history, reports, campaigns and payout settings.
- Financial records of payments, invoices, earnings, payouts and refunds, including the billing details on your invoices, are kept for as long as Spanish accounting and tax law requires, generally six years, even after you delete your account. Some are in our own records and accounting system, and some in our Stripe account.
- Fraud and disputes: if an account is being investigated for fraud, or records are needed for a legal claim, we keep what's needed until that's resolved.
- Server logs are kept by our hosting provider for a limited time and then deleted automatically.
- Emails with us: until your question is resolved, and longer only for one of the reasons above.
Your rights
Under the GDPR you can:
- see the personal data we hold about you and get a copy;
- correct it (you can change most of it yourself, in Settings, Your profile and Advertiser profile);
- have it deleted (you can delete your account yourself in Settings);
- ask us to restrict how we use it;
- get the data you gave us in a machine-readable format, to take elsewhere;
- object to uses based on our legitimate interests;
- withdraw your consent at any time, by clearing your profile or asking us. This doesn't affect what we did before.
To use any of these rights, email [email protected], from your account's email address if you can. We may ask you to confirm who you are. We'll answer within one month. Some rights have limits: for example, we can't delete records the law requires us to keep, and we'll tell you if that applies.
Complaints
If you're unhappy with how we handle your data, please tell us first so we can put it right. You can also complain to the Spanish data protection authority, the Agencia Española de Protección de Datos (AEPD), at www.aepd.es, or to the authority in the EU country where you live or work.
Cookies
Clickback only sets the cookies it needs to do what you ask of it. There are four, all on clickback.dev:
clickback-sessionkeeps you signed in as you move between pages. It expires after 2 hours without activity.XSRF-TOKENprotects forms from being sent by other websites. It lasts as long as the session.remember_web_…is only set if you tick "Remember me" when you log in. It keeps you signed in until you log out, for up to 400 days.referralis only set when you follow someone's referral link, and is only used to credit the person who invited you. It holds their code for 30 days so we can record who invited you when you sign up, and is deleted when you do.
We don't use analytics, advertising or tracking cookies. That's why the cookie notice at the bottom of each page has nothing to accept or refuse. When you press OK on it, your browser remembers that in its own local storage, not in a cookie. If you change the appearance setting, your browser keeps that choice in local storage too.
Our pages load no fonts from other companies, and only one script: Cloudflare's Turnstile check, on the sign-up page only (see Who we share it with). For any cookies it uses, Cloudflare's Turnstile Privacy Addendum points to Cloudflare's own cookie policy. Stripe's pages, where you pay or set up payouts, set their own cookies under Stripe's policy.
Children
Clickback is only for people aged 18 or over, and we don't knowingly collect data about anyone younger. If you think someone under 18 has an account, email us and we'll delete it.
Changes to this policy
When we change this policy, we'll update the date at the top. If a change affects how we use your data in a meaningful way, we'll also email you before it takes effect.
Contact
Questions about this policy or your data: [email protected], or write to sinoperro, S.L., 89b Carretera de Chile, A, 3A, Las Palmas de Gran Canaria, 35010, Spain.