Electronic signatures in Saint Vincent and the GrenadinesBuilt for business
in Saint Vincent and the Grenadines.

Section 22 of the Electronic Transactions Act, 2015, Act No. 6 of 2015, is met when a method identifies the person and shows that person's intention, and the method is as reliable as appropriate or is proven in fact. A secure electronic signature under section 27 is a different signature. inSigner keeps the completion record with the file.

Simple electronic signature on Essential and Pro · not a secure electronic signature under section 27

Service agreement

Signed

Example

Completed with the evidence record

s. 22Identify the person and show intention

s. 27A secure electronic signature is different

s. 5Wills, property, trusts, and powers

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 conveyance or transfer of an interest in real or personal property, an indenture, a declaration of trust, a power of attorney, or an immigration, citizenship, or passport document 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 transfer of an interest in real or personal 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 a secure electronic signature under section 27.

  • 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 Vincent and the Grenadines ask us.

The limits sit here, including section 22, a secure electronic signature under section 27, and the claims this page does not make.

Contact our team

What inSigner covers

The parts of an electronic signature flow in Saint Vincent and the Grenadines that the service offers today.

Are electronic signatures legal in Saint Vincent and the Grenadines?

The Electronic Transactions Act, 2015, Act No. 6 of 2015, gives legal effect to electronic documents, records and signatures. It was passed in the House of Assembly on 30 April 2015 and assented to on 12 May 2015. Section 1(2) says the Act comes into operation on a day appointed by the Governor-General by Proclamation published in the Gazette. Section 42 repeals the Electronic Transactions Act, Chapter 145. Section 7 says information and transactions shall not be denied legal effect, validity, or enforcement solely because they are in electronic form, provided the requirements of the Act are met. Section 9 says a writing requirement is satisfied by an electronic record if section 8(1)(b) and (c) are met: the information is accessible so as to be usable for subsequent reference and capable of being retained. Section 22 says a signature requirement, or a consequence if a document or a record is not signed, is satisfied for an electronic record if a method identifies the person and indicates that person's intention, and the method is as reliable as appropriate for the purpose or is proven in fact to have fulfilled those functions. Section 16 says an offer and the acceptance of an offer may be given by electronic communications. The standard inSigner signature is an electronic signature under section 2 and the ordinary method in section 22. It is not a secure electronic signature under section 27. Whether section 22 is met still depends on the document and the law that governs it. inSigner does not decide that question.

What does section 22 require, and how is a secure electronic signature different?

Section 22 asks for a method that identifies the person and indicates that person's intention in respect of the information in the electronic record, and for a method that is as reliable as appropriate for the purpose for which the electronic record was generated or communicated, in the light of all the circumstances, including any relevant agreement, or that is proven in fact to have fulfilled those functions, by itself or together with further evidence. Section 23 says that, unless otherwise provided by law, the parties may agree to a particular method or form of electronic signature or security procedure. Section 6 says nothing in the Act requires a person to use or accept electronic communications, electronic signatures, or electronic contracts, and that the parties may vary by agreement any provision in Parts II, III or IV or set reasonable requirements for how electronic signatures are accepted. Section 2 defines an electronic signature as data in electronic form attached to, incorporated in, or logically associated with other electronic data and serving as a method of authentication. A secure electronic signature is a different signature. Section 27 treats an electronic signature as a secure electronic signature when a specified security procedure, or a commercially reasonable security procedure agreed by the parties, can verify that the signature was unique to the person using it, capable of identifying that person, created under that person's sole control, and linked to the electronic record so that a change would invalidate the signature. Section 26 is about a secure electronic record, which is also a different status. Section 28 gives presumptions, unless contrary evidence is adduced, only in proceedings involving a secure electronic record or a secure electronic signature, and section 28(3) says that without that secure status Part V creates no presumption of authenticity or integrity. The standard inSigner signature is not a secure electronic signature under section 27. QES for Europe is an Enterprise option and is not a secure electronic signature under section 27. Section 15 says an electronic record or an electronic signature is not denied admissibility solely because it is electronic, and that this section does not affect the Evidence Act, Cap. 220.

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 a secure electronic signature under section 27, it is not a secure electronic record under section 26, and it is not encryption. Section 11 is about original form when information must be presented or retained as an original. The hash does not by itself decide that section.

What inSigner does not cover

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

Is the standard signature a secure electronic signature or a QES?

No. Essential and Pro use a simple electronic signature. Section 27 of the 2015 Act treats a signature as a secure electronic signature only when a specified security procedure, or a commercially reasonable security procedure agreed by the parties, can verify uniqueness, identification, sole control, and a link that would invalidate the signature if the record changed. Section 29 lets the Minister, by order in the Gazette, list specified security procedure providers or specify a security procedure. inSigner is not a specified security procedure provider under section 29, and the standard signature is not a secure electronic signature under section 27. Section 13(2) says a seal requirement is met if the document indicates that it is required to be under seal and it includes the secure electronic signature of the person by whom it is required to be sealed. Section 13(3) says a notarisation, acknowledgment, verification, or oath requirement is met if the electronic signature of the person authorised to perform those acts, together with the other information required by other applicable law, is attached to or logically associated with the electronic signature, document, or record. inSigner is not that authorised person and does not act as a notary. QES for Europe is an Enterprise option, priced separately, and it is not a secure electronic signature under section 27. It is not on Essential or Pro.

Does section 22 cover a will, a conveyance, a trust, a power of attorney, or an immigration document?

No. Section 5(1) says the Act does not apply to any written law requiring writing, signatures, or original documents for the making, execution, or revocation of a will or testamentary instrument; the conveyance of real or personal property or the transfer of any interest in real or personal property; the creation, performance, or enforcement of an indenture, a declaration of trust, or a power of attorney; the production of documents relating to immigration, citizenship, or passport matters; or any other matters the Minister determines by order published in the Gazette. inSigner does not file a document in a public registry. Your counsel decides the form a document needs.

Does accepting the process satisfy section 22?

Not by itself. Section 6 says nothing in the Act requires a person to use or accept electronic communications, electronic signatures, or electronic contracts, and that the parties may set reasonable requirements for how electronic signatures are accepted. Section 6(3) says whether a party agrees to conduct a transaction electronically is determined by the context and surrounding circumstances, including that party's conduct. Accepting the electronic process in inSigner records consent to sign that document. It does not, by itself, decide whether the method in section 22 identifies the person, shows intention, and is as reliable as appropriate, and it does not turn the signature into a secure electronic signature under section 27. 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 privacy or data protection law of Saint Vincent and the Grenadines. 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 Vincent and the Grenadines, not legal advice. The signature policy in the legal center is the binding text. Responsibilities for electronic signatures

Your next agreement in Saint Vincent and the Grenadines starts here

Send it. Sign it. Prove it.

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

Start signing free