Rather than streaming events as they happen, the extension batches usage counts locally and sends a single compact payload periodically. Here's an example of what gets transmitted:
That's it. The entire payload. No page URLs, no chat content, no keystrokes, no click coordinates, no device fingerprint.
- extension_id
- Which extension sent this - needed so we can route counts to the right project.
- v
- The extension version, so we can spot regressions in specific releases.
- bm
- Build mode (production / staging / development) - separates real usage from testing.
- t
- Local timestamp of when the batch was flushed.
- u
- A random installation ID created on your device. It is not tied to any account or name. It lets us count installations rather than submissions, and it is the ID your country is stored against (see "Storage, retention & security").
- fk / fv
- Only present while an A/B test is running: which test this installation is in and which variant it sees, so results can be compared per variant.
- e
- An object mapping short event keys to integer counts. Every possible key is listed below.
This is the complete, exhaustive list. The extension cannot send anything that isn't on this page - if it's not here, it isn't being collected.
Things explicitly not collected
- Kick chat messages, stream content, or any message body
- Email address or any contact info
- Your IP address (only the country it resolves to is kept, and only while analytics is on)
- Passwords, or any cookie other than your Kick session token, which badge sharing sends for an account check when linking and about every 30 days, and never stores (see Badge Sharing)
- Browsing history outside of Kick.com
- Any data about users who haven't installed Kick Augmenter
Every data flow this extension runs is listed here in full: what it stores, why, and how to turn it off.
Lets us see which features are used, spot regressions after a release, and decide what to build next. Every field is on the "What a single submission actually looks like" sample below.
- Installation UUID (random, not tied to any account)
- Extension version and build mode
- Integer counts for each event listed below
- Local timestamp of the flush
- Your country (a two-letter code from our network provider - your IP address is never stored)
Displays a bronze / silver / gold / legend tier badge next to fellow Kick Augmenter users' chat names so users can recognise each other. Any installation of the extension on Kick can query whether a given handle is linked - that's how the badges appear in chat, and it is intended behaviour.
- Your public Kick username (the handle others already see in chat)
- Your numeric Kick user_id (stable identifier Kick assigns to each account)
- The installation UUID this handle is linked to
- Your Kick session token, read from your Kick login cookie, when linking and about every 30 days after that. On Chrome it is sent automatically while badge sharing is on, which is the default. The token can access your Kick account, so our server uses it only to ask Kick which account it belongs to, so nobody can link an account they aren't signed in to, and then discards it. It is not stored or logged
- install_date - the timestamp of this installation's first check-in, used to compute your tier
- linked_at - the server timestamp when the link was created
The heartbeat tells us how many installations are active and on which version, so a broken release shows up quickly. The notification check is how announcements, update notices and feature switches reach the extension.
- Heartbeat (every few minutes while the browser is open): the random installation ID, which extension it is, its version and its build mode. Nothing else is ever sent
- Browser type (Chrome or Firefox): not a field the heartbeat sends. Our server works it out from the heartbeat request itself and keeps only that one word, never the request details it came from
- Notification check: which extension and version is asking, so the server can send the notices, feature switches and settings meant for it. With the installation ID attached it also records when this installation last checked in
- Both carry a per-installation secret that proves the ID belongs to this installation; it is never shown or stored anywhere else
Lets you join or leave the beta, download pre-release builds, and see and manage the installations linked to you.
- Opening it from the popup's account button: the extension sends this installation's random ID and its secret once, to get a one-time sign-in link that expires after a minute
- A portal account: a random account ID with no name, email or password, and the installation IDs you link to it, with which extension each is and when it was linked
- Sign-in sessions: a random token kept in a cookie on the portal site, stored on our side only in scrambled (hashed) form, with when it was created and last used
- Passkeys, if you add one: the public key and ID your browser creates, when it was added and last used, and the device type you pick from a list. The private key never leaves your device
- Beta membership: whether each linked installation has joined the beta
This is a small indie project with no users table, no sign-ups, and no way to "ask" anyone what they think. Anonymous counts are the only feedback loop we have - and they directly shape what gets built next.
In short: opting in is the single most useful thing you can do to shape the extension - and it costs you nothing but a handful of integers per week.
- Local settings: Your preferences stay on your device in your browser's extension storage. They never leave your browser.
- User notes are private: Notes you write on other Kick users stay in your browser and are never sent to us or shown to anyone. Versions before 28 October 2026 also copied notes to our server; those copies were deleted on 28 October 2026, and the server no longer stores any.
- Transport: All traffic to our backend goes over HTTPS.
- Where it lives: Data is stored in a password-protected, managed database. Only our own analytics server reads or writes it - the extension never talks to the database directly.
- Retention varies per system: See each system's detail card above for its retention rule. In short: anonymous counts roll up for up to 12 months; badge-sharing rows live until you unlink or uninstall.
- Firefox permissions: On Firefox each kind of data above needs its own Firefox data permission (Technical and interaction data, Personally identifying information, Authentication information, Website content). All are optional and off until you allow them; manage them under about:addons, Kick Augmenter, Permissions.
- Country: When analytics is on, our network provider works out which country a submission comes from, and we store that two-letter code once against your installation ID. Your IP address is never stored. We use the country only to see roughly where the extension is used - for example, to decide which languages to support. It is kept while analytics stays on and deleted shortly after you turn analytics off.
- Feedback form: If you choose to submit feedback via the popup button, that's a separate web form - it may ask for an optional email, and that data is handled under the same no-sharing rules. The extension itself never collects or transmits feedback data.
- Opt out of analytics instantly: Flip the "Anonymous Analytics" toggle in the popup. Collection stops at that moment.
- Opt out of badge sharing: Toggle "Share your Kick Augmenter badge" off in the in-chat settings panel. The link is deleted from the server immediately and your Kick session token is no longer sent.
- On Firefox: Remove any of the extension's data permissions in about:addons. The matching requests stop from the next one.
- Delete your badge link: Badge links are deletable on request. Opting out via the chat toggle is the fastest path - it removes the row from our server. Use the feedback button if you want the row gone for good rather than just opting out (opting out + reinstalling would re-link; a hard delete won't).
- Leave the user portal: On the portal, unlink each installation and remove your passkeys; unlinking also takes an installation out of the beta. To have the account itself deleted, use the feedback button.
- Turning analytics off deletes your country: Usage counts are tied only to a random installation ID, never to an account or name. The one location detail, your country, is deleted from our server shortly after you turn analytics off.
- Uninstall: Removing the extension clears all locally-stored settings and preferences from your device.
These are the exact data-usage declarations made on the Chrome Web Store listing page for this extension. The listing's "Privacy practices" tab and this report should always agree - if they don't, the report is wrong and we want to know. Where a category is ticked below, the link under it points to the exact section on this page that backs the declaration.
Data the extension collects
Certifications
- I do not sell or transfer user data to third parties, apart from the approved use cases.
- I do not use or transfer user data for purposes that are unrelated to my item's single purpose.
- I do not use or transfer user data to determine creditworthiness or for lending purposes.
Our entire analytics stack is intentionally minimal. We don't use Google Analytics, Mixpanel, Sentry, or any consumer tracking SDK. Data is processed only on our own analytics backend - it is never shared with, resold to, or syndicated through advertising networks or data brokers. Requests reach that backend through our network provider, which also supplies the country described under "Storage, retention & security".
If we change what is collected - for example, to add a new event when a new feature ships - this page is updated and the "last updated" date at the top will reflect the change. The same page is the single source of truth: if it isn't listed here, it isn't being collected.
If something here is unclear or you want more detail on any event, the fastest way to reach us is the feedback button in the extension popup. That opens a simple form - no account required.