How long are analysis results stored?

Yes, and this is an important limitation to understand. Our PDF authenticity checker detects modifications to existing PDF files—we cannot determine if a brand-new PDF was created with falsified content.

Example scenario: Someone could:

• Create a fake invoice or certificate with false information
• Print or export it as a fresh PDF file
• The PDF will appear as “not modified” because it’s technically a new file, not a modified existing one

How to protect yourself: Always pay close attention to the Creation Date shown in the analysis results. Ask yourself:

• Does the creation date make logical sense for this document?
• If it’s supposedly a 2020 invoice, why was the PDF created in 2026?
• Is the creation date suspiciously recent for an “old” document?
• Does the timeline match the situation and claimed document origin?

Additional fraud detection steps for critical documents:

• Request the original file from the issuing organization directly
• Check document details with the claimed issuer (company, institution, authority)
• Check for official digital signatures or stamps
• Compare document format and layout with known authentic samples
• For scanned documents (photos of documents), request the original digital file instead

Our service is a powerful tool for detecting tampering with existing files, but it cannot replace human judgment and thorough fraud detection processes. The creation date is your first line of defense against completely fabricated documents.

No, you cannot view or download your original PDF file from the results page. The results page displays only the analysis metadata and findings—not the document itself.

This is a deliberate privacy and security feature. The results page never exposes the original document, so no one who holds a shared result link can retrieve the underlying PDF. Where a web-uploaded file is retained, it is used only in anonymized form to improve our detection algorithm, as described in our privacy policy; files submitted through the API are never stored.

The results page shows comprehensive analysis information including:

• Modification status (modified/not modified)
• Modification verdict and specific findings
• Metadata (creation date, modification date, creator, producer)
• Structural findings (incremental updates, signatures, etc.)
• Specific anomalies detected

Keep your original PDF file: If you need to reference the actual document later, make sure to keep a copy on your local device. The analysis results are permanent, but access to the original file is not.

This policy protects user privacy by ensuring uploaded documents are not accessible to others through shared result links, even if the link is compromised.

All dates and times on HTPBE? are displayed in UTC (Coordinated Universal Time) for consistency, accuracy, and transparency. This is an intentional design choice to ensure everyone sees the same absolute time regardless of their location.

What is UTC?

UTC is the global time standard used worldwide. It’s equivalent to GMT (Greenwich Mean Time) and serves as the reference point for all timezones. Unlike local time, UTC never changes with daylight saving time or regional adjustments.

Why We Use UTC:

• Universal consistency: Everyone sees the exact same timestamp regardless of their location or timezone
• No timezone confusion: A document created “at 14:00” could mean different absolute times in New York vs Tokyo. UTC eliminates this ambiguity
• Technical accuracy: PDF files internally store timestamps in UTC. Displaying them in UTC preserves the original data without conversion errors
• International collaboration: When sharing results with people in different countries, UTC provides a common reference point
• Audit trail integrity: For legal and compliance purposes, UTC timestamps create unambiguous records

How to Convert UTC to Your Local Time:

If you need to know what time something was in your timezone:

• Google search: Type “14:00 UTC in [your timezone]” to get instant conversion
• Mental calculation: Add your UTC offset. For example, if you’re in New York (UTC-5), subtract 5 hours from UTC time
• Time converter tools: Many free online tools convert UTC to any timezone

Common UTC Offsets:

• New York: UTC-5 (or UTC-4 during daylight saving)
• London: UTC+0 (or UTC+1 during summer time)
• Paris/Berlin: UTC+1 (or UTC+2 during summer time)
• Dubai: UTC+4
• Singapore/Hong Kong: UTC+8
• Tokyo: UTC+9
• Sydney: UTC+10 (or UTC+11 during daylight saving)

What This Means for You:

When you see a timestamp like “12.02.2026 09:35:21 UTC” on HTPBE?:

• This is the absolute, universal time the event occurred
• It’s the same timestamp everyone else sees, regardless of their location
• You can convert it to your local time if needed, but the UTC value is the authoritative record

Example Scenario:

You upload a PDF at 3:00 PM in New York (UTC-5). The check date shows “20:00 UTC” because:

• 3:00 PM in New York = 15:00 in 12-hour format
• 15:00 - 5 hours offset = 20:00 UTC

Someone viewing the same result in Tokyo (UTC+9) also sees “20:00 UTC”, not their local time. This ensures consistency and prevents confusion.

Bottom Line:

UTC display may seem unusual if you’re used to seeing local times, but it’s the professional standard for global systems. It ensures accuracy, eliminates timezone-related errors, and provides a reliable foundation for document fraud detection timestamps.