Last updated: September 4, 2026
1. Data we process
Mervadon processes source content, titles, URLs, notes, collections, tags, and operation metadata when you explicitly use its capture or Workspace features. Workspace records are stored in the current browser by default.
2. NotebookLM page access
When you explicitly connect to NotebookLM, Mervadon operates in the active NotebookLM page context needed for that action. Mervadon does not bypass authentication and does not operate its own NotebookLM account.
3. Permissions
Page access is requested when you use a capture action. Mervadon does not read or export browser passwords, cookies, WIZ tokens, or authentication files.
4. No product cloud account
Mervadon does not require a Mervadon cloud account or operate a default cloud sync layer. Optional provider requests, if configured by the user, follow the current extension settings and do not change the local-first default.
5. Retention, export, and deletion
You control local records through the Workspace’s export and cleanup controls. Deleting local data does not promise to delete a remote NotebookLM object unless the corresponding explicit NotebookLM action is confirmed.
6. Independent product
Mervadon is an independent product and is not affiliated with or endorsed by Google or NotebookLM. Product capabilities and third-party page behavior may change over time.
7. Contact and changes
For support, use the support page. We may update this policy when the product boundary changes; the effective date above will be updated with the text.