Short version: StyleSpy runs entirely on your device, collects no personal data, and sends nothing to any server.
What StyleSpy accesses
To inspect a page, StyleSpy reads the page's DOM and computed CSS in the tab you're looking at — element styles, text, attributes, and structure. This happens only on the active page, and only to display the information back to you in the side panel and table.
What StyleSpy stores
-
Your most recent capture and your theme preference are saved using
Chrome's local extension storage (
chrome.storage) so the panel can restore them. - This data lives only on your computer. It is never transmitted off the device.
- Use the Clear button (panel footer) to delete the stored capture at any time.
What StyleSpy does NOT do
- No analytics, telemetry, tracking, or fingerprinting.
- No network requests — StyleSpy has no server and contacts no third parties.
- No accounts, no cookies, no advertising.
- No reading of your browsing history, passwords, or autofill data.
- Data you export (CSV / JSON) is written only when you click Export, to a file you choose.
Permissions & why they're needed
activeTab / scripting |
Inject the inspector into the page you're viewing so it can read styles. |
<all_urls> |
Lets the tool work on any site you choose to inspect. You can restrict per-site access in Chrome's extension settings. |
storage |
Remember your last capture and theme — stored locally only. |
tabs / sidePanel |
Open the side panel and the full-table tab, and target the page you're inspecting. |
Your control
You can restrict StyleSpy to specific sites (right-click the icon →
"This can read and change site data"), clear stored data with the Clear
button, or remove the extension at any time from
chrome://extensions. Uninstalling removes all locally
stored data.
Changes
If this policy ever changes, the updated version will ship with the extension. Because StyleSpy stores nothing remotely, changes only ever affect on-device behaviour.