A permission audit is a review of which websites can use browser features. Separate permissions from saved data, make one change at a time, and test the feature that justified access.
One topic. 6 useful perspectives.
6 sections
A camera, microphone, location or notification prompt is a request for a capability. It is not proof that the website requesting it is trustworthy. A permission can be appropriate for one feature and unnecessary for another. A video call needs access to a microphone; reading an article usually does not. Start an audit by asking what action you intended to perform and which capability is necessary for that action.
Open the browser's site settings through its own menus, not through a warning displayed by a website. Review the categories available in your browser version. Note the sites with persistent access to sensitive capabilities and those you no longer recognize or use. An unfamiliar address might be an old service name or an embedded provider, so investigate before drawing a conclusion about compromise.
Choose a site you understand and revoke an unnecessary permission. Reload that site and test the exact feature that previously used it. If the feature asks again, read the prompt in context. Where the browser offers temporary or more limited access, consider whether that is sufficient. Avoid treating every prompt as an instruction that must be accepted to continue.
Cookies, cached files and local storage are different from camera or location permissions. Clearing site data may log you out or remove a saved preference, while leaving some browser-level permissions untouched. Revoking a permission may leave account cookies in place. Use the browser's description of each setting instead of assuming that one reset button has the same scope everywhere.
A page can use services hosted on another domain. A video, sign-in widget or payment component may involve a separate provider. This makes it especially important to read the address associated with a prompt. Do not assume the largest logo on the page identifies the recipient of every permission. If the relationship is unclear, consult the service's support material before approving sensitive access.
Finish by revisiting the capabilities you changed and confirming the important workflows still function. Keep a brief note of any exception you deliberately restored. If something fails later, that note helps distinguish a permission decision from a network outage or account problem. You should be able to explain each persistent permission in terms of a feature you use.
No matching sections. Try a different phrase or choose All sections.
Take a moment to check your understanding. This is a reflection aid, not a certification or account check.
Progress is saved only in this browser. No account is created.