logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • API
HTPBE?

Structural PDF tamper detection API. Catches edits your KYC stack misses.

đŸ‡«đŸ‡ź Made in Finland

Product

  • How It Works
  • Why It Matters
  • Use Cases
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.14.0

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875

Status

Algorithm v2.14.0

Back to FAQ
FAQ

Does the PDF checker read my document content?

No, our PDF authenticity checker does not read or store your document content. While we temporarily load the PDF file into memory for technical analysis, we only examine file structure, metadata, and PDF formatting information—never extracting or reading the actual text, images, or content within your PDF files.

This privacy-focused approach means sensitive documents remain completely confidential. The PDF tamper detection process examines file structure, creation/modification dates, creator/producer information, digital signatures, and structural elements like xref tables and incremental updates.

We extract metadata such as filename, file size, page count, and PDF version, but never access or extract document content. This makes our PDF modification detection service safe for confidential documents including contracts, financial statements, personal records, and proprietary information. Your document content is never read, extracted, or stored—only technical metadata and structural information that helps determine PDF authenticity.

← Previous

What is the difference between Creator and Producer in PDF metadata?

Next →

What are incremental updates in PDF and why do they matter?

Related questions

Keep reading

3 answers

What are incremental updates in PDF and why do they matter?

→

Can a PDF be modified without detection?

→

How should I interpret PDF analysis results?

→