Privacy and Permissions

TroveKey is designed around local browser storage. The extension does not require an account and does not upload saved post text, notes, tags or metadata to a TroveKey server.

Local saved-content storage

Saved social posts and webpages are stored in the extension's IndexedDB database inside the current browser profile. Removing the extension or clearing its extension data can remove this library, so TroveKey provides versioned JSON export and validated import.

Why TroveKey requests browser permissions

TroveKey uses each permission only for the feature the user requests:

• tabs and activeTab search, switch and act on browser tabs;
• bookmarks search, create and remove Chrome bookmarks;
• history searches browser history;
• browsingData runs explicit data-clearing commands after confirmation;
• contextMenus adds the optional Save to TroveKey action;
• storage stores extension settings;
• <all_urls> allows the command palette and capture flow to run on ordinary webpages.

TroveKey does not collect cookies, login tokens or hidden feed data.

Capture limitations

Websites change and may block access through login walls, paywalls or protected page surfaces. When TroveKey cannot read all content, it marks the capture as partial and saves the canonical link plus available metadata.

Data control

The settings page shows local storage usage and provides export, import and clear-data controls. Destructive operations require confirmation.

Contact

For privacy questions or security reports, use the website's help center.