Version in force since:
This Policy explains how the Lapz electronic signature works, what it proves, what evidence we record and how signers' data is handled. The signer accepts it before signing, and the accepted version is recorded in the document's audit trail.
1. Who this applies to
This Policy covers electronic signatures made through Lapz, a platform of Lapz Serviços de Software Ltda. ("Lapz"). It applies to:
- Signer: the person invited, through an individual link, to sign a document or to receive a copy of it. A Lapz account is not required.
- Sender: the company or entity that uses Lapz and sends the document (the "Organization"), and the members of its team who prepare it.
- Verifier: anyone who receives the final copy and checks the verification page.
People who use Lapz with an account are also bound by the Terms of Use and the Privacy Policy (in Portuguese). On electronic signatures, this Policy prevails.
2. Legal validity
Under Brazilian law, a declaration of intent does not require a special form unless the law expressly demands one (Civil Code, art. 107). The Lapz electronic signature is a means of proving the authorship and integrity of electronic documents without a digital certificate of the signer. Article 10, § 2, of Provisional Measure (Medida Provisória) No. 2,200-2/2001 accepts such means when the parties admit them as valid or when the person against whom the document is presented accepts them.
By accepting this Policy before signing, the signer declares that they admit the Lapz electronic signature as a valid means of proving their authorship and the integrity of the document. The Sender makes the same declaration by sending the document through Lapz.
A document is deemed authentic when its authorship is identified by a legal means of certification, including electronic means (Code of Civil Procedure, art. 411, II). For enforceable instruments created or attested electronically, art. 784, § 4, of the Code of Civil Procedure accepts any form of electronic signature provided for by law and waives witnesses when integrity is attested by a signature provider. The Lapz digital seal and audit trail serve to attest that integrity; the effect in each specific case is decided by the courts.
Law No. 14,063/2020, which classifies electronic signatures as simple, advanced and qualified, governs interactions with public bodies and other situations it specifies, and does not apply to interactions between natural persons or between private legal entities (art. 2, sole paragraph, II, "a"). If the document will be submitted to a public body, check the signature level it requires.
3. When a Lapz signature is not enough
Some acts require a specific form that the Lapz electronic signature does not replace. For example:
- acts that the law reserves to a public deed or another notarial act, such as, as a rule, the creation or transfer of property rights over real estate worth more than 30 minimum wages (Civil Code, art. 108);
- acts for which the law, a public registry or the receiving body requires a qualified signature, made with the signer's own ICP-Brasil certificate, which Lapz does not currently offer;
- wills and other acts with a solemn form;
- documents that a third party, such as a bank, registry office or public body, only accepts in its own format.
The Sender is responsible for checking the required form before sending. If in doubt, consult a lawyer.
4. How signing works
- Invitation: the Sender uploads the PDF and indicates the signers and their contact details. Each signer receives an individual link by e-mail or WhatsApp. Anyone with the link can open the document, so it must not be shared.
- Acceptance: before starting, the signer reads and accepts this Policy. The acceptance is recorded with date, time and the accepted version.
- Identity check: depending on the method chosen by the Sender, the signer enters a 6-digit code sent by e-mail, WhatsApp or SMS (valid for 10 minutes, up to 5 attempts), enters the CPF registered by the Sender, or sends a selfie and a photo of an identity document (RG, CNH or passport). The Sender may also waive the additional check; in that case, identification relies only on access to the individual link.
- Signature: the signer fills in the indicated fields and adopts a signature (drawn, typed or uploaded as an image), applied to all of their signature and initials fields. The signer may share their location if they wish.
- Declining and transfer: the signer may decline to sign by stating a reason, which is sent to the Sender. When this option is offered, the signature may be transferred to another person, and the transfer is recorded.
- Completion: once everyone has signed, Lapz generates the final copy, with the signed document and the audit trail attached, and seals it digitally. Participants receive the download link by e-mail.
5. Evidence we record
To prove who signed, when and how, Lapz records:
- the invitation data: name, e-mail, phone and CPF provided by the Sender, the verification method and the signing order;
- each step (opening the link and the document, acceptance of this Policy, code request and confirmation, selfie and document upload, signature, refusal, transfer and download), with date and time in UTC, IP address and browser;
- a device identifier made of the browser, screen size and time zone;
- the device location, only if the signer allows it in the browser;
- the adopted signature image, the values entered in the fields and, when required, the selfie, the document photo and the attachments uploaded;
- the cryptographic digest (SHA-256 hash) of the original document and of the signed document.
Verification codes are not stored: we keep only a cryptographic digest that allows them to be checked. Lapz does not perform automated facial recognition. The selfie and the document photo are kept as evidence and may be reviewed by authorized people at the Sender.
6. Final copy, digital seal and verification
The final copy combines the signed document and the audit trail (signers, events, IP addresses, verification used and hashes) and receives a PAdES digital seal made with Lapz's ICP-Brasil digital certificate (e-CNPJ) or, when the Sender has registered its own, with the Sender's certificate. The seal covers the entire file: any later change becomes evident to whoever verifies it.
By default, the seal receives a timestamp from a time-stamping authority (RFC 3161 standard), which proves the file existed at that date and time, and the certificate validation data (chain and revocation status), so that verification remains possible after the certificate expires. The time-stamping authority receives only the cryptographic digest of the file, never its content.
The audit trail includes a QR code and the address of the verification page, which shows the title, status, signers (with partially hidden e-mail), dates and the hash of the final copy. The file can also be checked in PDF readers that validate digital signatures.
7. Communications and copies
By accepting this Policy, the signer agrees to receive electronically (by e-mail, WhatsApp or SMS, as applicable) invitations, codes, reminders, notices and the link to the final copy.
The final copy can be downloaded through the individual link and kept by the signer; we recommend keeping a copy. If you prefer a paper copy or do not want to use electronic means, decline to sign and agree on another way with the Sender. To correct your contact details or request a new invitation, contact the Sender.
8. Signer commitments
By signing, the signer declares and agrees to:
- be the person to whom the invitation was sent and, when signing on behalf of a company or another person, have the authority to do so;
- keep the e-mail, phone, link and codes received under their sole control, without sharing them;
- read the entire document before signing and sign only if they agree with its content;
- provide truthful information, including in the selfie and the identity document;
- notify the Sender and Lapz immediately if they suspect misuse of the link or codes.
A signature made with the link and the verification sent to the signer is attributed to them, unless proven otherwise.
9. Sender responsibilities
- The content of the document and the choice of signers, contact details and signing order.
- Choosing a verification method proportionate to the value and risk of the document. Without an additional check, or with a CPF check only, proof of identity is weaker.
- Checking the authority of those who sign on behalf of companies and the form required for the act.
- Having a legal basis to process the signers' data and informing them about it, including when requiring a selfie and an identity document.
- Keeping the final copy for as long as its legal and contractual obligations require.
10. Lapz's role
Lapz provides the signature technology, records the evidence and seals the final copy. It is not a party to the documents, does not review or validate their content and does not provide legal advice.
At the Sender's request or by order of a competent authority, Lapz may provide the evidence recorded for a document.
11. Storage and archiving
The final copy and the audit trail are stored in an archive with a retention lock (WORM), which prevents them from being changed or deleted for 3,650 days (about 10 years) from the creation of the final copy, in line with the general limitation period of the Brazilian Civil Code (art. 205). During this period, removal is only possible through an exceptional procedure with restricted administrative permission, for example to comply with a court order.
The remaining evidence (events, signature image, selfie, document photo and attachments) is kept with the document in Lapz for as long as needed for the purposes of this Policy and the exercise of rights.
12. Signer privacy
Who decides about the data: the Sender is the controller of the signer's personal data used in the signature. Lapz acts as processor and handles it according to the Sender's instructions and this Policy. Lapz is controller only of the records it uses for its own purposes, such as security and fraud prevention in the service.
What we use it for: identifying the signer, conducting the signature, generating and keeping the evidence and the final copy, and enabling verification. The legal bases are defined by the Sender; usually, performance of a contract or of preliminary procedures and the regular exercise of rights (LGPD, art. 7, V and VI).
Who sees it: authorized people at the Sender; the other participants in the document, because the trail attached to the final copy shows each signer's name, e-mail, CPF (when provided), status, date and time, IP address, browser and the process events; and whoever checks the verification page. The selfie, document photo and location are not included in the final copy.
Providers: Amazon Web Services (storage and processing in the United States), Resend (e-mails), Twilio (SMS codes), Meta (WhatsApp) and Vercel (web pages). The time-stamping authority receives only the cryptographic digest of the file, and certificate validation queries go to the certification authorities without signer data. Data is transferred internationally, as explained in the Privacy Policy.
Your rights: confirmation, access, correction, information about sharing and the other rights in art. 18 of the LGPD (Brazilian General Data Protection Law). Contact the Sender first; if that does not work, write to privacidade@softable.com.br indicating the document and the Sender. During archiving, the final copy and the trail are kept for the regular exercise of rights, and deleting evidence may undermine proof of the signature. If your request is not resolved, you may petition the ANPD (Brazilian Data Protection Authority).
13. Technical requirements
- An up-to-date browser with JavaScript enabled.
- Access to the e-mail or phone registered by the Sender.
- A camera, when the Sender requires a selfie and an identity document; without a camera, images can be uploaded.
- A PDF reader to open the final copy.
14. Versions and contact
This is version 2026-10-20. Each acceptance and each signature records the version in force at that moment. A new version applies only to signatures made after its publication; documents already signed remain governed by the accepted version, and previous versions can be requested through the contacts below.
This Policy is available in Portuguese, English and Spanish. In case of discrepancy, the Portuguese version prevails.
Content of a document: contact the Sender.
Platform: contato@softable.com.br.
Personal data: privacidade@softable.com.br.
Platform operator: Lapz Serviços de Software Ltda., CNPJ 69.699.086/0001-99, Av. Comendador Alfredo Maffei, 1489, Jardim São Carlos, São Carlos/SP, 13560-180, Brazil.