Privacy notice
This notice explains what happens to the data you enter in the demos on try.lacunasoftware.com, the Lacuna Demo Site. It covers the Demo Site only, and is distinct from Lacuna's corporate Privacy Policy, linked at the end.
Controller and contact
Lacuna Software, CNPJ 20.658.903/0001-71, is the controller of the personal data processed through the Demo Site.
- Contact Lacuna: contact form on lacunasoftware.com ↗
- Data Protection Officer (DPO): Cláudio Pessoa, dpo@lacunasoftware.com
What the Demo Site keeps
The Demo Site stores no personal data about you, except a signed PDF you choose to keep when you make its printer-friendly version (see below).
What you type in a demo exists only in the server's memory while your demo session lasts, and is discarded when it ends.
To limit abuse, the Demo Site counts recent demo actions in memory by IP address, e-mail address, CPF and mobile number. These counters are never written to storage and are lost whenever the server restarts.
The only things it stores are:
- a signed PDF you make a printer-friendly version of, with its file name, for 7 days;
- an anonymous count of each demo's uses per month;
- the encryption keys the site needs to run, which hold no personal data;
- technical logs, kept for 90 days, which never contain IP addresses, form values, names, e-mail addresses, CPFs, mobile numbers, certificate contents or API call contents.
Signer: Sign a document
When you submit the form, and only with your consent (the first checkbox), Lacuna sends your name, CPF and e-mail address, your mobile number unless you chose to sign with your digital certificate, and the document (the sample or the PDF you upload), to Dropsigner, the public instance of Lacuna's Signer at dropsigner.com. Dropsigner e-mails the signing invitation to that address and, for an electronic signature, texts signing codes to that mobile number.
If you sign with your digital certificate, Dropsigner's signing page reads your certificates in your browser through Web PKI and lists only those with your CPF. Dropsigner never receives the private key. The signed document carries your certificate, including the name and CPF in it.
If you tick selfie, liveness or face match, your face is captured on Dropsigner's signing page and goes to Dropsigner and, for the face match, to SERPRO, which compares it with your Denatran (CNH) photo. This happens only with your specific consent (the second checkbox), and only to sign this demo document: biometric data is sensitive personal data under the LGPD (art. 11).
Dropsigner keeps the files and the selfie, liveness and face-match evidence for 90 days, then deletes them. Download your signed document within those 90 days.
Signer: Sign without leaving your page
When you submit the form, Lacuna sends the document (the sample or the PDF you upload) to Dropsigner, the public instance of Lacuna's Signer at dropsigner.com, under a name that says it is a Demo Site test that binds no one. If you choose Me, with my own data, Lacuna also sends your name, CPF and e-mail address, and the document is signed in your name. If you choose the demo signer, Lacuna sends none of your data, and the document is signed in his name. Your PDF, and your name, CPF and e-mail address, are sent only with your consent (the checkbox the demo shows for them).
Dropsigner's signing page then opens inside the demo's page, loaded by your browser straight from dropsigner.com. Like any page, it receives your IP address and details of your browser, and your location only if you allow it. Your browser asks for your location in the Demo Site's name, since the page is embedded in it, but the request is Dropsigner's, and your location goes only to Dropsigner. Dropsigner keeps, as evidence of the signature, your IP address, your location if you allowed it, and the Demo Site as the application that vouched for the signer.
Dropsigner e-mails nothing for this demo: no invitation, no code and no other notification, to you or to anyone else.
If you sign with your digital certificate, Dropsigner's signing page reads your certificates in your browser through Web PKI and lists only those with your CPF. Dropsigner never receives the private key. The signed document carries your certificate, including the name and CPF in it.
The demo signer, Alan Mathison Turing, is fictional. No document signed in this demo binds anyone.
A document left unsigned expires at the end of the next day. Dropsigner keeps the files and the evidence of the signature for 90 days, then deletes them. Download your signed document within those 90 days.
Lacuna sends your data to Dropsigner on the basis of your consent (LGPD art. 7 I), where the demo asks for it.
On the Demo Site, none of it is stored: your PDF, what you type and the link to the signing page are held only in the server's memory for your demo session, and discarded when it ends. That link signs, with one click, as whoever the document names, so it is never logged.
Web PKI: Your certificates in the browser
Your certificates are read in your browser, through Web PKI; their private keys never leave your computer, token or phone. Step 2 shows the certificates Web PKI finds, with their details (such as names, CPF or CNPJ, date of birth and e-mail), on the page: like everything else in a demo, those details are held only in the server's memory for your demo session and discarded when it ends.
Step 3 sends the certificate you choose, including the name and CPF it carries, and a signature made with its key to Rest PKI Core, Lacuna's service, which validates them. The Demo Site stores none of it.
PKI Suite: Sign a file with your certificate
Your file and the signed file pass only through the Demo Site's server memory, and are never stored or logged.
Your public certificate and the signature made with its key reach the Demo Site, which puts them into the signed file. Web PKI signs in your browser, so your private key never leaves your computer, token or phone.
If you add a timestamp, only the document's hash goes to Rest PKI Core's timestamp server, never its content.
Checking whether your certificate has been revoked contacts the certificate authority that issued your certificate.
The report shows your own certificate unmasked, including the name and CPF in it: like everything else in a demo, they are held only in the server's memory for your demo session and discarded when it ends.
PKI Suite: Sign a file with Rest PKI Core
Your file is sent to Rest PKI Core, Lacuna's cloud signing service, which keeps it, and the signed file, for 2 hours.
On the Demo Site, your file and the signed file pass only through the server's memory, and are never stored or logged.
Your public certificate and the signature made with its key reach the Demo Site and Rest PKI Core, which puts them into the signed file. Web PKI signs in your browser, so your private key never leaves your computer, token or phone.
PKI Suite: Sign a PDF with your cloud certificate
Your CPF is sent to CloudHub, Lacuna's cloud certificate service, which asks the trust service providers (PSCs) it reaches whether they hold a cloud certificate for it. As of October 2026, those are BirdID, DSCloud, RemoteID, SafeID, Serasa, SerproID, Syngular, VaultID and VIDaaS. Your CPF then goes to the PSC you choose, where you sign in.
Your PDF never leaves the Demo Site: only its hash goes to CloudHub and to the PSC, which signs it.
On the Demo Site, your PDF and the signed PDF pass only through the server's memory, and are never stored or logged.
When you authorize the demo at your PSC, CloudHub stores that authorization, the signature session, with your CPF, encrypted, and keeps it for 30 days.
When you click Stop signing, the demo forgets the signature session at once, but at the PSC it may stay valid until it expires: up to 15 minutes, the time the demo asks for, unless the PSC sets another time.
Validating your certificate, including whether it has been revoked, contacts the certificate authorities that issued it.
PKI Suite: Validate a signed file
Your file, and the file a detached signature signs, pass only through the Demo Site's server memory while your demo session lasts, and are never stored or logged.
The report shows the certificates in your file as they are, unmasked, including their holders' names, CPFs and CNPJs, other people's included. It shows them only on your own page.
Validating contacts the certificate authorities that issued the certificates in your file, from the Demo Site's server, to build their chains and check whether they have been revoked.
Nothing is sent to any Lacuna service.
PKI Suite: Make a printer-friendly version
When you make a printer-friendly version of your own signed PDF, and only after the demo has told you so, the Demo Site keeps that PDF and its file name, under the verification code printed on it, so that whoever holds the printout can check it.
It keeps them for 7 days. After that the verification code finds nothing, and the file is deleted within a few days after.
Anyone holding the verification code can reach the file on its check page: its report, which shows the certificates in the file as they are, unmasked, including their holders' names, CPFs and CNPJs, and the downloads of the signed PDF and of its printer-friendly version.
Making a printer-friendly version of a sample keeps nothing: each sample has a fixed verification code.
Nothing else is stored or logged: a file the demo refuses is never kept, the printer-friendly version is made again on each download, and the logs never contain your file, its name, its signers or its verification code.
Validating its signatures, when you make the printer-friendly version and on the check page, contacts the certificate authorities that issued the certificates in the file, from the Demo Site's server. Nothing is sent to any Lacuna service.
PKI Suite: Timestamp a PDF
When you add a timestamp, your PDF is sent to Rest PKI Core, Lacuna's cloud service, which keeps it, and the timestamped PDF, for a limited time.
On the Demo Site, your PDF and the timestamped PDF pass only through the server's memory, and are never stored or logged.
To show you the timestamp's authority and time, the Demo Site validates the timestamped PDF on its own server, with PKI SDK. If your PDF already holds signatures, that validation contacts the certificate authorities that issued their certificates, from the Demo Site's server.
Lacuna Bio: Enroll and authenticate your face
When you enroll or authenticate your face, and only with your consent (the checkbox at the top of the demo), Lacuna's capture takes your face with your camera, as images and a 3D face map, and sends it to Rest PKI Core, Lacuna's service at core.pki.rest, through its capture page at restpkicore.lacunasoftware.com, and to Lacuna's FaceTec server. There it is checked for liveness and, to authenticate, compared one to one with the face enrolled under the Subject identifier you give.
The Subject identifier you choose, the random one the demo offers or your own e-mail address or CPF, goes to Rest PKI Core too, which keeps your enrolled face under it.
Your face is biometric data, which is sensitive personal data under the LGPD: Lacuna processes it only on the basis of your consent (LGPD art. 11).
Lacuna deletes them daily: your enrolled face, every face captured to authenticate it, and the Subject identifier.
None of it is stored or logged on the Demo Site. Your face goes from your camera straight to Rest PKI Core, never through the Demo Site, and the Subject identifier, like everything else in a demo, is held only in the server's memory for your demo session and discarded when it ends.
Amplia: Issue an e-CNPJ, e-CPF or SSL/TLS certificate
When you click Issue, and only with your consent (the checkbox above Issue), Lacuna sends the company name, CNPJ, legal representative's name, CPF, date of birth and e-mail address you typed to Amplia, Lacuna's certificate authority platform. Amplia puts them into a test certificate issued by Lacuna's test CA, which has no legal value. The Demo Site keeps none of it.
Amplia keeps the certificate, and so the data in it, for 24 months; Lacuna then purges it.
With the server option, the private key and the .pfx file are made in the server's memory for your demo session only: the key is never stored, and both are discarded when the session ends. With the Web PKI option, the key is made on your computer or token and never leaves your computer or token; only the certificate request, which holds the public key and the data above, goes to Amplia.
In the e-CPF demo, when you click Issue, and only with your consent (the checkbox above Issue), Lacuna sends the name, CPF, date of birth, e-mail address and mobile number you typed to Amplia. Amplia puts them into an order and, once you finish on Amplia's issue page, into a test certificate issued by Lacuna's test CA, which has no legal value. Amplia's issue page shows them back to you.
Issue creates an order on Amplia, and Amplia keeps it even if you don't finish on Amplia's page. Amplia keeps orders, pending ones included, and certificates for 24 months; Lacuna then purges them. The Demo Site doesn't delete abandoned orders, and it keeps none of this data.
The private key is made on Amplia's issue page, on your computer or token, with Web PKI. The Demo Site never sees it.
To confirm the issue, Amplia texts a code to the mobile number you typed.
In the SSL/TLS certificate demo, when you click Issue, Lacuna sends the DNS names you typed, and the CSR if you uploaded or pasted one, to Amplia, Lacuna's certificate authority platform. Amplia puts the names into a test certificate issued by Lacuna's test CA, which no browser trusts. The demo asks for no consent: DNS names aren't personal data, and the certificate's names come only from the DNS names, not from your CSR.
Amplia keeps the orders and certificates of this demo for 24 months; Lacuna then purges them. The Demo Site keeps none of it.
When the Demo makes the key for you, the private key and its .pfx file are made in the server's memory for your demo session only: they are never stored, and are discarded when the session ends. When you bring your own CSR, the private key never leaves your computer; only the CSR, which holds the public key, goes to Amplia.
As in the other demos, the data shown on the page can appear in Clarity recordings.
Amplia: Issue an e-CPF with your face
In the Face e-CPF demo, when you click Continue, and only with your consent (the checkbox above Continue), Lacuna sends the name, CPF and date of birth you typed to Serpro, the Brazilian government's data processing company, which checks them against the Receita Federal's records and tells Lacuna whether they match, whether the CPF is regular, whether you are of age and whether you have a driver's licence (CNH). This happens each time you use the demo.
Then Lacuna's capture takes your face with your camera, as images and a 3D face map, and sends it to Rest PKI Core, Lacuna's service at core.pki.rest, through its capture page at restpkicore.lacunasoftware.com, and to Lacuna's FaceTec server, where it is checked for liveness. The first time, Rest PKI Core sends an image of your face and your CPF to Serpro's Datavalid, which compares your face with the photo on your CNH; you are enrolled only if they match. When you come back, your face is compared one to one with your enrolled face, and Datavalid is not asked again.
Your face is biometric data, which is sensitive personal data under the LGPD: Lacuna processes it, and your data with it, only on the basis of your consent (LGPD art. 11).
Lacuna keeps, under your CPF, your enrolled face, every face captured to authenticate it, the image sent to Datavalid with Datavalid's result, and the capture's technical records (your IP address, browser and device), and deletes them 90 days after you last used the demo.
The Demo Site keeps the name, e-mail address and date of birth you typed, the date and score of your Datavalid comparison and the date you last used the demo, so that it can fill in the form and show you when your face was validated when you come back. It keeps them under a code made from your CPF, not the CPF itself, and deletes them 90 days after you last used the demo. Anyone who types your CPF in the demo sees the name, e-mail address and date of birth kept for it. Your face never passes through the Demo Site.
When you choose a key, Lacuna sends your name, CPF, date of birth and e-mail address to Amplia, Lacuna's certificate authority platform, which puts them into a test certificate issued by Lacuna's test CA, which has no legal value. Amplia keeps the certificate, and so the data in it, for 24 months; Lacuna then purges it. Nobody sends anything to your e-mail address.
With the A1 server option, the private key and the .pfx file are made in the server's memory for your demo session only: the key is never stored, and both are discarded when the session ends. With the A1 browser option and the A3 option, the key is made on your computer or token with Web PKI and never leaves it; only the certificate request, which holds the public key and the data above, goes to Amplia.
The demo can't delete your data itself. To have it deleted sooner than 90 days, or to exercise your other rights, use Lacuna's data-subject request form or write to the DPO (see Your rights below): Lacuna then deletes your enrolled face and what is kept with it, and the Demo Site's record of your data.
Cloudflare Turnstile
Before the Signer demo sends a document, before step 3 of the Web PKI demo, before the e-CNPJ demo issues a certificate, and before the e-CPF demo creates an order, Cloudflare Turnstile checks that a person, not a bot, is acting. For this check, Cloudflare receives your IP address and signals from your browser.
Microsoft Clarity
The Demo Site uses Microsoft Clarity to see how visitors use it. Until you accept its cookies, Clarity records your visit without cookies, on Lacuna's legitimate interest (LGPD art. 7 IX). If you accept them in the cookie banner, Clarity sets its cookies and records full sessions.
Clarity masks what you type in form fields, numbers and e-mail addresses, but names shown on the page, in the Status panel or the certificate list, can appear in its recordings, even if you haven't accepted cookies.
To withdraw your consent, open Cookie settings at the bottom of any page and reject the cookies: Clarity goes back to recording without cookies and its cookies are deleted.
Your rights
To exercise your rights as a data subject under the LGPD, use Lacuna's data-subject request form or write to the DPO at dpo@lacunasoftware.com.