Your notes.
Your choice to connect.

What the connection uses

You enter a Google email and explicitly approve a connection. During that ten-minute sign-in, the extension reads one temporary authentication cookie from Google's account page and sends it over HTTPS to its configured host. It does not ask for your Google password.

The host exchanges that cookie for Google credentials, verifies Keep access, and stores the email, device identifier and credentials in an encrypted registry. Google credentials have broad account access. Encryption protects stored files; the running host can decrypt credentials to read Keep.

The extension saves a random management key locally so you can approve ChatGPT and disconnect. It uses extension-only storage, with no Chrome Sync. The host stores a hash of that key. Google cookies and master tokens are never saved in extension storage.

What is read and shared

The reader holds note text, titles, labels, timestamps and checklist items in memory. There is no notes database. Authenticated requests return the notes needed by ChatGPT; those results are then handled by ChatGPT under your OpenAI settings and policies.

The extension checks the active connection tab to approve that specific ChatGPT request. It does not scrape notes, inject page scripts, or collect browsing history. Its Google permission is removed after submission, failure or sign-in expiry. Browser permission itself covers more than one cookie; the implementation reads only the specified connection cookie.

Limited use

Keep Context uses account data only to provide the search, read, connection and disconnect features you request. The application contains no advertising, analytics, data-sale feature or use of account data for model training. Google credentials are not returned to ChatGPT or other MCP clients. A host's access to credentials is needed for the connection and should not be used to inspect unrelated account data.

Application access/debug logging is disabled. Google, your host, its network providers and OpenAI may process request metadata under their own policies. The static project website contains no tracking scripts or credential forms; GitHub Pages serves it.

Disconnect and retention

Click Disconnect Keep in the extension. This removes your current hosted account and cached reader, clears the browser key, and revokes its MCP grants. Removing the extension alone does not delete the hosted account. Reconnecting the same verified email revokes the old browser key and ChatGPT grants.

Disconnect does not revoke Google's upstream device/session. Use your Google account's security settings for that. It also cannot instantly erase existing host backups. The application does not create scheduled backups; a deployed host must disclose its backup retention and deletion process.

Local mode and other hosts

The local CLI uses your computer's credential vault or explicitly configured secrets. It has a separate OAuth state file and is independent of hosted accounts. A modified extension or third-party service can behave differently; this page does not make promises on their behalf.

Questions or deletion help

Contact the service host for account-specific help or deletion if you lose the extension key. For software questions, use the project issue tracker. Share only the safe error message; do not post credentials, email addresses or note contents in public issues.