FAQ

Straight answers about hashes, proofs, and Hedera.

What does OwlVerify store?
Cryptographic hashes, proof metadata, and what’s needed to verify later. We’re not silently putting your full file on a public ledger.
Does OwlVerify put my file on-chain?
No. The hash and proof record are anchored to Hedera—not your raw document or payload as published content on the ledger.
What is a cryptographic hash?
A fixed fingerprint of your data. Same content → same hash. Change a single bit → a different hash. That’s how verification knows if something changed.
Why use Hedera?
It’s a public ledger that can record low-cost, timestamped transactions. OwlVerify uses it so proof anchors exist outside your infrastructure—useful when you want an independent reference point.
Can I verify a file later?
Yes. Submit content again and OwlVerify compares it to the proof you recorded. You get a match or mismatch—not a vague “maybe.”
What kinds of content can OwlVerify support?
Anything you can treat as a file or byte sequence: PDFs, media, exports, AI outputs, archives, and more—as long as you can hash it consistently.
Is this for developers only?
Builders get the most out of the API and automation paths. Product and operations folks can still use the console for uploads and checks.
Does OwlVerify guarantee compliance?
No product replaces your policies, contracts, or regulators. OwlVerify gives technical integrity proof; your compliance story is still yours to own.