1. Who this policy covers

This policy applies to all SMS and WhatsApp messages sent through the SignForge platform (signforge.io) using our messaging carriers, including Twilio. It covers messages sent to:

• Recipients — people designated by a SignForge sender to review and sign a document
• Senders — authenticated SignForge users who opt in to receive transactional account notifications by SMS

2. How consent is collected (opt-in)

SignForge is a transactional e-signature platform. Messages are sent only after a SignForge user takes a deliberate action inside our web application to initiate a signature request. This is the same consent model used by other major e-signature providers including DocuSign, Dropbox Sign, Adobe Acrobat Sign, and PandaDoc.

The opt-in flow works as follows:

1. An authenticated SignForge user (the "sender") signs in at signforge.io and creates a signing envelope at signforge.io/envelopes/new.
2. The sender uploads a PDF and enters the recipient's name, email address, and (for SMS or WhatsApp delivery) mobile number into our web form.
3. Before sending, the sender must check a required attestation box: "I confirm I have authorization to contact this recipient about this document and that they consent to receive SMS or WhatsApp notifications related to it." The attestation, sender ID, recipient phone number, IP address, and timestamp are recorded in our append-only audit log.
4. On submission, the recipient receives a single transactional SMS or WhatsApp message containing a unique, expiring link to review and sign the document. Up to two reminder messages and one completion confirmation may follow, all tied to the same envelope.

Recipients do not need a SignForge account. The sender's attestation, combined with the recipient's prior business relationship with the sender, constitutes transactional consent under the TCPA, the CTIA Messaging Principles & Best Practices, and applicable carrier policies.

3. Message types and sample content

Every SMS and WhatsApp message sent from SignForge falls into one of the following transactional categories. No other message types are sent.

4. Message frequency

Message volume is strictly tied to user-initiated signature requests. A typical recipient receives:

• 1 initial signature request per envelope
• Up to 2 reminders per envelope (only if the document remains unsigned)
• 1 completion confirmation when the envelope is fully signed

SignForge does not send marketing campaigns, newsletters, promotional offers, or bulk messages over SMS or WhatsApp. Frequency varies based on the number of envelopes a recipient is involved in.

5. Opt-out (STOP) and help (HELP)

Recipients can opt out of all SignForge SMS messages at any time by replying with any of the following keywords: STOP, UNSUBSCRIBE, CANCEL, END, or QUIT. Opt-outs are processed automatically by our messaging carrier (Twilio Advanced Opt-Out) and take effect immediately. Once opted out, no further SMS messages will be sent to that phone number from SignForge.

Recipients who reply with HELP or INFO will receive an automated response with support contact information:

"SignForge support: support@signforge.io. Reply STOP to unsubscribe. Msg & data rates may apply."

For WhatsApp, recipients may also block the SignForge sender identity directly within WhatsApp using the platform's built-in block controls. To re-enroll after an opt-out, please email support@signforge.io.

6. Sender obligations

SignForge senders are solely responsible for ensuring they have a legitimate basis to contact each recipient by SMS or WhatsApp about a specific document. By using our SMS or WhatsApp delivery features, the sender represents and warrants that:

• They have an existing business relationship with the recipient or other lawful basis to contact them about the document being sent
• They have obtained any consent required under applicable law (TCPA in the United States, PECR in the United Kingdom, local laws in other jurisdictions) before adding a phone number to a signing envelope
• The phone number entered belongs to the named recipient and has not been opted out of receiving messages from the sender
• They will not use the SMS or WhatsApp channel to send marketing, promotional, fraudulent, abusive, or unlawful content of any kind

SignForge reserves the right to suspend or terminate accounts that violate this policy or generate excessive carrier complaints, opt-out rates, or undeliverable messages.

7. Costs and carrier fees

SignForge does not charge recipients to receive SMS or WhatsApp messages. However, standard message and data rates from the recipient's mobile carrier may apply. Carrier charges are the responsibility of the recipient.

8. Supported carriers and regions

SignForge sends SMS messages through Twilio. Delivery is supported in most countries served by Twilio. Toll-free numbers used for delivery in the United States are individually verified through the carrier's Toll-Free Verification program. WhatsApp messages are delivered through Twilio's WhatsApp Business API using approved message templates.

9. Data handling and retention

Phone numbers entered by senders are stored only for the purpose of delivering the messages described in this policy and maintaining the audit trail required for the legal validity of the signed document. Phone numbers are not shared with third parties for marketing purposes and are not used for advertising, profiling, or sale to data brokers. See our Privacy Policy for full details on how personal data is handled.

10. Reporting abuse

If you believe you have received a SignForge SMS or WhatsApp message in error, in violation of this policy, or as part of suspected fraud or abuse, please contact us immediately at abuse@signforge.io or support@signforge.io. We investigate all reports and will take appropriate action, up to and including suspending the offending sender account.

11. Changes to this policy

We may update this SMS & WhatsApp Policy from time to time to reflect changes in our practices, carrier requirements, or applicable law. Material changes will be announced through the Service or by email to active senders. The "Last updated" date at the top of this page indicates when the policy was last revised.

12. Contact

Questions about this policy or about a specific message you received can be sent to support@signforge.io or via our Contact page.