What you should knowbefore you sign

All signatures comply with the eIDAS Regulation (EU 910/2014), so they are valid and admissible as evidence across the 27 member states. Evidential weight depends on the verification level: the more thoroughly the signer is identified, the harder the signature is to challenge.

Yes. Every signature produces a trail with the document hash recorded on a blockchain, a certified timestamp and a record of how identity was verified. That combination is what lets you establish before a court or an inspection who signed, when and under what conditions.

It is the orderly retention of every piece of evidence tied to a signature: the document, the signer identification, the exact moment, the originating address and any later events. Without custody you have a signed document; with custody you have a defensible case file.

A QTSP is a qualified trust service provider, supervised by its national authority and listed on the official EU trusted lists. TsubaSign certifies documents with qualified providers, which strengthens recognition of the signature before notaries and public bodies.

Yes. Personal data is processed in accordance with the GDPR and ISO standards, with end-to-end encryption and granular management of permissions and roles. Biometric data is only processed with the signer explicit consent and solely to verify their identity.

Four. Simple signature, which only records IP and browser. Email OTP, which verifies control of that account. SMS OTP, which links identity to a mobile phone. And full KYC, with official ID document and facial liveness proof.

It depends on the legal risk of the document. Simple signature is enough for internal approvals with no contractual value. Email OTP suits B2B workflows and onboarding. SMS suits transactions with financial or reputational risk. Full KYC is the level for regulated sectors: legal, financial, real estate and health.

Yes, and that is exactly what we recommend. All levels coexist on one platform, so you can configure each workflow according to legal risk, signer type and the compliance requirements you face.

Not as evidence in legal or regulatory proceedings. It records an acceptance in situations with no legal risk, but if you need to defend the signature against a third party you need at least OTP verification.

Four steps: the recipient receives the document for secure review, their identity is verified with OTP, biometrics or two-factor, the document is signed leaving digital and cryptographic traces, and it is sealed with the evidence and legal custody.

No. There is no installation and no prior training. The signer receives a secure link by email or SMS and completes the process in the browser in a few minutes.

Yes. Signing is multi-device and works the same from a mobile, tablet or desktop browser. Biometric verification is also compatible with apps, SMS and secure links.

Yes, the platform supports multi-signature. You can define the signers and manage the workflow, users and permissions from a single dashboard.

The rejection is recorded too. Every event in the process (signature, rejection or modification) is sealed, so the file reflects what actually happened, not only the cases that end in a signature.

Yes. TsubaSign provides a REST API that lets you send documents for signature, check the status of the process and retrieve the evidence from your own applications, without going through the dashboard. Get in touch and we will explain how it fits your environment.

Because it makes document integrity verifiable. Each signature generates a unique hash recorded with a certified timestamp. If someone alters the document afterwards, the resulting hash no longer matches the recorded one, and the tampering becomes evident.

Both options are available. The record can be written to a public or a private blockchain, depending on each organisation confidentiality and compliance requirements.

It is a real-time facial validation that checks there is a real person in front of the camera rather than a photograph, a video or a recreation. It is combined with automated biometric comparison against the official ID document to prevent impersonation.

It is detected. The hash recorded on the blockchain corresponds to the exact document at the moment of signing; any later change, however small, produces a different hash. That is why tampering cannot go unnoticed.

All data is hosted within the European Union. This simplifies GDPR compliance, because there are no international transfers to third countries that would need to be justified in an audit.

There is no single published rate. Pricing depends on signature volume and the verification level you need, and a tailored proposal is prepared after a demo. The figures on the pricing page are indicative and exclude taxes.

Yes. You can request free access from the contact page. We will prepare a demo tailored to your case and to the validation level you need.

Mainly law firms and notaries, health and insurance (informed consent and medical authorisations), human resources (contracts and onboarding), and fintech or regulated sectors with KYC, AML and external audit obligations.

Write to us from the contact page describing your case: document type, approximate volume and the verification level you think you need. We will reply with a proposal and, if you prefer, schedule a demo.