What Permissions Have I Granted
Permissions on this site
Detecting…
Shows Permissions API state for this origin. Some browsers hide or limit certain permission names.
How to use
- Open the page on the site you want to audit — permission states load automatically.
- Read the headline for how many permissions are granted, and the table for each name.
- Change permissions in your browser's site settings, then click Refresh.
FAQ
What permissions have I granted to this site?
The table lists Permissions API states for this origin: granted, denied, prompt (not decided yet), or unsupported in your browser. The headline summarizes how many are granted.
Why does a permission show unsupported?
Safari, Firefox, and Chromium differ on which permission names can be queried. Unsupported does not always mean the feature is unavailable — only that this API cannot read it.
Is this the same as browser Settings → Site settings?
It should align for permissions the API exposes. Your browser settings panel is authoritative for revoking access; this page is a quick in-tab audit.
Why is geolocation still prompt after I allowed it?
Reload after changing settings. Some browsers cache permission state until the tab is refreshed or the site requests the feature again.
Do you upload my permission list?
No. Queries run locally against navigator.permissions in your browser.
Can I reset all permissions?
Use your browser's lock icon or Site settings for this origin and clear permissions. Then refresh this page.
Introduction
What Permissions Have I Granted lists what your browser reports for this website — camera, microphone, geolocation, notifications, clipboard, and more — using the Permissions API, with granted, denied, and prompt counts at the top.
Sites you trusted months ago may still hold camera or location access. Auditing permissions should not require digging through five levels of browser settings — this page surfaces the API-visible state in one table.
Permission states
| State | Meaning |
|---|---|
| granted | You allowed this capability for this origin |
| denied | You blocked it |
| prompt | The site must ask again before use |
| unsupported | This browser cannot query that permission name |
Common use cases
- After testing a webcam or mic tool — confirm you did or did not leave access enabled.
- Privacy spring-cleaning — review old localhost or staging origins during development.
- Support — screenshot the table when a site says permission denied unexpectedly.
- Compare browsers — see how strict mobile Safari is vs desktop Chrome for the same URL.
Best practices
- Revoke unused camera and microphone access from sensitive origins first.
- Remember notifications and geolocation are separate rows — denying one does not deny the other.
- Use browser DevTools → Application to inspect cookies and localStorage if needed.
- For webcam testing after granting camera, use webcam test in this project.