JevLensA clearer view.
A clear data policy.
Effective September 22, 2026 · JevLens v0.2.0
JevLens is a Solana token research extension and companion workspace. This policy describes what the service collects, where information is sent, how long it is retained, and how to control or delete it.
1. Data we handle
- Public website content: token mint or pair addresses found in visible links on terminals you enable, the public token address in the current supported page URL, or an address you paste into the extension. The full terminal page URL, page text, cookies, balances and transaction history are not sent to our backend.
- Workspace identifiers and authentication: a random workspace ID and bearer credential. Your browser keeps the credential; Neon stores its one-way SHA-256 hash, the workspace ID, creation time and expiry time. No email, name or wallet connection is needed.
- Your saved research: saved token addresses and save times, associated with your workspace ID, plus public market snapshots.
- Public research: market data, security reports, JEV classifications, scores, source context and timestamps. Evaluation history is stored by public token address, without association to an individual workspace.
- Operational data: daily or per-minute usage counters keyed to a workspace. During workspace registration, the service uses a salted HMAC of your network IP for abuse prevention; the application does not store the raw IP. Vercel and other providers may process IP addresses and request metadata in their own operational logs.
- Local settings: consent and enabled-terminal permissions. The extension observes link visibility only to decide which public addresses to evaluate; it does not record mouse movement, keystrokes or general browsing history.
2. How we use it
We use this data to deliver token research, save your watchlist, share your chosen workspace between the extension and dashboard, avoid duplicate API calls, enforce usage limits and operate the service. JevLens does not sell this data, use it for advertising, or use it to determine creditworthiness. Our use and transfer of extension user data is limited to the extension’s disclosed functionality, consistent with the Chrome Web Store User Data Policy and Limited Use requirements.
3. Services that receive data
- Vercel: hosts the dashboard and API and receives service requests and network metadata.
- Neon: stores workspace credential hashes, watchlists, usage counters, public evidence caches and evaluation history.
- DEX Screener: receives public token/pair queries from our backend and supplies market data. Your browser may request token images directly from its image CDN, which receives your IP and ordinary request metadata.
- Rugcheck: receives public token addresses from our backend and supplies available public security findings.
- Pump.fun: receives public creator-address queries for launch history.
- Bubblemaps: when configured, receives public mint-address queries for wallet-distribution metrics.
- TypeSafe: receives public market and security evidence for evaluation by JEV. We do not send it workspace credentials, workspace IDs, your watchlist as a list, or your IP address.
Requests use HTTPS in the production service. Each provider also handles operational data under its own policies. Review Vercel, Neon, TypeSafe, DEX Screener and Rugcheck for their current terms and policies.
4. Retention
| Data | Retention |
|---|---|
| Workspace and watchlist | Until you delete it or after 30 days of inactivity; expired records are removed by the next daily cleanup, normally within a further day. |
| Public evaluation history | Seven days, plus up to one day for scheduled cleanup. |
| Usage counters and hashed registration network identifiers | Two days, plus up to one day for cleanup. |
| Public evidence cache | Used as fresh for 45–300 seconds depending on source. Old rows are eligible for removal after one day and removed by daily cleanup. |
| Unreferenced public token snapshots | Seven days, plus cleanup time. Snapshots referenced by a watchlist remain until no longer referenced. |
| Provider logs and backups | Subject to provider retention policies; deletion from the active application database does not immediately erase provider-managed backups. |
Cleanup also runs when new workspaces are created. If a provider outage delays cleanup, records are removed when cleanup resumes; expired credentials cannot authenticate.
5. Your choices and deletion
Enable each terminal separately. Disable a terminal in the extension popup to remove its permission. Uncheck the research consent control to remove all terminal permissions and stop new scheduled analysis; a request already sent may finish. Disabling research does not delete your watchlist.
Remove saved tokens with the bookmark control. To delete the workspace, open dashboard Settings → Delete my workspace and watchlist, or extension Workspace connection & data → Delete this workspace. Confirming deletes that workspace and its watchlist from the active database and invalidates its credential on all connected devices. Public token research, which is not linked to the workspace, expires under the separate retention schedule.
Uninstalling removes extension-local settings but does not notify us to delete a remote workspace. Delete it before uninstalling, or let it expire after inactivity. Keep your private workspace connection confidential: someone with it can access the workspace’s saved tokens. Sharing a workspace is optional.
6. Permissions and code
Storage stores your local consent and workspace
credential. Scripting registers locally bundled code on
enabled terminals. Required network host access is limited to
https://jevlens.vercel.app/*. Optional terminal access is
limited to axiom.trade, gmgn.ai,
bullx.io, and neo.bullx.io. No wildcard
terminal subdomains, wallet permissions, cookies permission or
browsing-history permission are requested. JEV returns data; executable
extension code is bundled locally.
7. Research limits
JevLens provides experimental research context, not investment advice, a guarantee of safety or a return prediction. Missing evidence is shown as unavailable. Social activity and narrative provenance do not yet have independently verified sources. JevLens does not place trades, route transactions or collect trading fees.
8. Support and policy updates
See JevLens support for connection, privacy and deletion help. For publisher correspondence, use the verified developer contact displayed on the Chrome Web Store listing once published. The publisher must configure that contact before store submission. Changes to this policy will be published here with an updated effective date; material changes to extension data use will require a new disclosure.