Privacy Policy

Last updated September 2026

Readout is a Chrome extension that shows you your own Medium article statistics. This page describes, plainly, what it does and doesn't do with your data.

What Readout accesses

Readout requests host permission for medium.com so it can call the same internal API medium.com's own stats pages use. Requests are made with credentials: "include", which means your browser attaches your existing, already-signed-in medium.com session cookie automatically — the same way it would for any page you open on medium.com yourself.

Readout never reads, copies, or stores that cookie. It only rides along with requests the browser makes on Readout's behalf.

What Readout stores

Everything Readout fetches — article titles, view/read/clap counts, earnings, publish dates — is written to chrome.storage.local, a storage area private to your browser profile. This is what lets the dashboard open instantly instead of waiting on a network request every time.

This data never leaves your browser. Readout has no server, no account system, and no backend of any kind to send it to.

What Readout does not do

It does not collect analytics, telemetry, or usage statistics.
It does not use trackers, pixels, or third-party scripts.
It cannot see or access any Medium account other than the one you're signed into in your own browser.
It does not sell, share, or transmit your data to anyone — there is no third party in this picture at all.

Uninstalling

Removing the extension from Chrome deletes everything it stored, via Chrome's normal extension-storage cleanup. There is nothing left behind anywhere else, because nothing was ever stored anywhere else.

Changes to this policy

If what Readout accesses or stores ever changes, this page will be updated to match before that change ships.

← Back to Readout