Electronic signatures in Saint LuciaBuilt for business
in Saint Lucia.

Section 21 of the Electronic Transactions Act 2011 is satisfied when an electronic signature adequately identifies the signatory and indicates approval, and is as reliable as is appropriate. An encrypted signature under section 2 is a different signature. inSigner keeps the completion record with the file.

Simple electronic signature on Essential and Pro · not an encrypted signature under section 2

Service agreement

Signed

Example

Completed with the evidence record

s. 21Identify the signatory and show approval

s. 2An encrypted signature is different

s. 3Wills, immovables, title, and will trusts

PDF + recordSHA-256 of the final file

One flow. A clear record.

Confidence from send to signed.

A clear signing path that records intent, each action, and the evidence behind the agreement.

  1. 01

    Prepare and send

    Upload the document, place the fields, and name every signer.

    See how it works
  2. 02

    Accept and sign

    Each signer accepts the electronic process and signs the fields you placed.

    See how it works
  3. 03

    Prove and keep

    Download the completed PDF together with its evidence record.

    See how it works

Everyday agreements

Document types you can sign with inSigner

Upload a PDF and keep the completion record with the file. A will, a trust created by a will, the creation or transfer of an interest in immovable property, or a document of title is not on this list.

  • Sales

    1. Sales contracts
    2. Order forms
    3. Quotes
    4. Proposals
    5. Statements of work
    6. Master service agreements
    7. Change orders
    8. Renewal agreements
  • Customers

    1. Service agreements
    2. Onboarding packets
    3. Subscription agreements
    4. Acceptance forms
    5. Delivery receipts
    6. Project briefs
    7. Support agreements
    8. Customer addenda
  • Vendors

    1. Vendor agreements
    2. NDAs
    3. Purchase orders
    4. Consulting agreements
    5. Contractor agreements
    6. Supplier questionnaires
    7. Referral agreements
    8. Partnership agreements
  • People

    1. Offer letters
    2. Employment agreements
    3. Handbook acknowledgments
    4. Policy acknowledgments
    5. Commission plans
    6. Performance plans
    7. Equipment agreements
    8. Contractor packets
  • Operations

    1. Move-in checklists
    2. Maintenance logs
    3. Access lists
    4. Key receipts
    5. Facility rules
    6. Insurance acknowledgments
    7. Site instructions
    8. Parking licenses that are not a creation or transfer of an interest in immovable property
  • Company

    1. Internal approvals
    2. Policy updates
    3. Meeting acknowledgments
    4. Access requests
    5. Travel approvals
    6. Expense approvals
    7. Confidentiality acknowledgments
    8. Project sign-offs

And many more.

Evidence, not just a signature

Every action leaves a clear record.

The completion record brings together who was invited, what they signed, and the hash of the final file.

Evidence record

Example
Status
Completed
Signers
The people you invited
Integrity
SHA-256 hash of the final file

If the file changes, the hash no longer matches. Download it with the PDF.

  1. 01

    Consent to sign

    The record keeps the acceptance of the electronic process.

  2. 02

    Signer attribution

    Name, email or phone, and the send, view, and sign events.

  3. 03

    Time-stamped events

    A chronological record from delivery to completion.

  4. 04

    Document integrity

    A SHA-256 hash shows whether the final file still matches.

Commercial agreements

One record. Many everyday documents.

The same completion record for commercial agreements that do not need an encrypted signature under section 2.

  • Business

    Sales contracts

    Vendor agreements

    NDAs

  • Operations

    Proposals

    Orders

    Statements of work

  • People teams

    Offer letters

    Policy acknowledgments

  • More than one team

    The same flow

    In the languages you already use

Questions, answered

What teams in Saint Lucia ask us.

The limits sit here, including section 21, an encrypted signature under section 2, and the claims this page does not make.

Contact our team

What inSigner covers

The parts of an electronic signature flow in Saint Lucia that the service offers today.

Are electronic signatures legal in Saint Lucia?

The Electronic Transactions Act 2011, No. 16 of 2011, is the statute. Section 1 gives that short title and says the Act comes into force on a day fixed by the Minister by Order in the Gazette. The Revised Laws of Saint Lucia (2023) record that Statutory Instrument 95 of 2020 brought listed sections into force on 1 June 2016, including sections 2, 5, 13, 21, 22 and 23, and section 3(a), (c), (d) and (e). They also record that Act 6 of 2014 amended the 2011 Act and came into force on 12 May 2014. The arrangement of sections on that revised-laws page matches the 2011 Act. The section text cited here is the 2011 Act published by the Government of Saint Lucia. Section 2 defines an electronic signature as information contained in, attached to, or logically associated with an electronic document, and used by a signatory to indicate adoption of the content of that document. The definition does not include a signature produced by a facsimile machine or by an electronic scanning device. The same section defines an encrypted signature as an electronic signature encrypted by a private key or other encrypted signature creation device, and it defines a signatory as a person who has affixed an encrypted signature by that device. Section 21(1) says a legal requirement for a signature, other than the signature of a witness, is satisfied by an electronic signature if it adequately identifies the signatory and adequately indicates that person's approval of the information, and it is as reliable as is appropriate given the purpose and the circumstances. Section 21(2) says that, where the signature is on information required to be given to a person, that person must consent to receiving the electronic signature. Section 5 says information must not be denied legal effect solely because it is in electronic form, or because it is referred to in an electronic communication intended to give rise to that legal effect. Section 13 says a legal requirement may be satisfied by information technology where sections 16 to 32 apply and the conditions in the Regulations are satisfied. The standard inSigner signature is the ordinary electronic signature under section 2. It is not an encrypted signature. It does not, by itself, satisfy section 21(1)(b) or the conditions in the Regulations under section 13. Whether a given document is valid still depends on the document and the law that governs it. inSigner does not decide that question.

What does section 21 require, and how is an encrypted signature different?

Section 2 defines an encrypted signature as an electronic signature encrypted by a private key or other encrypted signature creation device. An encrypted signature creation device means unique data, including codes or private cryptographic keys, or a uniquely configured physical device, used in creating an encrypted signature. A signatory, in that section, is a person who has affixed an encrypted signature by such a device. Section 23(1) presumes, for sections 21 and 22, that an electronic signature is as reliable as is appropriate only where the means of creating it are linked to the signatory and to no other person, those means were under the control of the signatory and of no other person, any later alteration of the electronic signature is detectable, and, where the legal requirement is meant to assure the integrity of the information, any later alteration of that information is detectable. Section 23(2) says that presumption does not stop proof, on other grounds, that an electronic signature is as reliable as is appropriate, or that it is not. Sections 2, 21 and 23 do not name a certifying authority and do not require a certificate for the ordinary electronic signature. The standard signature does not make the person a signatory in the section 2 sense, and it is not a certificate. QES for Europe is an Enterprise option and is not an encrypted signature under section 2.

How does the record show who signed what?

Each person signs the fields you placed on the document you sent. The evidence record keeps their name and email or phone, when the document was sent, viewed, and signed, the IP address, the device data, and the authentication used.

Can I download the evidence for a completed document?

Yes. You can download the completed PDF and the evidence record, including a SHA-256 hash of the final file. If a single byte changes, the hash no longer matches. The hash shows whether the final file still matches. It is not an encrypted signature under section 2, and it is not encryption. Section 15 says that, for Part 3, the integrity of information is maintained only if the information has remained complete and unaltered, other than an endorsement or an immaterial change arising in the normal course of communication, storage, or display. The hash does not by itself decide section 15, and it does not by itself decide section 23(1).

What inSigner does not cover

The limits, including the claims this page does not make.

Is the standard signature an encrypted signature or a QES?

No. Essential and Pro use a simple electronic signature. Section 2 treats an encrypted signature as one encrypted by a private key or other encrypted signature creation device. Section 23(1) is a presumption about reliability. It is not the standard inSigner signature, and accepting the inSigner flow does not by itself bring a signature within that presumption. Sections 2, 21 and 23 do not name a certifying authority. The standard signature is not a certificate from a certifying authority. Section 22 says a legal requirement that a signature or a seal be witnessed can be met by an electronic signature of a witness only where that section's conditions are met, including that the person receiving the electronic signature consents. inSigner does not act as a notary, does not witness a signature, and does not file a document in a public registry. QES for Europe is an Enterprise option, priced separately, and it is not an encrypted signature under section 2. It is not on Essential or Pro.

Does section 21 cover a will, an interest in immovable property, a document of title, or a trust created by a will?

Not for the paragraphs the Revised Laws record as in force. Section 3 of the 2011 Act says the Act does not apply to the creation or transfer of interests in immovable property, negotiable instruments, documents of title, wills, trusts created by wills, and any class of documents or transactions excluded by the Regulations. The Revised Laws record that S.I. 95 of 2020 commenced section 3(a), (c), (d) and (e) on 1 June 2016. Those paragraphs are the creation or transfer of interests in immovable property, documents of title, wills, and trusts created by wills. The same note does not list section 3(b) on negotiable instruments or section 3(f) on classes excluded by the Regulations. An uncommenced paragraph is not an exclusion in force. Section 3 does not list a power of attorney or a court filing. inSigner does not file a document in a public registry. Your counsel decides the form a document needs.

Does accepting the process satisfy section 21?

Not by itself. Section 21(1) requires an electronic signature that adequately identifies the signatory and indicates approval, and that is as reliable as is appropriate for the purpose and the circumstances. Section 21(2) adds that, where the signature is on information required to be given to a person, that person must consent to receiving the electronic signature. Accepting the electronic process in inSigner records consent to sign that document. It does not, by itself, decide section 21(1)(b), it does not bring the signature within section 23(1), and it does not make the signature an encrypted signature under section 2. Section 13 also requires the conditions in the Regulations where a legal requirement is to be satisfied by information technology. inSigner does not claim that its flow satisfies those conditions. Sections 14 and 20, on consent to electronic form and on agreement to a method of electronic signature, are not in the list of provisions the Revised Laws record as commenced on 1 June 2016. The sections that note records as in force do not say that the whole Act applies only where the parties agree to transact electronically. inSigner does not decide those points for you.

Does inSigner make a workflow comply with local privacy law, or cover clinical consent and uptime?

No. For the documents you send, you decide the purpose. inSigner does not write your privacy notice and does not make a workflow compliant with the Data Protection Act in the Revised Laws of Saint Lucia. Nubesti handles the account, billing, security, support, and marketing. Do not use the product by default for patient forms, clinical consent, account opening, credit decisions, or KYC. Identity checks are add-ons priced separately. There is no public status page and no uptime percentage. The mobile apps are planned, not a public download.

This page is general information about the law of Saint Lucia, not legal advice. The signature policy in the legal center is the binding text. Responsibilities for electronic signatures

Your next agreement in Saint Lucia starts here

Send it. Sign it. Prove it.

Create an account and send a commercial agreement with its completion record.

Start signing free