Signed Document Policy

docrud may capture signature-related operational evidence such as signer-entered identity, drawn signature image, timestamp, IP or session details, location metadata when enabled, and certificate-page records generated by the platform.

These records are intended to support operational traceability and business recordkeeping within the scope of the product.

The operator may also maintain logs concerning access to the document, signature prompts, acknowledgement actions, and related workflow events to support customer audit trails, fraud review, dispute handling, and service support.

Unless specifically integrated with a legally recognized external signature provider or separately governed process, a signature workflow inside docrud should not be represented as a universal substitute for all legally prescribed forms of execution.

Users remain responsible for confirming whether a document requires a specific statutory execution method, stamp duty handling, witness process, digital signature class, or formal legal review.

Nothing in the signed-document flow should be interpreted as creating automatic legal validity for every instrument, deed, filing, undertaking, board action, employment matter, regulated sector document, or cross-border arrangement.

Under the Information Technology Act, 2000, electronic signatures and secure electronic signatures carry a statutory framework, and certain forms of recognized electronic authentication may depend on prescribed methods, valid certificates, or licensed trust infrastructure.

Where a transaction specifically requires a Controller of Certifying Authorities-recognized method, a licensed certifying authority workflow, a Digital Signature Certificate, or an approved eSign implementation, users remain responsible for ensuring that the chosen execution flow satisfies that requirement.

Accordingly, customers must not describe every docrud signing event as a government-recognized secure electronic signature unless the relevant workflow is in fact connected to an applicable legally recognized signature infrastructure and process.

Signed document records, logs, timestamps, signature images, access events, and appended certificate pages may assist in operational recordkeeping and evidentiary support, but their final evidentiary treatment will depend on applicable law, judicial assessment, and surrounding facts.

Nothing in the platform should be interpreted as a conclusive certificate of legal proof, admissibility, or evidentiary sufficiency in every forum or transaction.

Users remain responsible for preserving related communications, approvals, board or managerial authority records, transaction context, and any other supporting evidence that may be relevant to the legal standing of the signed document.