nx venturer
← NX Venturer

Legal document · version of 2 October 2026

Electronic Signing and Document Exchange Terms

The effect of a signature in NX Venturer, the evidence recorded and when a qualified signature or a notary is required.

Working version: the operator's details (address, registration number, tax ID) and the person responsible for personal data processing will be added before public launch.

The Russian version prevails in case of any discrepancy.

1. Electronic signature agreement

The parties to a document sent for signing through NX Venturer agree that a signer's confirmation in the Service is recognised by them as equivalent to a handwritten signature under the Civil Code of the Republic of Uzbekistan, which permits electronic signatures in the cases and manner agreed by the parties, and the Law of the Republic of Uzbekistan “On Electronic Document Management”.

An NX Standard signature is confirmed by a personal one-time link and a code sent to the signer's email. An NX Strong signature is additionally confirmed by a passkey (WebAuthn) with user verification on the signer's device and a handwritten stroke.

2. Difference from a digital signature

NX Standard and NX Strong signatures are not an electronic digital signature within the meaning of the Law of the Republic of Uzbekistan “On Electronic Digital Signature” and are not issued by a registration centre. Where the law requires a qualified electronic digital signature, a notarial form (for example, transactions with participation interests in a limited liability company) or state registration, signing in the Service records the parties' intent but does not replace the required form.

A signer without an account accepts these Terms when confirming the action via a personal link; the text and version of the accepted consent are kept in the evidence.

3. What the Service records

For every signing the Service keeps: the SHA-256 checksum of the exact document and of its signing representation, the signer's identity and the method of confirming it, the UTC time of each action, IP address and device information, the consent text and version, the handwritten signature image, a chain of evidence hashes in which every record includes the previous one, and the log of emails sent and document views.

On completion the Service produces an executed PDF with the signature record, a verification ID and a QR code, and a certificate of completion with the full timeline. Any copy can be verified by its ID on the Service's verification page. The executed file may additionally be sealed with the Operator's certificate: any change after sealing is detected by PDF viewers.

4. Retention and release of evidence

Signing evidence is kept for at least five years after completion and is released to the parties to the document and, on a lawful request, to competent authorities and courts. The Operator does not alter recorded evidence; changes are prohibited at the database level.

5. Internal approvals

Internal approvals (board, general meeting, investors) record the decision of authorised persons and its evidence. Executing a corporate action in the Service (for example, closing a round) requires a separate confirmation after the required approvals are collected and does not replace the formalities required by law and the constitutional documents.