Transparency Report
What Kick Augmenter collects
A full, plain-English breakdown of every piece of data this extension collects, what it's used for, and what it will never touch.
Last updated: 21 April 2026
🙈
Anonymous Analytics
Feature-usage counts. Off by default, no identifiers.
Opt-in
🎖️
Badge Sharing (Kick Loyalty)
Your public Kick handle linked to this install so other users see a tier badge next to your chat messages.
On by default
What a single submission actually looks like
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:
{
"extension_id": "kick-augmenter",
"v": "1.4.2", // extension version
"bm": "production", // build mode
"t": 1713348192000, // timestamp
"e": { // event counts since last flush
"po": 1, // popup_open × 1
"sc": 3 // settings_changed × 3
}
}
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.
- 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.
Popup Open
Settings popup was opened
Settings Changed
A setting was modified
Extension Enabled
Extension was enabled
Extension Disabled
Extension was disabled
Tour Started
Onboarding tour was started
Tour Step Viewed
A tour step was displayed
Tour Completed
Onboarding tour was completed
Tour Skipped
Onboarding tour was skipped
Notification Shown
A server notification was displayed
Notification Dismissed
A server notification was dismissed
Error
An extension error occurred
Things explicitly not collected
- Kick chat messages, stream content, or any message body
- Email address, IP address, or any contact info
- Login credentials, session tokens, or cookies
- Browsing history outside of Kick.com
- Any data about users who haven't installed Kick Augmenter
Each system, in detail
This extension runs two distinct data flows. The first is truly anonymous; the second is tied to your public Kick handle. Both are listed here in full.
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.
What's stored:
- 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
- Default state
- Opt-in (off until you enable it)
- How to opt out
- Flip the "Anonymous Analytics" toggle in the popup off. Collection stops immediately.
- Retention
- Aggregated counts retained up to 12 months so we can see trends across releases.
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.
What's stored:
- 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
- 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
- Default state
- On, with a one-click opt-out
- How to opt out
- Toggle "Share your Kick Augmenter badge" off in the in-chat settings panel. The server row is deleted (via the /unlink endpoint) and the link stops immediately. You can also request full removal at any time - every linked row is deletable.
- Retention
- Kept until you unlink or uninstall. If you uninstall and later reinstall, the server keeps your original install_date so your tier survives - that's by design so a reinstall doesn't reset you to Bronze. If you want the row gone for good rather than preserved, use the in-chat opt-out or get in touch.
Why we ask
What your opt-in actually helps with
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.
🛠️
Fixing what's broken
A spike in error counts after a release is often how we first notice something is broken - long before anyone manages to write in.
🎯
Prioritising the right features
Knowing which features people actually use (and which they never touch) means time gets spent on the things that matter.
🗑️
Removing dead weight
Features with near-zero usage become candidates for simplification or removal - keeping the extension lean for everyone.
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.
Storage, retention & security
- Local settings: Your preferences stay on your device in Chrome's local storage. They never leave your browser.
- Transport: All traffic to our backend goes over HTTPS.
- Where it lives: Data is stored in a managed Postgres database with row-level security enabled.
- 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.
- 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.
Your rights & choices
- 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.
- Delete your badge link: Badge links are deletable on request. Opting out via the chat toggle is the fastest path - it hits the /unlink endpoint and removes the row. 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).
- Analytics has no personal link: The anonymous-analytics flow has no field that maps back to you, so there's nothing personally-linked to delete there. Turning analytics off fully ends that collection.
- Uninstall: Removing the extension clears all locally-stored settings and preferences from your device.
Listing
Chrome Web Store disclosures
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
✓
Personally identifiable information
Name, address, email address, age, identification number.
↑What this covers on this page:
Badge Sharing (Kick Loyalty)
✕
Health information
Heart rate, medical history, prescription drugs.
✕
Financial and payment information
Transactions, credit card numbers, credit ratings, financial statements, payment history.
✕
Authentication information
Passwords, credentials, security questions, PINs.
✕
Personal communications
Emails, texts, chat messages.
✕
Location
Region, IP address, GPS coordinates, place ID.
✕
Web history
List of web pages a user has visited and associated metadata.
✕
Website content
Text, images, sounds, videos, or hyperlinks.
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.
Third-party services
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.
Changes to this report
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.
Questions
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.