Statement Token Selector

Privacy and permissions

Tokenization runs locally in a dedicated worker using bundled WASM and vocabularies. No account, API key, remote tokenizer, analytics, or network service is used. Selected/pasted text is held in memory and is not written to extension storage. Closing the panel ends its analysis session. Explicit copy controls write the requested text, token IDs, or JSON to your clipboard; clipboard contents are managed by your operating system.

The right-click selection handoff keeps one pending passage per Chrome window in service-worker memory until the panel consumes it, navigation clears it, or it expires after 60 seconds (worker shutdown also clears it). No text is persisted.

Permissions: contextMenus adds the explicit Analyze selected text menu action; sidePanel displays the inspector; activeTab grants temporary access after you invoke the extension; scripting injects selection/highlight code into that activated tab. There are no persistent host permissions or automatic site-access requests. The extension does not bypass Chrome's protected-page restrictions. Password inputs are excluded. The floating preview is visible on the page, so consider your surroundings when inspecting private text.

The PDF token reader opens files only through your explicit local file choice. PDF data, extracted text and highlights remain in memory for the reader session. Rendering and tokenization use bundled workers/assets; there is no PDF upload, storage, remote font/CMap fetch or OCR service. The reader adds no permissions and does not automatically read the PDF currently open in another tab.

Contact

Publisher: Shubham Pareek
Support: shubhampareek12112@gmail.com