Security
Your document is processed
where you opened it.
The LegisComply application is designed so extraction, detection, replacement, and restoration happen inside your browser—not on an application server.
Website document tool · Data flow
Four local operations. One deliberate handoff.
- 01Read
Your browser reads pasted text or extracts text from a selected PDF, DOCX, or TXT file.
- 02Detect
Rules identify likely sensitive values locally. An optional enhanced scan runs a downloaded model in your browser. You review the suggestions.
- 03Replace
Confirmed values become contextual tokens. The reversible mapping remains in memory in the current tab.
- 04You send
You choose whether to copy protected text or share a downloaded working copy with your AI provider. The website does not submit it automatically.
Not sent to LegisComply
Document contents, filenames, detected values, custom terms, protected output, and token mappings.
No cloud document database
The website does not save mappings. The extension offers separate, opt-in encrypted local recovery.
Local storage choices
Website mappings are tab-only. Extension recovery can retain encrypted mappings for 7, 30 or 90 days, with expiry checked on access.
Honest boundaries
What “local” does and does not mean.
Normal website requests still occur. Your browser connects to the site host to load the application. Hosting services may receive ordinary network metadata such as IP address and user agent, but LegisComply does not place document text in those requests.
Your AI provider is outside this boundary. Once you paste protected text into another service, its security, retention, training, and privacy terms apply.
Screenshot redaction. The website tool and extension release 0.5.19 read supported images locally. Review suggestions and add manual boxes before exporting a new PNG with selected pixels permanently replaced. The screenshot reader runs on your device; recognition can miss details. Image redactions cannot be restored. Store availability may differ from the local release.
The extension starts off. Enable it in its menu after reviewing its data-handling disclosure. It then checks supported prompts and files locally. Turning it off withdraws consent and locks recovery; encrypted mappings remain until expiry or deletion.
Local does not mean invisible to the AI site. Its scripts may read text typed into its composer and originals restored into its page. Token replacement on a supported send path does not prove that the provider never accessed the original values. Reload AI tabs to remove restored display values after locking or turning protection off.
Detection can miss context. Automatic matches are a review aid, not a guarantee of anonymity. A distinctive fact pattern can identify a matter even after names are replaced.
PDF, DOCX, and TXT are supported. Image-only PDFs require an extractable text layer. PNG, JPEG and WebP screenshots have a separate local redaction flow.
Microsoft Clarity loads only after an explicit analytics choice. The working application is masked.
Review every output and use only within your organization’s policies and risk tolerance.
For your security review
Follow the information.
Read, detect, replace and restore locally. Keep the reversible mapping on this device.
Copy text or upload a working copy.
The provider’s own retention, training and access policies apply.
On narrow screens, scroll the table sideways to read all three columns.
| Service | When it connects | Information involved |
|---|---|---|
| Vercel · website hosting | When the website and its assets load. | Ordinary request metadata, including IP address, browser and requested path. No document-processing upload endpoint. |
| Microsoft Clarity · website analytics | After you allow product analytics. | Technical and usage information, masked application views and fixed event names. Document values are not event parameters. The extension has no analytics SDK. |
| Hugging Face / jsDelivr · model and runtime delivery | When the website’s optional enhanced scan needs uncached assets. | Download request metadata; delivery networks may also receive it. Inference runs locally. Model/runtime assets may remain cached in the browser. |
| Your chosen AI service | When you use its website or share content. | The content you submit and the provider’s own website telemetry. Original images are not scanned; sharing them can disclose their full contents. |
Extension access & storage
What you enable. What you can remove.
Access to supported AI pages. Content scripts run on listed ChatGPT, Claude, Gemini, Perplexity and Microsoft Copilot domains to check prompts and attachments and restore known tokens. Processing starts after you enable protection. This access does not cover every website.
Storage permission. The extension saves consent, settings and optional encrypted recovery locally. The experimental local-model build also uses an offscreen document to run its packaged model.
Recovery is optional. Token/value pairs are encrypted with AES-GCM using a passphrase-derived key. Site origin, creation time and mapping type remain unencrypted. Recovery is separated by AI-site origin, not by conversation or account. An unlocked session keeps its key in trusted extension session storage.
Retention and deletion. Choose 7, 30 or 90 days; expiry is checked on access. Use the extension menu to lock or delete saved mappings. Turning protection off locks recovery but does not delete it. There is no cloud backup or passphrase reset. Reload AI tabs to remove restored display values.
Original images. Images are not scanned or redacted. By default, sharing requires approval. Remembering approval for an AI site allows later images through without another prompt; restore the ask-each-time setting in the extension menu.
See the privacy notice for website storage, consent and deletion details.
Internal verification · October 16, 2026
Evidence with a defined scope.
Scope. Review of a local development checkout based on revision e92f6a2, including uncommitted changes. Website package 0.2.2; standard extension manifest 0.4.4. Version numbers alone do not identify this tested checkout or establish which code is deployed.
Automated checks. 181 unit tests passed; one was skipped. Another 23 browser checks passed for outbound prompt/file handling and image approval. Two packaged-extension browser checks passed for consent and encrypted recovery, including restart, locking, origin isolation and deletion.
Website check. A fictional-text workflow completed protection and restoration against a local production build. Its test values did not appear in observed request URLs or bodies. Clarity did not load before consent or after declining analytics. This check did not cover analytics-enabled collection or an enhanced-model run.
What this demonstrates. In controlled browser fixtures, selected email and financial values were absent from captured protected send payloads, while originals could be restored in the displayed page. Consent and recovery behavior matched the tested scenarios.
What this does not demonstrate. These checks use simulated AI pages, not a fresh end-to-end assessment of live provider sites. They do not prove complete detection, absence of other collection by the host page, or security of every dependency. The experimental local-model extension was not browser-tested in this review.
Download the verification record (JSON) for test commands, results, limitations and source-file fingerprints.
Assessment status. This is an internal engineering review. No independent penetration-test report, SOC 2 report or ISO 27001 certificate is provided here. These results should not be treated as certification or a guarantee of compliance.
Security contact
Report a concern privately.
Email [email protected] with the subject “Security report”. Include the affected website or extension version, browser version, steps to reproduce and the expected impact.
Use fictional examples. Do not email client documents, live credentials, passphrases or token mappings. If sensitive evidence is necessary, ask for a suitable transfer method first.
For a firm’s pilot review, send the evidence your IT team needs and any gaps this page leaves unanswered. Agree on approved workflows before using confidential matters.
Ready when you are
Protect the document before you prompt the AI.
See the complete workflow using the built-in US sample, or paste your own non-critical text.