Data Retention

What pdfToMarkdown retains after document conversion requests.

PDF files

Submitted PDF files are used to perform conversion. We do not intentionally keep PDF files as customer document records after processing. The OCR worker may use temporary files during conversion, and infrastructure providers may retain operational logs according to their own systems.

Markdown output

Converted Markdown is returned in the API response. We do not intentionally store converted Markdown as a product record. 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.