Sovereignty Model

A signature system that depends on a single company is a contradiction. If the company disappears, so does every signature it ever produced. Mark is built on the opposite premise: every proof artifact must be independently verifiable using only public infrastructure.

We never hold your private keys. Keys are generated on your device (or YubiKey) and never leave it.

We do hold:

• Verification code mappings — short codes that point to signed bundles. These expire and are a convenience layer.
• Signing request metadata — when you use co-signing, we temporarily store the envelope. Encrypted at rest, deleted after completion.
• Push notification tokens — for co-signing notifications. No message content.

Everything else lives on your device or on-chain.

1. With Mark — Enter the verification code at mark.noblestar.tech/verify. Easiest path.
2. With the file — The signed bundle is a self-contained JSON file. Drop it into any Mark-compatible verifier. No server needed.
3. From the chain — Query the Polygon blockchain directly for SignatureBundlePublished events by document hash. Zero Mark dependency. Works with any Ethereum-compatible tool (Etherscan, cast, ethers.js).

If Noblestar disappears tomorrow:

• Your keys still work — they are on your device.
• Your identity record is on the Polygon blockchain — anyone can read it from any node.
• Your signed bundles are also on-chain — published to the MarkSignatureBundleRegistry contract.
• Your on-chain service records are permanent and readable by design.
• Verification codes stop working — but the underlying proofs do not.

The only thing lost is the convenience layer. The cryptographic proof survives.

The Mark Signing Protocol specification is open. The verification logic is open source. Anyone can build a compatible client, verifier, or relay. The protocol is the product — the app is one implementation.