How are sensitive documents handled?

Promvel PDF leads with local-first handling. In regulated local-compute mode, PDFs are processed in your browser, on your direct console host, or in infrastructure you control, while the cloud control plane is intended to store only the metadata needed for authentication, orchestration, quotas, and audit records.

Are PDF contents stored in the cloud?

In regulated local-compute mode, cloud endpoints are intended to receive metadata only, not raw PDF bytes, extracted text, or filled form values. If you choose a deployment that sends files to remote infrastructure, that changes the data-handling posture and should be reviewed explicitly.

Why does deployment mode matter for privacy?

The same product can run with different data-plane configurations. Browser-local processing keeps PDFs on-device, a direct console host keeps them within your controlled environment, and a managed remote service has a different privacy boundary, so deployment mode has to stay explicit.

Promvel

Privacy-first processing

How local PDF Processing Works

Q: What metadata may be stored?

Typical records include account identifiers, tenant-scoped job state, usage counters, billing references, worker lease details, and sanitized progress events. The system is designed to avoid sending raw field values or document contents into logs or cloud events.

Promvel PDF keeps document processing local first. This page shows what stays on your device, what metadata may be stored for orchestration, and which deployment choices change that boundary.

See agent workflows Read privacy details

Document processing stays local

PDFs and structured inputs are processed in your browser or controlled infrastructure.

The control plane handles access and orchestration

Authentication, tenant scope, worker state, and job tracking help coordinate work without storing document contents.

Operational events stay sanitized

Progress events are designed to store safe metadata, not raw PDFs, extracted text, or filled form values.

What happens when you start a workflow

Promvel PDF separates document processing from orchestration so you can review where files move, what metadata is retained, and whether your deployment matches the privacy posture you expect before handling sensitive documents.

Authentication and tenant boundaries

User accounts, worker identity, short-lived tokens, and tenant scoping help isolate each request.

Job tracking and quotas

Jobs move through tracked states with usage counters and timing data for reliable orchestration.

Sanitized audit and progress events

Audit and progress events carry operational context without storing document contents.

undefined

How to evaluate your privacy posture

Confirm where document processing runs and verify that operational logs stay metadata-only before handling regulated files.

The strongest safe privacy claim depends on how your deployment handles the data plane. Review the operating mode before moving regulated or sensitive documents into production.

Confirm whether processing runs locally in-browser, on a direct console host, or through remote infrastructure.

Review retention, logging, and storage settings before handling regulated documents.

Use managed accounts, trusted devices, HTTPS, and tenant-scoped access controls.

Check your logging pipeline to ensure events remain sanitized end to end.