Completed PDF
The completed fields are added to a final PDF and the finished file is protected against unnoticed changes.
Trust & evidence
Keep the completed PDF and signing certificate together, then verify whether a saved copy matches LulaSign’s record.

The completed record
Public verification gives a limited result. Detailed signing activity is reserved for authorised workspace users.
The completed fields are added to a final PDF and the finished file is protected against unnoticed changes.
A readable certificate summarises the documents, participants, completion time and verification reference.
A code opens the completion record. You can also upload the final PDF to check that it matches the file LulaSign recorded.
The original documents, completed PDF, certificate and important signing events stay connected.
Public verification shows what is needed to check a document. Detailed personal and activity information is restricted.
Who sees what
Anyone holding the PDF or its verification code can confirm it is genuine. The detail stays with the people in your workspace.
How it is protected
The safeguards behind the completed record, in plain terms.
LulaSign records a SHA-256 fingerprint of each completed PDF. Change a single character and the fingerprint no longer matches, so an altered copy shows up as a mismatch.
The standard file check calculates the fingerprint on your own device and sends only that, so the document itself never has to leave your computer.
Every recipient gets their own secure link, optionally guarded by a one-time code by email, SMS or WhatsApp. A link sent to the wrong place can be revoked and replaced.
Who was invited, who opened, signed or declined, and when, stays with the request. Authorised workspace users can review it; the public check shows only what is needed.
Workspace users can protect their account with an authenticator app and recovery codes, and each person signs in with their own login and role.
LulaSign staff need two-step sign-in and a fresh check before sensitive actions, their access is recorded, and it never gives them ownership of your workspace.
Document verification
The code on the completed PDF or certificate opens the LulaSign record. Uploading the PDF goes one step further and checks whether the file still matches the one completed through LulaSign.
The seal on the PDF
LulaSign certifies every completed PDF with a digital seal of its own: a PAdES certification signature that allows no changes. Open the file in Adobe Acrobat or another PDF reader and its signature panel shows the seal.
Until you trust that certificate, a reader may call the seal “unknown” or “not trusted”. That is about who made it, not about the document. Read why, and how to trust it.
Honest limits
LulaSign supports ordinary electronic-signature workflows. It does not claim that every South African transaction can use the same method.
See what LulaSign collects, why it is used and how to raise a request.
Read the privacy noticeUnderstand how long completed files remain available and which essential records may be kept longer.
Read the retention policyLearn where ordinary electronic signatures may fit and where extra care is needed.
Read the guideLulaSign · Simply sign.