This API edition uses your own DeepSeek key. The developer operates no lookup server and collects no analytics or lookup history.
What goes to DeepSeek
Clicking the selection icon or using Ctrl+X (⌘X on Mac) on reading text sends your selection and, if enabled, up to 600 nearby characters to DeepSeek's official APIs. Selecting or copying alone sends nothing. News, time-sensitive selections and “Explain a little more” also start a web search. Search evidence is then passed to the model.
Your key stays in session memory
Your key is held only in Chrome’s in-memory session storage, restricted to trusted extension contexts. It is not written to local or sync storage or sent to reading pages. Re-enter it after restarting Chrome or disabling, reloading or updating the extension. Ordinary background-worker suspension retains it. On startup, this version deletes the former local-storage key without importing it.
You control the sharing
Change or replace your key through API settings. Pause globally or per website, or turn nearby context off. Answers stay only in memory for the current card. Pausing retains the current session key. Clearing session storage or ending the browser session removes it; uninstalling also removes saved preferences. Local removal does not revoke a key at DeepSeek.
Your DeepSeek account
Setup checks your key using the model-list API without sending reading text. Model and search calls are billed to your DeepSeek account. DeepSeek handles submitted data under its current API policies. Check them before submitting sensitive text. Opening original sources or the optional practice article contacts those websites.
EXPLAINED · PRIVACY