Anyone can check a document in seconds
A counterparty, a bank or a court does not need an account to trust your document. They scan the QR code, or drop the PDF into the verifier.
A QR code on every certificate
The certificate of completion of each signed document has a QR code and a short link such as verify.sign.yt/k3Fq9ZxT2mPa7LwB. It opens a public page showing the document status, how many signatures were collected and when, the hash of the signed original, the platform seal, the post-quantum seal and the Bitcoin anchor.
The page uses the branding of the organization that sent the document.
Check that your file is identical
The QR code proves the document exists in sign.yt. To prove your copy is unchanged, upload it on the same page: its hash is compared with the hash of the signed original, and the full signature report is shown next to it.
No personal data in public
Signer names are masked, for example "J. K*****", and no emails, phone numbers or IP addresses are shown. The link is a long random code that cannot be guessed, and lookups are rate-limited.
Any PDF, signed with sign.yt or not, can also be dropped into the verifier to see whether its signatures are intact.
Frequently asked questions
Does the person checking need an account?
No. Both the QR page and the PDF verifier are public.
What does the public page reveal?
Status, masked signer names with signing dates, the final hash and the seal and anchor status. Not the content of the document.
Can the links use my own domain?
By default they point to verify.sign.yt. Moving them to your domain is part of the paid Full customization add-on.
More features
- Profil Zaufany and qualified signatures
Let Polish signers use Profil Zaufany, e-dowód or mObywatel via Węzeł Podpisu, or sign with a qualified electronic signature from a trust service provider.
- Audit trail
Every action is logged in an append-only, hash-chained audit log. Signatures are chained per document and a certificate of completion is added to each PDF.
- GDPR compliance
Data export and erasure requests handled in the product, PDFs encrypted at rest with a separate key per organization, and strict tenant isolation.