How are documents stored?

ANANKE Trust generates a cryptographically protected PDF for each document and stores it in encrypted, organization-isolated infrastructure. A fingerprint (hash) is anchored to the blockchain. The protected PDF is delivered to recipients by email.

Who can verify documents?

Anyone with an ANANKE LABS account can verify documents through the web application or mobile app. Verification is also available via the Integration API for automated workflows. The issuer controls what information verifiers see — not who can verify.

What data do we store?

We store the protected PDF, issuance metadata, lifecycle status, templates, and audit trail entries. All stored data is encrypted and organization-isolated. Only cryptographic fingerprints are published externally to the blockchain — no personal data.

How long does verification take?

Typically under a few seconds. Verifiers get a clear result: authentic and current, or not.

Can we revoke a document after issuing it?

Yes. You can suspend, revoke, replace, or reactivate any document at any time through the web application or API. The updated status is reflected immediately for all future verifications.

What volume can the platform handle?

ANANKE Trust supports single ad-hoc issuance, template-based workflows, and bulk issuance from CSV with per-row tracking. Built for institutional scale.

Is this the same as a digital signature?

ANANKE Trust provides verification evidence and lifecycle assurance — complementary to digital signatures. For legally qualified electronic signatures (eIDAS/DGSSI), ANANKE Sign is a separate planned product.

Core product

Make any document verifiable, tamper-proof, and audit-ready.

ANANKE Trust lets your organization issue digital documents that anyone with an ANANKE LABS account can verify independently — confirming they are authentic, unchanged, and current. No phone calls, no email chains, no manual checks.

Get in touch See the university workflow

Challenge

The problem we solve

Today, when someone receives a diploma, a certificate, or an official document, there is no reliable way to verify it. Employers call registrar offices. Embassies request apostilles. HR teams waste days confirming that a PDF has not been altered.

5–15 days

Average time to verify a credential manually

100s

Of staff-hours spent on verification calls each year

Growing

Document fraud across borders and institutions

Zero

Standard way to prove a PDF has not been altered

ANANKE Trust replaces this with fast, independent verification — backed by proof, not promises.

Capabilities

What ANANKE Trust does for your organization

Key capabilities that transform how your documents are trusted across organizations and borders.

Prove authenticity instantly

Any verified ANANKE LABS user can confirm that a document is real, issued by your organization, and has not been tampered with — in seconds, not days.

Detect tampering automatically

If someone modifies even a single character in a document after issuance, the system flags it immediately. No manual checks needed.

Track lifecycle changes

Revoked a certificate? Replaced a credential? Verifiers always see the current status — not a stale snapshot from months ago. Suspend, revoke, reactivate, or replace at any time.

Deliver protected documents securely

Recipients receive a cryptographically protected PDF by email. The document carries built-in proof that can be independently verified.

Build a defensible audit trail

Every issuance, verification, and status change is recorded with timestamps. If a dispute arises, you have evidence that holds up.

Issue at institutional scale

Issue single documents ad hoc, use templates for recurring types, or process thousands at once via CSV bulk upload with per-row tracking.

Trust Guarantees

What every document proves

When you issue a document through ANANKE Trust, any verified user can confirm all of these independently.

"This document exists"

Existence

Confirm that a specific document was created at a specific point in time with issuer-backed evidence.

"Nothing has been changed"

Integrity

Detect any modification to the original content, no matter how small. Even a single character change breaks the cryptographic fingerprint.

"We issued this"

Origin

Verify exactly which organization created this document, through the cryptographic protection bound to the issuing entity.

"Here is the chain of events"

Audit trail

Every action — issuance, status change, verification — is recorded with timestamps and actor identity. Defensible evidence if a dispute arises.

"This was created at exactly this time"

Timestamp

Dispute-resilient issuance timestamps tied to the verification record.

"This is still valid" or "This was revoked"

Lifecycle

Always know the current status. If a credential was suspended, revoked, replaced, or reactivated, the status reflects it immediately.

Workflow

How it works

Four steps from issuance to verification.

Create your documents

Issue a single document, select a template for a recurring type, or upload a CSV for bulk issuance. Use the ANANKE web application or connect your systems through the Integration API.

Automatic protection and anchoring

ANANKE Trust automatically applies verification protection and optional external evidence. No personal data is published externally.

Recipients get their protected PDF

Each recipient receives a protected PDF by email. The document carries built-in verification evidence that can be independently checked.

Manage over time

Suspend, revoke, replace, or reactivate the status of any document through the web application or API. Verifiers always see the current state. Your audit trail is maintained automatically.

Live Preview

See how a document is issued through the Trust platform.

Verification

How verification works

Anyone with an ANANKE LABS account can verify documents. Issuers control what information verifiers see.

Web application

Upload a PDF in the ANANKE web application. Get an instant result with full status and details. Available to any authenticated ANANKE LABS user.

Mobile app

The ANANKE Mobile app is built primarily for T-CODE scan and verification. It also supports uploading a Trust-issued PDF directly for verification, giving you full flexibility wherever you are.

Integration API

Integrate verification into your own systems via the API. Automate checks as part of your onboarding, compliance, or audit workflows. Full documentation at docs.anankelabs.net.

What verifiers see

Verifiers receive a clear, human-readable result — not raw data. The issuer controls which fields are visible.

Verdict

Authentic and valid, or not — with a clear explanation

Issuer identity

The organization that issued the document, verified independently

Document status

Active, suspended, revoked, or replaced — always current

Issuance date

When the document was created and recorded in the verification timeline

Approved fields

Only the metadata the issuer chose to share (e.g., document type, recipient name)

Audit trail

Lifecycle events — when status changed and why

Verification in action

See both web and mobile verification workflows.

Use Cases

Who is ANANKE Trust for?

Any organization that issues documents others need to trust.

MVP

Universities

Issue diplomas, transcripts, and certificates that can be verified in seconds — without employers calling your registrar office.

See how it works

Research

Banking & Finance

KYC documents, account confirmations, and compliance attestations with full audit trails and cryptographic proof.

Discuss your use case

Research

Enterprise

Vendor onboarding packets, contract authenticity, and compliance documentation that travels with verifiable proof.

Discuss your use case

Research

Public Sector

Citizen service documents, permits, and regulatory submissions with verifiable accountability trails.

Discuss your use case

Security

Security and data handling

ANANKE Trust is built for organizations that handle sensitive documents. Here is how we protect your data:

Only cryptographic fingerprints are published to the blockchain — no document content, no personal data

Protected PDFs are stored in encrypted, organization-isolated infrastructure with industry-standard encryption

Cryptographic keys are managed in hardware security modules — never in application code or databases

Strict organization isolation: each organization's data, proofs, and configuration are fully separated

You control what fields verifiers see — verification reveals only what is needed to confirm authenticity

Full audit trail records actions and actors, not document content

FAQ

ANANKE Trust FAQs

Ready to make your documents verifiable?

We are building the infrastructure to replace manual verification with cryptographic proof and full lifecycle management. Contact our team to discuss your use case.