When you install the Loupely Chrome extension, Chrome displays a list of permissions the extension is requesting. Some of those notices can sound alarming even when what they’re actually asking for is limited and specific.
What Loupely requests and why #
Active tab access. The extension needs to see the page you’re running a capture on, so it can observe browser-side events as they happen. This is scoped to the tab where you initiate the capture. Loupely doesn’t watch other tabs.
Local storage. The extension saves your connection key and your account session locally so you don’t have to sign in every time you open the popup. Nothing from your browsing activity is stored.
Network requests. The extension communicates with your WordPress site’s REST API (to pair with the plugin) and with Loupely’s diagnostic servers (to send the capture data for processing). It doesn’t make requests to unrelated domains.
What Loupely doesn’t access #
The extension doesn’t request access to your browser history, your other open tabs, your passwords, or any website you haven’t explicitly initiated a capture on. The scope of access is limited to the capture you’re running, on the page you’ve opened the extension on, at the moment you run it.