Your pages stay yours.

The short version

• The extension reads a page only when you open its find bar on that page.
• Exact word searches run entirely in your browser and never leave your device.
• Meaning searches send your query and the page's passages to our search service to be scored by an AI model. Our server doesn't save them.
• The extension has no accounts, no analytics, no ads and sets no cookies.

What the extension reads

When you press the shortcut or click the toolbar button, the extension opens its find bar in that tab and reads the text of the page, only then and only there. It does not read the values of form fields, plain text areas or password fields, your cookies, your history or other tabs. Text in rich-text editors on the page (a Notion page, an email or chat message you are writing, a comment box) is read like any other page text and, for a meaning search, sent to be scored. Closing the bar removes the highlights.

The find bar is drawn inside the page, so the page's own scripts can see what you type into it, as with any text box on that page.

If you let Ctrl+F / ⌘F open Leita, a tiny script on websites listens for that one key. It reads nothing and sends nothing.

Exact searches

A word or short phrase that appears on the page is matched in your browser, like regular find. Nothing about it leaves your device.

Meaning searches

For anything else, the extension sends your query and the page's text passages over HTTPS to our search service: this site's server, hosted by Lovable on Cloudflare. The server asks an AI model (TypeSafe Jev, through the Lovable AI gateway) to score each passage and sends the scores back.

• Our server doesn't save your query or the page's text.
• To answer a repeated search instantly, the server keeps, in memory, a one-way hash of your connection, the query and the passage together with its score, for up to 15 minutes. The hash cannot be turned back into the text.
• To prevent abuse, requests are rate limited using a salted hash of your connection's address, kept in memory for about a minute.
• Our server's logs record the status, passage counts, timings and the client version (for example ext/1.9.1), never query or page text. The hosting provider (Lovable on Cloudflare) may log the connecting IP address and browser details of each request for operation and security.
• The Lovable AI gateway and the model provider process the query and passages to produce the scores, under their own terms.
• If you set your own search service address on the extension's Advanced page, meaning searches go to that service instead, under that service's own policy.

Google Docs

Each time you open the bar on a Doc, the extension reads the document's text from the open page and also fetches the document's plain-text export from Google with your own Google session. That text stays on your device, except the passages sent for a meaning search as described above.

PDFs

The extension loads the same file again from the address you are viewing (usually from the browser's cache) with your browser's normal session, and extracts its text on your device with a bundled copy of Mozilla's pdf.js; the file is never uploaded. The browser's session storage holds the address and text of up to three recently searched PDFs and, briefly during a PDF jump that reloads the page, your query and results. It is cleared when the browser closes.

Files on your computer

If you allow access to file URLs on the extension's details page, local pages and PDFs are read the same way, only when you open the bar on them.

What is stored on your device

Your Ctrl+F / ⌘F choice, an optional custom search service address, and the session items above. Nothing else. Removing the extension deletes all of it.

Permissions, and why each one exists

• Access to all websites (shown by Chrome at install as "read and change all your data on all websites"): Chrome can only let an extension react to a key on sites it is allowed to run on, and a find tool has to be one key press away on any page. This access is used for two things: opening the bar on the current page when you press the shortcut, and, if you switch it on, a 1 KB listener for Ctrl+F / ⌘F that does nothing except open the bar. Page text is read only when the bar is open on that page. The same access covers the call to the search service and, in Google Docs, the fetch of the document's text export and, in a PDF, loading the file again to read its text. You can narrow it at any time on the extension's card in chrome://extensions.
• activeTab: lets the toolbar button and shortcut still work on the current tab if you have narrowed the site access above.
• scripting: injects the find bar into the current tab at that moment, registers the Ctrl+F / ⌘F listener while that switch is on and, in a PDF, passes a message to Chrome's viewer so the bar knows when the passage is on screen. Nothing else is injected on page load.
• storage: saves the Ctrl+F / ⌘F choice, the optional custom service address and the per-session PDF text described above.
• offscreen: runs the PDF text extraction in a hidden extension page, on your device.

This website

This site is hosted by Lovable on Cloudflare. Cloudflare may log IP addresses to keep the service running and secure, and sets a bot-management cookie (__cf_bm). Lovable's site analytics count page views, and errors on the site are reported to Lovable with the page path. Fonts are served from this site, not from a third party. The playground works like the extension: exact words stay in your browser and meaning searches go to the search service described above.

Sharing

No data is sold, shared for advertising or used to build profiles. The extension includes no third-party scripts, SDKs or trackers.

Children

The extension is a general-purpose tool and does not knowingly collect information from anyone, including children.

Changes

If this policy changes, the new version will be posted here with a new effective date.

Your rights and contact

Because our server saves no query or page text, there is nothing tied to you for us to hand over or delete. You can still ask us anything about this policy or your data.

Published by Axel von Essen.

Email vonessen.axel@gmail.com.