Privacy

This website

There is no analytics, no tag manager, no tracking pixel, no advertising network and no A/B testing. No cookies are set. Nothing on this site tries to work out who you are or whether you have been here before.

Your browser makes no third-party requests while reading this page. The two typefaces are served from this domain rather than from Google, so visiting does not tell Google you were here.

The one thing stored on your device

If you use the light/dark control in the header, your choice is written to localStorage under the key lancescope-theme. It stays in your browser, is never transmitted, and choosing “Follow the system” deletes it. Clearing site data removes it. That is the only thing this site stores.

What the server unavoidably sees

The site is hosted on Vercel, which keeps ordinary request logs — the sort every web server keeps, including IP address, user agent, and the page requested. Those logs are Vercel’s, retained under their policy, and they are not read, exported, joined to anything, or used to build a profile. See Vercel’s privacy policy.

To show the current version, this site asks GitHub’s public API for the latest release. That request is made by the server, once an hour, not by your browser. Clicking a download or GitHub link does take you to GitHub, at which point their policies apply.

The live demo

demo.lancescope.mlynn.dev is a second host, and a separate one: it runs the console as a container rather than on Vercel, so it keeps its own request logs of the same ordinary kind. It has no account, no cookie and no telemetry, and it stores nothing you do on it — the settings file is the only thing that build can write, and the demo is configured so that nothing can write it.

One thing is worth naming plainly. The demo reads its dataset from huggingface.co over the network as you browse, so the queries you run there become requests to HuggingFace from the demo server. They carry no identifier of yours — HuggingFace sees the server, not you — but they do mean your activity leaves that machine. To keep queries in one place, run LanceScope on your own computer against a database on your own disk, where it reaches the network only in the four cases named on the front page.

The app

LanceScope runs on your machine and reads your data. It has no account, no sign-in, no licence check and no telemetry — nothing reports back to anyone, including us. It makes network requests in exactly four cases, three of which you initiate:

• A dataset you point it at over hf://, which it reads from huggingface.co.
• A language model, if you configure one — either a local model, or an API you supply a key for. Nothing is sent to a model unless you turn that layer on.
• Downloading the app itself, from GitHub.
• The update check, and it is the one you do not initiate. Once a day on launch — and whenever you pick Check for Updates — the app fetches a small file from this project’s GitHub releases to see whether a newer version exists. It sends nothing but the request: no identifier, no version, no data about your machine or your database. If there is a newer one it says so; it does not download or install anything.

Your database contents, file paths, queries and settings stay on your machine. The files the app writes for itself all live in your user config directory: its settings, the size and position of its window, and the date it last checked for an update. None of them holds anything about your data.

Contact

Questions, or something here that looks wrong: open an issue.