Use Later · Local privacy

Your bookmarks. Your choice.

This document details data handling in the current local development preview. All storage is local-first by design.

What stays in this browser

Imported post text, source links, authors, timestamps, and feedback are stored directly in IndexedDB on your device. Feedback includes the task queries you evaluated. There is no account registration, remote database, or cross-device cloud sync. Anyone with access to this browser profile has local access to stored items.

Uploaded JSON files are parsed client-side in memory. Extension settings, private folders, tags, and personal notes are never read or stored. Basic keyword searches run entirely inside your browser without making any external network requests.

What a Jev search transmits

When you explicitly check the Jev authorization toggle and start a scan, your task query and imported post texts are sent to the local application server. The server proxies the query and candidate texts directly to TypeSafe's API for semantic relevance and actionability scoring.

The API key resides strictly on the server and is never exposed to the browser. The local server does not persist request payloads or log post text to disk. Third-party provider data processing is governed by TypeSafe's terms. Review TypeSafe model documentation before sending confidential posts.

Removing your data

You can remove individual posts along with their feedback records at any time, or click Clear local data in the workspace to wipe all stored items and history immediately. Clearing browser site data for this origin also completely removes stored bookmarks.

Preview operational limits

Live evaluation is restricted to local development on loopback addresses (127.0.0.1). Production public endpoints disallow unauthenticated scans. Scans utilize 4 parallel workers, a 45-second deadline, and a process-local daily ceiling of 4,000 reserved evaluations.