Skip to main content

Security & Data Handling

Use this page to understand how Doqlo handles document processing, where data is temporary, and which security responsibilities stay on your side.

Overview​

Doqlo is designed to minimize long-term document retention. Editing happens in the browser by default, while export and delivery use limited server-side processing only where the current product requires it.

This page is a product-facing explanation of current behavior. It is not a legal policy replacement.

How Data Is Handled​

  • Signature placement, text overlays, date overlays, and PDF editing actions happen in your browser.
  • During export, your document may be temporarily transmitted to Doqlo servers so the final output can be generated.
  • Ordinary supported Sign and Bulk Fill PDFs stay in the browser during admission. If either product offers compatibility conversion, the selected PDF is transmitted only after you explicitly choose Create and continue and sign in. The authenticated conversion path processes the source and compatible output only for that request. Bounded, access-restricted reverse-proxy and native-tool temporary buffers may be used and are cleaned on terminal paths. Neither file is retained as repository data, included in application backups, or made available for later retrieval.
  • A conversion candidate is not opened or saved as a local draft unless the returned compatible PDF passes browser validation. Cancelling or a failed conversion leaves the candidate out of draft storage.
  • PDFs that require a password to open and dynamic XFA PDFs are not sent for automatic conversion. Doqlo instead explains how to create and upload a compatible copy manually. Passwords are not collected or transmitted.
  • When Bulk Fill offers Download current PDF in Batch Export, selecting it sends the admitted working PDF and saved page organization through a separate authenticated, rate-limited request. The source and result are processed for that request only, returned directly with no-store caching, and are not retained as a document, job, reusable URL, or recovery copy. This action is independent from the normal batch export.
  • Doqlo is not a long-term document repository. Source PDFs and exported outputs are not offered as an archive or recovery service.
  • For Bulk Fill delivery, generated output artifacts may be held temporarily so a requested download can complete through Doqlo-controlled delivery.
  • Current application-level delivery validity is capped at about 6 hours, with cleanup managed under a 24-hour hard backstop.

Because temporary delivery artifacts are short-lived and access-limited, you should download and store the files you need on your own systems.

.doqlo Project File Custody​

Current v5 .doqlo files are sealed reusable configuration. They do not contain CSV text, rows, headers, preview values, or the CSV filename. They may contain intentional static field values, typed Signature text and metadata, bounded processed PNG data for placed drawn or uploaded-image signatures, and diagnostic source PDF metadata such as its filename, page count, and fingerprint. They do not contain source PDF bytes.

Accepted older v1 through v4 project files may contain the complete CSV data and original filename that were loaded when the file was saved. Opening and re-saving an accepted older project creates v5 without that embedded CSV data. Until then, protect and share the older file as you would protect the source dataset.

Project files are downloaded to storage you control. They are not temporary Cloud Delivery artifacts and do not inherit the 6-hour delivery window. Doqlo processes manual Save Project and Open Project payloads in server memory for the request and does not offer project files as a server-side archive.

Security Basics​

  • Account access is tied to authenticated Doqlo accounts. Available sign-in options can include Google and Microsoft, depending on configuration.
  • Public API access uses BF export API keys. Keep keys on the server side and revoke or rotate them if you believe a secret was exposed.
  • Webhook integrations should verify Doqlo signatures before trusting the payload.
  • Temporary delivery access is application-controlled and time-limited rather than a public long-term file-hosting feature.
  • Public API and webhook integrations are intended for HTTPS-based transport.

Your Responsibilities​

  • Upload only documents and data you are authorized to process.
  • Protect your account access, billing access, and any API credentials.
  • Review exported output for correctness before you rely on it in your own business process.
  • Secure your own webhook endpoint, infrastructure, and downstream systems.
  • Avoid sending sensitive or confidential documents to support unless they are necessary for the issue you are reporting.