Sensitive access
See observed requests for camera, microphone, location, clipboard, screen sharing, and file selection.
Allowed · blocked · unclearSite Privacy Guard turns privacy signals into plain language—what a site requested, what the browser appeared to allow, and where you can review the permission.
If you did not start a call or recording, review this site’s permissions.
Repeated requests are grouped by destination—not listed one by one.
Start with the access that might matter to you. Routine website connections are grouped and shown as information, not proof of tracking.
See observed requests for camera, microphone, location, clipboard, screen sharing, and file selection.
Allowed · blocked · unclearReview visited website hostnames and saved privacy signals after a tab is closed.
From install onwardReview distinct external destinations. Repeated requests are grouped so the timeline stays readable.
Signals, not accusationsOpen browser site-permission settings where available, or get plain guidance for files and screen sharing.
You stay in controlColor is paired with words so the report remains useful for people with different vision needs.
A sensitive request appears to have succeeded. Review it if you did not expect it.
A request was seen, but its result is unclear. Check the browser permission if concerned.
Other-company or tracker-name signals can be normal site features or false alarms.
A denied request or quiet report is not proof that a site collected nothing.
Site Privacy Guard v1.5.1 is an unpacked extension for Chromium browsers. This ZIP is included beside this HTML page.
Allow the extension’s requested website and navigation access so it can report the signals described above.
Download the ZIP, then extract it to a folder you can keep. Do not load the ZIP file itself.
chrome://extensions · Enter this in Chrome’s address bar.
Use the switch near the top-right of the extensions page, then choose Load unpacked.
Choose the folder containing manifest.json. Pin Site Privacy Guard from the toolbar menu.
Monitoring begins after installation. Click the shield icon to check the current site or open all-sites history.
Sunil Bishnoi · Cyber Security Intern
IOCL Gujarat Refinery
I’m learning about networking, data centers, and identity and access management. I made Site Privacy Guard to make browser privacy signals easier for everyday people to understand—and to point them to a practical next step when a sensitive permission appears.
Made with: Manus AI, HTML, CSS, and JavaScript. The browser extension uses JavaScript and Chromium Manifest V3 APIs.
Privacy tools should explain what they can—and cannot—see.
No. It reports observable browser/API attempts and request destinations. It cannot see encrypted HTTPS contents, form values, cookies, server-side collection, or prove what a company stored.
No. Websites normally see your public IP when you connect. Site Privacy Guard does not look it up, infer it, or save it.
No. It is an auditor, not a blocker. Browser permission buttons take you to site settings when possible. Screen sharing uses the browser’s share picker; a file-selection signal does not confirm upload.
No. Visit history starts after installation and records hostnames and visit times only. It does not request access to your browser’s previous history.
Records stay in the browser’s local extension storage. The timeline is capped at 500 events per hostname. Export is manual; clear a single site or the whole logbook whenever you want.
Refresh tabs after installing or updating. Browser settings, extension stores, internal pages, and other restricted pages cannot be monitored. A quiet report is not proof of zero collection.
Review the signal, decide what you trust, and change browser permissions yourself.