Your documents are examined, not warehoused.

Temporary processing, no document archive

Originals, sensitive derivatives and reports stay in private memory storage. They are not written to the operational database, a document bucket or a research corpus. New examinations require a working processing path and cleanup controller. Uploads pause if those operational checks fail.

Upload and examination

You choose a PDF in your browser and submit it through an authenticated account or API key. Examinations use the shared DWS forensic engine. The current deployment runs deterministic forensic tools locally in a Cloudflare container restricted to the United States. It does not invoke an external AI provider. Reports disclose checks that ran, checks that were unavailable and that AI examination was not invoked.

Originals and sensitive derivatives are removed after processing, including failed or canceled jobs, with a maximum source age of one hour from initial server ingestion. Processing stops at that deadline. The processing environment uses private memory storage, no swap, disabled core dumps and a read-only root filesystem. Document-content logging and memory snapshots are disabled.

Reports and deletion

Reports remain in the same temporary memory storage for at most 24 hours from report creation. A restart can make them unavailable earlier, so download any report you need to keep. Account ownership is checked before report access; downloads are private and must not be cached. The document controls provide a deletion request. A request is distinct from verified completion: failed upstream cleanup remains pending and must be surfaced to operators.

Reports contain findings, evidence and document metadata. Downloaded files, recipient mailboxes and copies retained on your own devices are outside our deletion controls. We do not send examination reports as email attachments. A locally selected, unsubmitted file may remain in browser storage through sign-in; browser cleanup cannot run while that browser is closed. Clear site data to remove that selection.

Operational records

Account identities, payment and subscription references, credit transactions, job identifiers, outcomes, timestamps and cleanup states are retained separately for service operation and applicable legal or accounting needs. They are not document storage. These records may be backed up. Document text, filenames, prompts, report contents and sensitive request bodies are excluded from the operational database and application logs. Hosting request metadata, such as request times and response status, is distinct from document content.

Limits of deletion and security claims

Application deletion does not prove immediate physical erasure from provider media. Our controls cover this application and its configured processing path; they are not a promise of immediate physical erasure from all provider hardware. We do not claim SOC 2 certification, HIPAA compliance, verified encryption at rest, or a verified no-training arrangement for every upstream processor.