Passport

Your information. Your choice of what to share.

Passport is an independent, open-source personal-information vault from Toll Bench. It encrypts information in your browser and lets you export selected information as a separately encrypted package. The standalone application runs locally without an account, AI provider, telemetry or cloud storage. A separate hosted client connects encrypted storage to an authenticated host through an isolated frame.

Status: 0.1.0a11 released, reference alpha. Not independently security-audited. Includes the standalone reference application and a separate hosted client component. Use sample information while evaluating it. Standalone behavior is unchanged. See hosted embedding and security responsibilities.

Run it

Install the published release: python -m pip install toll-passport==0.1.0a11, then toll-passport serve. See the verified release receipt.

Python 3.9 or later and a current browser with Web Crypto and IndexedDB are required. From a source checkout:

python3 -m venv .venv
. .venv/bin/activate
python -m pip install .
toll-passport serve

Open http://127.0.0.1:8765. Keep that exact address and port: browser storage is scoped to its origin. A different port or localhost is a different storage location. Install a released wheel with python -m pip install path/to/toll_passport-0.1.0a11-py3-none-any.whl. A GitHub release does not imply availability on PyPI; check the release notes.

Standalone capabilities

• Create a vault with an automatically generated encryption key.
• Save notes, structured answers, optional labels and multiple files locally.
• Find saved answers for an exact subject and task context, review their source and age, and explicitly fill the local answer form.
• Encrypt titles, tags, filenames and contents before writing browser storage.
• Lock and unlock using a separate recovery file.
• Export an encrypted backup and restore it into another browser.
• Select exact fields from an exact record version; preview and export an independently encrypted sharing package.
• Open a received sharing package locally and save it in your vault.
• Remove records or remove the local vault; existing exported copies remain.

The contact information itself can be stored as information. CRM workflows, contact lists, goals, action packs, recurrence, agent dispatch, marketplace payments and reputation belong to Toll Bench and are outside this project.

Recovery and storage

Creation automatically requests a recovery-file download. Store that file securely, separately from your encrypted backups. It contains the key that unlocks the entire vault. Export a new encrypted backup after changes. Recovery requires both the backup and recovery file if browser storage is lost. No operator can reset a lost key. Browser storage can be cleared, evicted or unavailable; it is not a backup.

The unlocked key is kept in page memory, not IndexedDB, localStorage or the Python server. Refreshing, closing or locking the page requires the recovery file again. A compromised device or browser extension may read unlocked information. This alpha has no passkeys, OS keychain integration, password protection or multi-device synchronization.

Files are limited to 25 MiB each; the encrypted snapshot is limited to 100 MiB. Base64 encoding, metadata and versions consume some of that space. The local server only serves five static assets on loopback and accepts no uploads. It is not a remote deployment server.

Sharing

Only explicitly selected fields are copied into a release. The original vault key is never used as the sharing key. Download the encrypted package and its separate package key, then deliver them through appropriate separate channels. The standalone application sends nothing. This download flow is separate from hosted item and question disclosure channels.

The recipient and purpose are authenticated package metadata, not verified recipient identity or access control. Anyone possessing the package and key can decrypt it. Downloads cannot be recalled, revoked or made to expire. The optional hosted channels release explicitly approved copies to an authenticated host. The host implements verified recipient authorization, grants, expiry and future-read revocation; the public client is not that authority. See selected item sharing and the integration boundary.

Optional question labels

A question-producing application may suggest a stable question key. Subject, task reference and reuse scope come from trusted owner context. The reference UI accepts optional labels including unfamiliar ones. Recognized labels can find saved answers for matching context; the owner reviews candidates and explicitly chooses an answer to fill the form. Missing labels never prevent saving, fail an agent or affect a score. Answers remain private until selected for release. Hosted applications can supply bounded authenticated questions through the optional channels; intake and delivery authorization remain the host’s responsibility. Question metadata contract.

Development

Runtime code has no third-party package dependencies: Python standard library and browser Web Crypto only. No third-party JavaScript or fonts are loaded.

python -m pip install build twine
python -m build
python -m twine check dist/*
python -m pip install dist/*.whl
python -m unittest discover -s tests -p 'test_*.py' -v
node --test tests/*.test.mjs

Node 22 is used for core tests. Browser checks use Playwright as a development-only dependency; see verification. CI tests and builds the distributable. Publishing is a separate manual, tag-bound workflow with PyPI Trusted Publishing; it requires account-side setup described in releasing.

Ownership and attribution

Copyright 2026 Steven Ochs and Tollbench. Created for Toll Bench. Licensed under Apache-2.0; preserve NOTICE with redistributions as applicable. This license applies to Passport's included source, not the private Toll Bench application or its trademarks. See third-party notices and citation metadata.

This is newly authored Passport code. No Ente, Bitwarden or proprietary Toll Bench implementation was copied. Cryptographic primitives are supplied by Web Crypto; this is not a new encryption algorithm. See security and format before extending the reference implementation.

Hosted capabilities

The optional batch question channel supports private drafts and uploads followed by explicit disclosure to one named recipient. Trusted fixed panels let a host add its own encrypted-book UI without publishing its business features. These interfaces do not grant agents access to the vault.

The optional deterministic topic catalog supports private entity-specific answer reuse with editable question chips and the existing Send action. Unknown hints do not fail questions or grant access to saved information.

The optional item picker and local source import helper support exact note/file selections, fixed folder snapshots, private uploads and repeat-safe source records. Encrypted intent persistence precedes explicit release. Item grants, operator flows, goals, CRM, connectors and provider-specific import conversion remain host features. Imported prose never silently becomes a classified fact.

Your hosted information library

Opening a hosted book first shows its actual state. A new book generates a key in your browser and waits for you to save the recovery file. An existing book asks for that original file to unlock. Loading and storage errors never look like an empty book.

After unlocking, browse actual notes, files and saved answers in one library. Search matches titles and tags locally; type filters do not classify or infer information. Expand an item to read it, download its files, remove it or choose exactly what to share. Add information and upload controls remain visible; the manual saved-answer form and recovery/export settings are secondary. No material is automatically imported from other services. See the hosted UI contract.