Skip to content

No-Server Architecture

JuryBinder is a local-first application. All case data lives on your device. The application makes no network requests containing juror names, notes, flags, favorability ratings, or any other case content.

What this means in practice

When you type a note about a juror in JuryBinder, that note is written to a file on your device. It is not sent to JuryBinder's servers. It is not processed by any cloud service. It is not logged, indexed, or stored anywhere other than your .jbinder file and the browser's private local storage.

This is not a privacy setting or a data retention policy — it is a structural property of how the software is built. There is no code path that transmits case data. There is no server to receive it.

The .jbinder file

Your case data lives in a .jbinder file on your device. This is a standard ZIP archive containing JSON files for each contributor's notes and mutations, plus an Excel snapshot of the current juror state. You own this file. It lives wherever you put it — your laptop, an iPad, a USB drive, a secure firm server. JuryBinder never touches it except when you explicitly open, edit, or export it.

If you share the file with co-counsel via email or AirDrop, it moves directly between your devices. It does not pass through JuryBinder's infrastructure.

What the license server does and doesn't receive

The only network requests JuryBinder makes are to the license server, and they contain only:

  • Your license key (a random alphanumeric string)
  • When creating a new case: a randomly generated UUID with no attached meaning
  • The app version number

The server never receives the case name, juror names, questionnaire content, notes, flags, or any other case-specific information.

The Discovery Strip

JuryBinder includes an Export → Discovery Strip function that produces a clean Excel file containing only juror names, seat numbers, and raw questionnaire answers — no notes, no flags, no mutation history, no favorability ratings. This file is safe to share with opposing counsel or the bench in response to a discovery request.

The full .jbinder file contains your work product and should be treated accordingly.

Verifying the software

Each JuryBinder release is distributed with a SHA-256 hash of the application file. You can verify the file you received matches the published hash to confirm it has not been modified. Instructions are available at jurybinder.com/verify.

For IT and compliance teams

JuryBinder requires no server installation, no VPN configuration, and no data leaving your network. It runs entirely in the browser using standard web APIs. The application can be reviewed by opening the single HTML file in a text editor.