The short versionin one sentence
The RMS - Screenshots Chrome extension collects no data whatsoever. It has no servers, no account and no analytics. It takes a picture of the tab only when you attach a screenshot to a ReviewMySites comment, hands that picture to the page that asked for it, and sends it nowhere itself.
It does not read, change or send what is on any page: no text, form data or keystrokes.
It does not record the sites you visit or how long you spend on them.
No capture button, no scheduled captures, no video or audio of any kind.
What the extension collects
Nothing. The extension does not collect, store or transmit personally identifiable information, health information, financial information, authentication information, personal communications, location, web history, or user activity. It has no analytics and no telemetry of any kind, and it does not sell or share data with anybody, because it holds none to begin with.
What happens when you take a screenshot
A capture happens only when a ReviewMySites review bar on the page asks for one, which happens only when you attach a screenshot to a comment. The extension photographs the visible area of the tab you are looking at, never another tab and never the rest of your screen, and hands the image straight back to that page.
The extension sends the image nowhere itself. What happens to it next belongs to ReviewMySites: it is uploaded to the project the comment lives in and is visible to the people with access to that project. That part is covered by the ReviewMySites Privacy Policy.
Because a screenshot is a picture of the visible tab, it will contain whatever was on screen at that moment, including anything private that happened to be visible.
Permissions, and why each exists
Access to all sites: optional, and off by default
Chrome’s tab capture API is available only to extensions holding broad host access; it cannot be scoped to one site. This access is declared as optional, so it is not granted when you install the extension and Chrome shows no permission warning there. It is requested from the extension’s own setup screen, which explains what it is for before Chrome’s dialog appears. The same switch revokes it, as does removing the extension from chrome://extensions. The extension re-checks the grant before every capture rather than remembering it, so revoking takes effect immediately.
Scripting
Used only after you have granted site access, to place the extension’s own two small scripts into tabs that were already open at that moment. Chrome does not add them to existing tabs, so without this the extension would do nothing on the page you were working on until you reloaded it. No code is generated or fetched at runtime: every file it runs ships inside the extension package.
Whether it is installed
The extension makes one of its icons readable by web pages. That lets a ReviewMySites page tell “not installed” from “installed but not switched on”, and show you the right next step. Any website could check for that icon in the same way, so a site can learn that the extension is installed in your browser. It learns nothing else: the icon carries no information about you, and loading it gives the site no access to the extension.
No remote code
Everything the extension executes is contained in the package you installed from the Chrome Web Store. It loads no scripts from the internet, evaluates no code fetched at runtime, and makes no network requests of its own.
Children
The extension is a tool for professional teams reviewing websites and is not directed at children under 16. As it collects no data at all, it holds none belonging to anyone, of any age.
Changes to this policy
If this policy changes, the date at the top of the page changes with it. If a future version of the extension ever collects anything, that will be said here plainly, before the version that does it is published.
Contact
Privacy questions, permission questions, anything: send us a message. Or go back to the extension page.