A corridor you can verify

Accounts are secured with WebAuthn passkeys — there are no passwords to phish, guess or leak. The private key is generated by your device's authenticator and never leaves it.

Your first device is the seed. Additional devices each register their own passkey by scanning a short-lived QR linking code, so every device holds a distinct credential.

Passkeys require a secure (HTTPS) context and are bound to this site's domain, making them resistant to phishing and man-in-the-middle attacks.

Real-world identity is confirmed through Nafath, the Saudi national single sign-on. Only an identified account can open the Vault, Tunnel, Concierge and Signing tools.

Collaborators who open a shared document must also pass Nafath, and every read is written to a tamper-evident audit log.

In this prototype Nafath is deliberately stubbed with a clearly-labelled lookalike; production swaps it for the real Nafath OIDC integration.

Every Vault document is encrypted with AES-256-GCM before it touches storage. Only the ciphertext is persisted; the plaintext exists only transiently while you upload or download.

Each document is fingerprinted with SHA-256 so you can cryptographically compare files and prove two documents are byte-for-byte identical.

Document versions form a hash chain: each version commits to the previous version's hash, exactly like the Previous Invoice Hash used in ZATCA e-Invoicing Phase 2.

Altering any earlier version breaks every later hash, so the full history is tamper-evident and independently verifiable.

Redis bridges the web app and the Tunnel with disk persistence disabled — challenges, linking codes and session data live only in memory and expire automatically.

The WireGuard Tunnel runs in RAM mode with no traffic logging. Sessions are capped at 1 Mbps and the peer pool is self-healing.

The signing tool wraps your document in a PDF container with a certificate page recording the signer, date, time, location and a webcam photo of the signing party.

The certificate embeds the SHA-256 of the original bytes, binding the signature to the exact document that was signed.