We do not collect your data
Maude does not collect, transmit, or store any of your data on our servers. We don't have any servers. Nothing you do in Maude is sent to us, or anywhere else, unless you create a maude that sends something.
Where your data lives
All of your data is stored locally in your browser using Chrome's local storage. Your maudes (names, URL patterns, scripts, and settings) exist only on your device, unless you publish them. Uninstalling the extension removes its data from Chrome's local storage.
Why Maude requests permissions
Chrome requires extensions to declare permissions. Here is what Maude uses and why:
storage
Your maudes are saved in Chrome's local storage so they persist between sessions. This is the only place they are stored.
activeTab
When you open Maude, we need access to the tab you are viewing so we can show its URL (e.g. to prefill a new maude) and so we can run your maudes on that tab when they match. Access to the tab is only used when you interact with Maude or when you have a maude that matches the current page.
scripting
Maude injects the scripts you specify into the pages you choose for each of them. This permission is used only to run your scripts you have configured, and only on the pages you have configured them for.
sidePanel
Maude uses Chrome's side panel to show the list of maudes and the controls for managing them.
Access to sites your visit
Maude needs access to the sites you visit so it can inject your scripts into them. We do not access page content for any other purpose.
Remote code
Maude injects the scripts you specify into the pages you choose for each of them. Those scripts have full access to these pages and their content, so make sure you trust the scripts you add. We do not use this access in any other way.