PDF files

Submitted PDF files are used to perform conversion. Inspected bytes are staged under a random ID in private temporary object storage. Their signed conversion URL expires after 15 minutes. We request deletion immediately after a definite provider outcome; interrupted or ambiguous copies are eligible for a bounded cleanup job that runs every five minutes after their expiry. Storage lifecycle rules provide a backup. Physical deletion can lag logical expiry and cleanup requests.

For signed-in conversions, an immutable private draft remains usable for 30 minutes, including while completing a purchase when Checkout is available. Starting conversion creates a separate temporary OCR copy with a signed URL valid for up to 15 minutes. Expired draft sources are removed by bounded cleanup; physical deletion can lag expiry. Successful account conversion responses, including Markdown, can be replayed for 24 hours without charging again. Access then expires; stored copies are removed by bounded cleanup and storage lifecycle rules, so physical deletion can occur later. Billing receipts and credit movements are retained separately from document content for accounting and payment reconciliation.

Markdown output

Converted Markdown is returned in the API response. Successful account responses are stored temporarily for the replay period described above. Do not rely on pdfToMarkdown as document storage.

Usage metadata

We retain usage metadata needed for quotas, rate limiting, abuse prevention, debugging, and product analytics. This can include API key, tier, page count, status code, source IP, timestamp, request latency, and error code.

GitHub OAuth data

For Developer keys, we retain the GitHub account ID, login, optional profile fields returned by GitHub, API key metadata, quota, and account timestamps.

Deletion requests

To request deletion of account or usage metadata, contact privacy@pdftomarkdown.dev. Some operational records may be retained where required for security, abuse prevention, or legal obligations.