Telegram Augmenter
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.
- 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
- Personal identifiable information (PII)
- Telegram messages or media content
- Login credentials or authentication tokens
- Browsing history outside of Telegram Web
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 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: Anonymous counts are retained for up to 12 months to let us see trends across releases.
- 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.
- Nothing to delete: Because no submission carries an identifier that maps back to you, there is nothing personally-linked to delete. Turning analytics off fully ends collection.
- 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.
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.