Privacy

The same three lists the plugin shows you before it sends anything, plus what happens to them afterwards. Last updated 9 October 2026.

Who runs this

Tickover is a trading name of an independent sole proprietor based in Vietnam. There is no company behind it yet. Questions, corrections and requests all go to the same place: hello@tickover.dev, answered by a person.

What the plugin sends

Your GitHub id, operating system, Claude Code version, when each turn starts and stops, the Claude Code session id and when that session started, counts of file extensions in your project directory, which questions you skip, and your answers with how long you took and where you answered them (terminal pane, local page, VS Code, or inside Claude Code).

Derived on our side, not sent by the plugin: your country, from the IP address of the request, and an activity tier from how many turns you run a week (light under 5, regular 5 to 20, heavy over 20). Buyers can target on both.

Never: prompts, file contents, file paths, repository names, repository owners, or transcripts. Your status line JSON names the repository you are in; the plugin does not forward it. Your working directory is read on your own machine to count file extensions and is never sent.

What it is used for

  • Deciding which question to offer you, and whether you match a buyer's audience.
  • Paying you: an answer becomes a ledger entry, and the ledger is what a payout run reads.
  • Enforcing the limits that keep the panel worth buying — at most 10 paid answers a day, and attention checks mixed in with them.
  • Weekly aggregates from the unpaid profile questions, published on the data page. Those are counts by option. No individual answer is published.

Nothing here is sold, and nothing is used to build a profile for anyone but you and the buyer of a study you answered.

What a buyer receives

One row per answer: the option you chose, when you chose it, your country, your primary programming language (the one with the most files in your file-extension counts), your activity tier, your operating system, and a respondent code. That code is a salted digest of your account and the study — so it is a different code in every study, and two buyers cannot line their exports up to rebuild one person across both.

What a buyer never receives: never your GitHub login, never your GitHub id, never your email address, never anything you typed into Claude Code.

Those four segment columns are withheld until a study settles. On a narrowly targeted study, a buyer watching answers arrive one at a time could otherwise read one person's country, language, tier and operating system off the first row.

Who else handles it

  • GitHub — you sign in with it, and we read your account id, your login and the date the account was created. Nothing is written back.
  • Payments — buyers pay by PayPal. We keep the payment reference and amount for accounting, and nothing about any card. PayPal receives your name, email address and payment details and processes the payment.
  • PayPal — how developers are paid. We hold the PayPal address you give us and send it with a payout batch.

There are no advertising networks here, no third-party analytics, and no tracking pixels. One cookie exists, named mw_session, and it is what keeps you signed in.

How long it is kept

Turn timings, your language mix, your operating system, your tool version and your last-seen time are kept while your account is open, and go when you close it. Answers, the ledger entries behind them and completed payouts are accounting records a buyer has already been charged for, and are kept.

What you can do

Signed in, the settings page lists every value we hold about you, read out of the database rather than described. The same page deletes your account.

Deleting is not the same as erasing, and the difference is worth reading before you do it.

  • Removed: your GitHub login, operating system, Claude Code version, country, activity tier, file-extension counts, last-seen time, the date your GitHub account was created, every turn we recorded, and your payout method.
  • Kept: your answers, the ledger entries behind them and any payout already made. They are accounting records a buyer has been charged for, and after deletion there is nothing on them that names you. The account row stays too, emptied: an internal id, the date you first signed up, and your GitHub id, which is what stops a closed account being made again.
  • Every way back in closes at once: your command-line token stops working, every browser session ends, and any sign-in link still outstanding stops working.
  • Your GitHub account cannot be used with Tickover again. This is permanent.
  • Anything not yet paid out is forfeited: a closed account is left out of every payout run. If you are owed money, wait for the next one first.

If this page changes

The plugin is open source and so is this page's history. A change that narrows what we collect needs no warning; a change that widens it will be shown in the consent screen again before it takes effect.