Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.blinkpdf.io/llms.txt

Use this file to discover all available pages before exploring further.

When you send a document to Blink PDF, it is processed entirely in memory and discarded the moment your PDF is returned. Nothing you submit is written to a database, logged to disk, or retained beyond the lifecycle of a single API request.

​
What zero-retention means

“Processed in memory. Never stored on disk. Never used to train models.”
Zero-retention is a hard architectural guarantee, not a configurable policy. The rendering pipeline is stateless by design:
  1. Your request arrives and is held in memory for the duration of the render.
  2. The PDF is generated and streamed back to you.
  3. The request payload — including all Markdown content, metadata, and any intermediate document state — is immediately purged from memory.
No background job, no async flush, no eventual-consistency delay. When the response closes, your data is gone.
“Purged immediately” means within the same request lifecycle. Blink PDF does not use write-ahead logs, render queues, or persistent buffers that could retain content after the response is sent.

​
What is NOT stored

The following data is never written to disk, database, or any persistent store:
  • Markdown content — the document text you send in the request body
  • Generated PDFs — the binary output is streamed directly to you and not cached
  • PDF metadata — titles, authors, and custom fields you pass in the metadata field
  • Document structure — headings, tables, images, and any intermediate parse tree
  • Image content — remote images fetched during rendering are held in memory only and discarded immediately after use

​
What IS stored

Blink PDF does retain a minimal set of account-level data necessary to operate the service:
Data typeStored?Purpose
Account email & credentials✅Authentication
API keys (hashed)✅Request authorization
Usage counters (request count, byte totals)✅Billing and rate limiting
Markdown content❌—
Generated PDFs❌—
PDF metadata fields❌—
Usage counters record that a request was made and how large it was — not what was in it. Your document content never touches the billing subsystem.

​
Zero model training

Your data is never used to train, fine-tune, or evaluate any machine learning model — Blink PDF’s own or any third party’s. The rendering engine is deterministic software, not a learned model, and it has no feedback loop that ingests document content.
If you work in a regulated industry and need to document this guarantee for an audit, the zero-retention policy is stated in the Blink PDF Terms of Service and Data Processing Addendum (DPA). Reach out to support to request a signed DPA for your records.

​
Why this matters for regulated industries

Industries with strict data-handling requirements — legal, medical, financial services, government — often cannot send document content to third-party services that log or store it, even temporarily. Zero-retention removes that blocker:
  • Legal — draft contracts, briefs, and privileged correspondence can be rendered without leaving your control boundary.
  • Medical — patient-facing documents (discharge summaries, lab results) containing PHI can be generated without triggering a HIPAA logging concern.
  • Finance — trade confirmations, account statements, and KYC documents can be formatted as PDFs without exposing sensitive figures to a third-party data store.
SOC 2 Type II certification is on the Blink PDF roadmap. If SOC 2 compliance is a hard requirement for your procurement process, contact the team to discuss your timeline and to receive updates when certification is available.

Markdown Rendering

See how the stateless in-memory rendering pipeline works end to end.

Accessibility

Learn about PDF/UA-1 compliance, Unicode support, and color emoji.