What this extension can see

There is no server

This extension has no backend. Nobody operates a service behind it, so there is nowhere for your data to be collected, sold, or breached. Everything it knows lives in chrome.storage.local on your own machine.

What it stores

• The seat-map addresses you chose to watch, and a label for each.
• What the last check found — seat counts, which blocks were free, and a recent history of how many seats were free over time.
• Your filter settings and how often to check.
• Your Telegram bot token and chat ID, or your webhook address, if you set them up. These are stored unencrypted, readable by anything with access to your Chrome profile. Fine for a bot you made for this; don't reuse one that does anything important.

What leaves your machine

• BookMyShow — pages are loaded in your own browser, in your own logged-in session, exactly as if you'd opened them yourself. No credentials are read or transmitted.
• Telegram, only if you configure it, and only the alert text.
• Your webhook address, only if you configure one, and only the alert text. Chrome asks your permission for that specific address before it is used.

There is no analytics, no telemetry, no crash reporting and no third-party script of any kind. The extension bundles no remote code — the content security policy blocks it.

What it deliberately does not read

BookMyShow's pages carry your account details — name, email, mobile number and a session token — in the same page data as the showtimes. The code does not descend into those parts of it at all, so that information is never read rather than read-and-discarded. There is a test asserting this, using a value that trips if anything touches it.

The tabs permission is not requested. The extension cannot read the addresses or titles of your other tabs, and never sees your browsing history.

Removing it

Uninstalling deletes everything above. There is no account to close and nothing retained elsewhere, because there is no elsewhere.