Instagram Augmenter

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: November 3, 2026

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 "u": "3f6c1a9e-…", // random installation ID "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.
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.

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
PiP Auto-opened Picture-in-picture opened automatically
Fullscreen Used Fullscreen mode was activated
Seek Used Video position was changed
Seek Preview Used The seek-bar preview was used
Keyboard Shortcut Used A keyboard shortcut was triggered
Feed & media
Media Download Started A photo or video download was started (which post isn't sent)
Media Download Succeeded A photo or video download finished
Media Download Failed A photo or video download failed
Caption Auto-expanded A post's caption was expanded automatically
Feed Auto-advanced The feed scrolled to the next post automatically
Feed Auto-advance Cancelled An automatic scroll to the next post was cancelled
Image Maximised An image was opened in the enlarged view
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
Tour Dismissed A tour was closed with "don't show again"
Notifications
Welcome Notice Shown The one-time "Instagram Augmenter is now enabled" notice was displayed
Welcome Notice Dismissed The one-time "Instagram Augmenter is now enabled" notice was dismissed
Notification Shown A server notification was displayed
Notification Dismissed A server notification was dismissed
Diagnostics
Error An extension error occurred

Things explicitly not collected

  • Personal identifiable information (PII)
  • Instagram content or messages
  • Login credentials or authentication tokens
  • Browsing history outside of Instagram

Each system, in detail

This extension runs two distinct data flows. Both are anonymous, and both are listed here in full.

🙈 Anonymous Analytics

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
  • Your country (a two-letter code from our network provider - your IP address is never stored)
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, and your stored country is deleted shortly after.
Retention
Aggregated counts retained up to 12 months so we can see trends across releases. Your country is kept while analytics stays on and deleted shortly after you turn it off.

📡 Service Check-ins

Two small background requests that run whether or not Anonymous Analytics is on. A heartbeat every 5 minutes lets us count how many installations are active and on which version: it sends only the installation ID, which extension it is, its version and its build mode. Nothing else is ever sent. An hourly check fetches announcements, update notices and remote feature switches (used to turn off a broken feature quickly). Neither carries usage counts, page content or anything about what you do on the site.

What's stored:
  • Installation UUID (the same random ID analytics uses, not tied to any account)
  • Extension version and build mode
  • Browser type (Chrome or Firefox): not a field the extension sends. Our server works it out from the heartbeat request itself and keeps only that one word, never the request details it came from
  • When this installation was first and last seen (one row, overwritten on each check-in - no history)
  • A one-way hash of a random secret created on your device, so no one else can reuse your installation ID
Default state
On, with a one-click opt-out
How to opt out
Turn "Update Notifications" off in the popup to stop the hourly check (you'll also stop getting announcements and remote feature switches). On Firefox both depend on the "Technical and interaction data" permission, which is off until you allow it: without it the heartbeat never runs and the hourly check sends no installation ID or secret. Remove the permission in about:addons at any time. On Chrome the heartbeat can't be turned off on its own - uninstalling the extension stops it.
Retention
One row per installation, overwritten on every check-in, with no history kept: when it was first and last seen, and the version, build mode and browser type of its latest heartbeat. Ask via the feedback button to have it deleted.

🔑 User portal

Lets you join or leave the beta, download pre-release builds, and see and manage the installations linked to you.

What's stored:
  • 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
Default state
Opt-in (off until you enable it)
How to opt out
Don't open it: the popup button is the only way in, and nothing is sent until you click it. On the portal, Unlink removes an installation and takes it out of the beta, Remove deletes a passkey, and Sign out ends the session. Opening it is always your own click, so it does not depend on Firefox's data permissions.
Retention
Sign-in links expire after a minute (ten minutes when linking a second installation) and sessions after 30 days; expired ones are deleted automatically. Linked installations and passkeys stay until you unlink or remove them. Unlinking every installation does not delete the account itself, which holds no personal details; to have it deleted, get in touch through the feedback form.
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

↓ CWS: Location
  • Local settings: Your preferences are kept in your browser's extension storage and are never sent to us. If you turn on your browser's own sync, the browser may copy them to your other signed-in devices.
  • 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; the service check-in row is overwritten on each check-in and kept until you ask for it to be deleted.
  • Firefox permissions: On Firefox, analytics and the installation ID in the service check-ins need Firefox's "Technical and interaction data" permission. It is optional and off until you allow it, even if the popup's analytics toggle is on; manage it under about:addons, Instagram 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.

Your rights & choices

  • Opt out of analytics instantly: Flip the "Anonymous Analytics" toggle in the popup. Collection stops at that moment.
  • Service check-ins: The heartbeat and update check run even with analytics off and carry no usage data. Turn "Update Notifications" off in the popup to stop the hourly check; uninstalling stops both.
  • On Firefox: Remove the extension's "Technical and interaction data" permission in about:addons. Analytics, the heartbeat and the installation ID on the hourly check stop from the next request.
  • 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.
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. ↑What this covers on this page: Storage, retention & security
✕ 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

  • 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. Requests reach that backend through our network provider, which also supplies the country described under "Storage, retention & security".

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.

Back to top