Transparency Report

What Instagram 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: June 24, 2026

🙈
Anonymous
No accounts, no names, no IP addresses stored with metrics.
🔢
Counts only
Numeric totals of feature usage - never content, never context.
Opt-in
Off by default. Nothing is sent unless you explicitly allow it.
🎚️
One-click off
Toggle it off in the popup any time. Collection stops immediately.

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": "instagram-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.

Every event this extension can send

↓ CWS: User activity

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.

General
Extension Load Extension was initialized
Popup Open Settings popup was opened
Settings Changed A setting was modified
Video Controls
Video Controlled A video player was interacted with
Play/Pause Used Play or pause button was used
Volume Changed Volume level was adjusted
Speed Changed Playback speed was changed
PiP Used Picture-in-picture mode was activated
Fullscreen Used Fullscreen mode was activated
Seek Used Video position was changed
Keyboard Shortcut Used A keyboard shortcut was triggered
Onboarding Tour
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
Notifications
Notification Shown A server notification was displayed
Notification Dismissed A server notification was dismissed
Diagnostics
Error An extension error occurred

Things explicitly not collected

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

Your rights & choices

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

Health information Heart rate, medical history, prescription drugs.
Location Region, IP address, GPS coordinates, place ID.
Web history List of web pages a user has visited and associated metadata.
User activity Network monitoring, clicks, mouse position, scroll, or keystroke logging. What this covers on this page: Every event this extension can send
Authentication information Passwords, credentials, security questions, PINs.
Website content Text, images, sounds, videos, or hyperlinks.
Financial and payment information Transactions, credit card numbers, credit ratings, financial statements, payment history.
Personal communications Emails, texts, chat messages.
Personally identifiable information Name, address, email address, age, identification number.

Certifications

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.