Sift privacy policy

Last updated: 14 October 2026

Sift is a Chrome extension that answers questions about the page you're reading. It has no account system and no analytics, and it doesn't show ads or sell data. This page says what leaves your browser, where it goes, and what is kept.

What Sift reads

Sift reads the text of a page only when you ask a question about it in the side panel. It extracts the readable text of the current tab, and any text you've selected, and uses it to answer. It doesn't read pages in the background or when the panel is closed.

What is sent, and to whom

• Nebius Token Factory (the language model provider). Each question is sent with the extracted page text, your earlier questions and answers on that page, and the page's URL. This is how the answer is produced.
• Tavily (web search). When the model decides it needs more of the same site, a search query it wrote is sent, limited to the site you're on. If a result needs reading in full, that result's URL is sent too.
• Sift's demo server. If you haven't entered your own API keys, requests to Nebius and Tavily go through a small server run by the Sift developer (on Cloudflare Workers), which adds shared keys and forwards the request. It receives the same content listed above. It doesn't store that content. It keeps only a per-day count of requests for each random install ID and IP address, to enforce usage limits, and deletes counts from earlier days. Cloudflare, as the host, may keep standard operational logs.

Those providers handle the data under their own terms and privacy policies. Pages you don't ask about are never sent. Avoid asking Sift about pages that hold information you don't want shared with these providers, such as private documents, banking or medical pages.

What is stored on your device

• API keys you enter on the options page are kept in chrome.storage.local, on your device. Each is sent only to the service it belongs to (Nebius or Tavily).
• A random install ID, created when you use the demo server. It isn't linked to you and exists only so the demo server can count requests.
• Conversation, extracted page text and run traces are kept in chrome.storage.session, which Chrome clears when the browser closes. Run traces hold question and answer text only if you switch that option on in the options page.

Shared thread links

The Share button, after you confirm, copies a link that carries the thread you chose to share (questions, answers, quotes and the page URL) in the part of the link after #. That part isn't sent to any server when the link is opened. Anyone you give the link to can read the thread. The link page is hosted on GitHub Pages.

Permissions

Sift asks for access to web pages so it can read the one you're asking about. It uses that access only for that purpose. It doesn't use the data for anything unrelated to answering your question, doesn't sell it, and doesn't use it to judge creditworthiness or for lending.

Retention and deletion

Sift keeps no server-side copy of your conversations. Remove your keys on the options page, or uninstall the extension, to delete everything stored on your device.

Contact

Questions or requests: open an issue at github.com/aishahsofea/sift.