Privacy Policy
The extension sends nothing anywhere. There is no server, no account and no analytics.
What it reads
When you open the popup, the extension asks medium.com for your own author statistics using your existing Medium session — the same data the medium.com/me/stats page shows you:
- your published posts: title, publish date, reading time
- per-post daily view, read, clap and new-follower counts
- per-post referrer categories (Medium feed, direct, search, external links)
- your follower count
medium.com.
Where it goes
Into chrome.storage.local on your own computer, so the popup opens instantly next time. That is the only copy.
Nothing is transmitted to the developer or to any third party. There is no backend to transmit it to. The only network requests the extension makes are to https://medium.com/_/graphql — Medium's own endpoint, on your own account, carrying the session cookie your browser already has.
Permissions, and why each one exists
| Permission | Why |
|---|---|
storage | Caches your stats on your machine so the popup opens instantly. |
scripting | Runs the stats requests inside a medium.com page, where your session cookie is first-party. An extension-origin request would not carry it. |
https://medium.com/* | The only site the extension touches. |
tabs permission, no access to other sites, and no remotely loaded
code — everything that runs ships inside the package.
Deleting your data
Removing the extension deletes the cache with it. To clear it without uninstalling, use Remove extension data in chrome://extensions.
Contact
Questions or a problem: open an issue at https://github.com/sbalnojan/medium-breakout/issues.