diff --git a/compose.yaml b/compose.yaml
index b16b071..52ca98e 100644
--- a/compose.yaml
+++ b/compose.yaml
@@ -5,7 +5,7 @@ services:
context: .
dockerfile: osg.dockerfile
- image: osg:29 # <--automate this number change to trigger stack redeploy.
+ image: osg:30 # <--automate this number change to trigger stack redeploy.
environment:
DOCKER: "true"
diff --git a/web_content/OSG Page Image.webp b/web_content/OSG Page Image.webp
new file mode 100644
index 0000000..9f84c15
Binary files /dev/null and b/web_content/OSG Page Image.webp differ
diff --git a/web_content/howto.html b/web_content/howto.html
index 07a67a4..55aeff8 100644
--- a/web_content/howto.html
+++ b/web_content/howto.html
@@ -37,6 +37,23 @@
Check the timestamp and original details from when the signature was registered
Compare the displayed signature with the one in your document, they should be pixel-perfect identical
+
+ Are these signatures legally binding?
+ They absolutely can be! Read more about it here
+ Under the ESIGN Act, some types of documents CAN NOT BE SIGNED ELECTRONICALLY. This includes:
+
+ - Marriage, Birth, and Death certificates
+ - Wills, codicils, and testamentary trusts
+ - Depending on your state, "DNR" orders, general powers of attourney, and any document which specifies a physical signature.
+
+ In summary (for the USA) all ESIGN Act requirements can be met:
+
+ - By generating the signature, and choosing to use it in a document, you are demonstrating intent to sign.
+ - By using the signature you are consenting to do business electronically with those you are signing with.
+ - The Opt-out clause is not applicable to generating a signature, since you can always choose not to use it.
+ - All signers must recieve "Fully Executed" and fully signed copies of the document for the signature to be legally binding.
+ - You may be required to retain digital records of the document under the ESIGN Act.
+