Privacy by architecture

Your abstract
stays with you.

The matcher is a static website. It downloads the tools needed for inference, then processes the title and abstract entirely inside your browser.

The core guarantee

Static files in.
No abstract out.

The browser fetches the application, a quantized MiniLM model, the current session catalogue, and precomputed session vectors. A background Web Worker performs embedding and ranking locally.

  • No server-side inference
  • No analytics or telemetry
  • No form submission or account
  • No abstract in persistent storage

Data boundaries

What enters, what remains, what leaves

01

Downloaded

Static HTML, CSS, JavaScript, the browser-compatible model, session metadata, and session vectors.

02

Kept in memory

Your title, abstract, tokens, embeddings, and latest ranking exist only in the current page and Web Worker memory.

03

Never transmitted

The submitted title, abstract, derived query embedding, selected results, and scientific topic are not placed in a request.

04

Cached for offline use

Only static application, model, and catalogue assets are cached. Submitted text and results are excluded.

Inspectable behavior

A guarantee you can verify

Open the browser network panel before matching. Requests fetch only static site assets; pressing “Match sessions” does not send the abstract anywhere.

The source contains no analytics integration, telemetry endpoint, account system, or server-side inference route. Closing or reloading the page discards the query held in memory.

Private by default

Ready to find a session?

Open the session finder ↗