Privacy, in plain language.
Your package is processed in the browser tab you opened. It is not uploaded to this application.
What stays on your device
Selected document bytes, filenames, relative paths, extracted text, search terms, snippets, document hashes, duplicate groups, and generated CSV files remain in browser memory. The app does not use cloud document storage or a server-side parsing route.
What can reach our server
Billing requests contain a Checkout attempt identifier or the license code you enter. Credit use adds a random operation identifier. Minimal aggregate events use a random installation identifier and fixed, coarse buckets for package size, file count, and supported-format counts.
What aggregate events exclude
Events reject filenames, paths, document hashes, extracted content, snippets, search terms, exact sizes, solicitation identifiers, and open-ended metadata. There is no fingerprinting or automatic page/form capture.
Retention and clearing
Aggregate usage events are intended for a 90-day retention window. Billing and credit-operation records are retained for financial and fraud-control needs. “Clear package” terminates the worker, revokes local file URLs, and removes the in-memory index. It preserves the free-use count and any license you deliberately attached.
Important boundary
This version is not presented for controlled attachments, FCI, CUI, or classified material. Use only files you are authorized to process.