Last updated: June 11, 2026

Service overview

pdfToMarkdown is a server-side PDF to Markdown API. When you submit a PDF URL or base64-encoded PDF, the request is handled by a Cloudflare Worker and forwarded to a RunPod GPU worker for OCR and conversion.

Document content

PDF files and OCR output are processed to return the API response. We do not intentionally store submitted PDF files or converted Markdown as customer document records. Processing may involve transient runtime memory, temporary files inside the OCR worker, and infrastructure logs needed to operate and debug the service.

Account and API data

If you sign in with GitHub, we store the GitHub account ID, login, optional name, optional email, avatar URL, API key metadata, quota, and timestamps needed to issue and manage your developer key.

Usage logs

We log API usage metadata such as API key, tier, processed page count, status code, source IP, and timestamp. These logs help enforce quotas, diagnose reliability issues, and understand product usage. We do not need document text in analytics events.

Analytics

We use PostHog to measure website and API usage, including page views, CTA clicks, OAuth flow events, API request status, latency, and error codes. Analytics events must not include PDF content or converted Markdown.

Third-party processors

The service currently uses Cloudflare for edge hosting, routing, storage, and database infrastructure; RunPod for GPU OCR execution; GitHub for OAuth; and PostHog for analytics.

Your choices

You can avoid GitHub login by using the public demo key, subject to its limits. You can request account or usage-data deletion by contacting privacy@pdftomarkdown.dev.

Contact

For privacy questions, contact privacy@pdftomarkdown.dev.