Privacy & Security
Document Content
PDFs, tables, screenshots, redaction regions, and pseudonym keys are processed on your device. There are no document upload endpoints, analytics integrations, external OCR services, or content telemetry. Clear the queue or close the tab to release application references. Browsers and operating systems may retain memory temporarily; secure memory erasure is not guaranteed.
Website Requests
Your browser requests application pages and self-hosted processing assets. The hosting server or CDN may see your IP address, requested URL, user agent, and request time in ordinary access logs. Document content and filenames are not placed in these requests. This is not a promise of anonymous browsing or zero network traffic.
Site Administration
Separate site-administration features use authentication cookies and store site content, administrator session token digests, and management audit records on the server. These records do not include visitors' input documents. Administration pages and API responses are excluded from the offline document-processing cache.
Offline Storage
The optional offline package stores application code, fonts and five OCR language models in browser Cache Storage, not input documents or outputs. Saved rule templates use localStorage and contain rule settings, not source values, regions, keywords or pseudonym keys. Template names are stored locally; avoid confidential names. Delete templates in the editor or clear browser site data. Storage pressure or browser updates may evict cached assets.
Export Verification
PDF exports are reparsed to check text extraction, decoded streams, metadata and unsafe document structures. Failed checks block the download. Checks only assess the provided regions and known patterns. Manual regions can cover only part of an identifier; OCR and detection can miss text. Always visually review the exported document in an independent viewer.
Output Names
Export filenames retain the source filename with a prefix. Rename downloaded files before sharing if the original filename contains personal or confidential information.
Compliance Limits
This software is not certified for GDPR, HIPAA, SOC 2, or PCI DSS. Local processing does not establish compliance or eliminate re-identification risk. Masking leaves fragments, keyed pseudonyms retain relationships, and table headers remain visible. Consult your organization's policies before sharing information.
Optional Team Accounts and Billing
Workspace accounts store account names, email addresses, password hashes or SSO identities, organizations and roles. Explicit review submissions send only source/output SHA-256 hashes, file type, output size, region count and signed decisions. Documents, extracted text, filenames and region coordinates are not uploaded. Workspace uses a session cookie and is excluded from offline caching. Configured billing uses Stripe Checkout and configured SSO uses the organization identity provider. Signed audit records persist for organizational accountability; they are not a promise of legal certification.