What does Arkova actually do?

Arkova creates a permanent, independently verifiable proof of any credential or document. It anchors a tamper-evident fingerprint of the file to a public network, so anyone can later confirm the issuer, the timing, and the integrity — without Arkova ever holding the file.

Do you store my documents?

No. Fingerprinting happens in your browser; only the SHA-256 fingerprint and minimal metadata ever leave your device. Even if we were breached, your documents stay private — because we never had them.

What does "tamper-evident" actually mean?

If a single byte of the original document changes, its fingerprint no longer matches the anchored one and verification fails. Integrity is provable by mathematics, not asserted by us.

What happens if Arkova goes away?

The proof outlives us. Because the fingerprint is anchored to a public network, a record stays independently verifiable even if Arkova's servers are offline or the platform that issued it shuts down.

How does someone verify a record?

Every record has a public ID. Anyone can look it up — on the Verify page or with a single API call — to see the issuer, the anchor time, and the tamper-evident status. No account, and no access to the original file, required.

Can I integrate it with my systems?

Yes. A REST API (single-call and batch), HMAC-signed webhooks, and direct anchoring from sources like DocuSign plug into the SIS, LMS, HRIS, and ATS stacks you already run — with a full audit trail of every call.

The verification layer runs in production today; the full product is in early access. Join the waitlist and we will reach out to scope a pilot.