Privacy

Privacy and data handling

ContextKeeper is designed around local browser storage. This page explains what the extension saves, what it does not currently provide, and the limits of local storage.

What ContextKeeper stores

When you save a workspace, the extension stores its name, selected eligible tab titles and URLs, pinned state, and an optional note. Workspace data is stored with Chrome's chrome.storage.local.

Where the data is stored

The extension uses the browser's local storage and does not require a ContextKeeper account or remote database. The current extension code does not implement a ContextKeeper server upload or cloud-sync feature.

Permissions used

The extension manifest requests the Chrome tabs and storage permissions. The tabs permission allows it to read eligible tab information for the workspace-saving workflow; storage is used to persist saved workspace data locally.

Important security limits

Local browser storage is not encryption. Do not place passwords, authentication tokens, confidential URLs, or other secrets in workspace notes. A JSON export can include workspace names, URLs, titles, and notes, so protect backup files and share them only when appropriate.

What is not included

Version 1.0.0 does not include user accounts, cross-device sync, AI processing, or JSON import. This website does not claim that the extension has undergone an independent security audit or formal certification.

Changes and questions

If the extension's data handling changes in a future release, this page should be reviewed and updated to match the code. For questions or issue reports, use the GitHub issue tracker. Avoid including private URLs or backup files in public issues.