A method for electronically signing contracts between at least a first and a second party, the method comprising the first party accessing filling in an online form of a second party's server, the method comprises: a. the second party's server: i. compiling the personal data provided by the first party, together with the terms and conditions of the contract, ii. creating a unique identifier, iii. including said unique identifier in the contract, iv. generating a random key encrypting the contract, v. v. encrypting said random key with a trusted third party public key of a pair of TPP public and private keys, wherein the public key is properly certified and shared and the private key is kept secret inside the trusted third party,, vi. computing a hash digest H vii. sending the encrypted contract, the encrypted random key and the hash digest H to the trusted third party, b. the TTP placing the encrypted contract in a publicly accessible server and sending the URL of the publicly accessible server to the second party's server, c. the second party's server sending the URL of the publicly accessible server and the random key to the first party, d. the first party downloading from the trusted third party, decrypting and accessing using the random key, the contract, e. the trusted third party receiving from the first party the ID inside the decrypted contract and comparing a hash of said ID against H received from the second party's server and generating an evidence that the contract has been accessed by the first party when the hashes match, f. when the hashes match, the trusted third party generating and sending an SMS or an email containing a one-time password to the first party, g. the first party replying the SMS or email sent by trusted third party entering the received OTP indicating first party's agreement with the contract, h. the trusted third party receiving and checking the validity of the OTP, i. upon validating the OTP, the trusted third party compiling all the technical information and creating a certificate document which includes: i. the encrypted contract, ii. the encrypted random key, iii. the hashed ID, iv. an ID of the first party, v. phone number or email the OTP was sent to, and vi. time in which the confirmation OTP was generated. j. timestamping the certificate document and storing the timestamped certificate document on the trusted third party information system. a. the second party's server: i. compiling the personal data provided by the first party, together with the terms and conditions of the contract, ii. creating a unique identifier, iii. including said unique identifier in the contract, iv. generating a random key encrypting the contract, v. v. encrypting said random key with a trusted third party public key of a pair of TPP public and private keys, wherein the public key is properly certified and shared and the private key is kept secret inside the trusted third party,, vi. computing a hash digest H vii. sending the encrypted contract, the encrypted random key and the hash digest H to the trusted third party, i. compiling the personal data provided by the first party, together with the terms and conditions of the contract, ii. creating a unique identifier, iii. including said unique identifier in the contract, iv. generating a random key encrypting the contract, v. v. encrypting said random key with a trusted third party public key of a pair of TPP public and private keys, wherein the public key is properly certified and shared and the private key is kept secret inside the trusted third party,, vi. computing a hash digest H vii. sending the encrypted contract, the encrypted random key and the hash digest H to the trusted third party, b. the TTP placing the encrypted contract in a publicly accessible server and sending the URL of the publicly accessible server to the second party's server, c. the second party's server sending the URL of the publicly accessible server and the random key to the first party, d. the first party downloading from the trusted third party, decrypting and accessing using the random key, the contract, e. the trusted third party receiving from the first party the ID inside the decrypted contract and comparing a hash of said ID against H received from the second party's server and generating an evidence that the contract has been accessed by the first party when the hashes match, f. when the hashes match, the trusted third party generating and sending an SMS or an email containing a one-time password to the first party, g. the first party replying the SMS or email sent by trusted third party entering the received OTP indicating first party's agreement with the contract, h. the trusted third party receiving and checking the validity of the OTP, i. upon validating the OTP, the trusted third party compiling all the technical information and creating a certificate document which includes: i. the encrypted contract, ii. the encrypted random key, iii. the hashed ID, iv. an ID of the first party, v. phone number or email the OTP was sent to, and vi. time in which the confirmation OTP was generated. i. the encrypted contract, ii. the encrypted random key, iii. the hashed ID, iv. an ID of the first party, v. phone number or email the OTP was sent to, and vi. time in which the confirmation OTP was generated. j. timestamping the certificate document and storing the timestamped certificate document on the trusted third party information system.