TroveKeyTroveKey
गोपनीयता

Privacy and Permissions

How TroveKey stores saved content locally and uses Chrome permissions.

Updated 2026-07-16

TroveKey is designed around local browser storage. The extension accesses tab information, bookmarks, browsing history, and webpage or post content only when necessary for a feature the user requests. It does not require an account and does not upload saved text, notes, tags, metadata, bookmarks, browsing history, or tab data 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;
  • search sends a user-entered query to Chrome's configured default search provider when the user selects that action;
  • storage stores extension settings;
  • <all_urls> allows the command palette and user-initiated capture flow to run on ordinary webpages, and supports an optional original-link check requested from the local library.

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

Direct requests to source websites

When the user runs Check original links, TroveKey sends a credential-free HEAD request directly to each original URL. When the library displays a remote thumbnail, the browser may request that image directly from its source website. The source website receives these requests as it would normal browser traffic, including standard network information such as the requester's IP address. These requests do not pass through a TroveKey server, and TroveKey does not proxy or download full media.

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.

Chrome Web Store Limited Use

TroveKey's use of information received from Chrome permissions and APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. The information is used only to provide or improve TroveKey's disclosed single purpose. It is not sold, used for personalized advertising or unrelated purposes, or made available for human reading.

Contact

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

Privacy and Permissions | TroveKey