> For the complete documentation index, see [llms.txt](https://docs.tosdr.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tosdr.org/documentation/faq/browser-extension-faq.md). # Browser Extension FAQ 1. Why does the ToS;DR Browser Extension ask for so many permissions, like reading every visited website's data? > ToS;DR requires the permission to read website's data to fetch the URL of the site you are currently on. All website content is not visible to us in any way. You can verify this behavior by browsing through our browser extensions [source code](https://github.com/tosdr/browser-extensions). 2. Does ToS;DR send a server request for every website I visit? > No. The ToS;DR extension comes with a built-in database of all rated services and their URLs, so it can locally check the sites you visit without contacting our servers. A request is only made when you actively interact with the extension to view details. Even then, we don’t send the full URL—just the domain. For example, `drive.google.com/drive?...` would be reduced to `drive.google.com`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tosdr.org/documentation/faq/browser-extension-faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.