You've got questions. We've got answers. And other 1990s references.

Is SigFetch really free? What's the catch?

SigFetch is really free — no document limit, no recipient limit, no card on file, and no trial period. If you find it useful, I ask that you donate to support the cause, the same way you'd tip a DoorDash driver or your favorite bartender. SigFetch runs on tips.

Sending, signing, audit trails, and Certificates of Completion are all free, for as long as I can keep it that way. That's the point of the project. If SigFetch helps you, you can always throw me a bone.

Are SigFetch signatures legally binding?

For most routine business documents in the United States, federal and state laws generally give electronic signatures the same legal effect as signatures on paper. SigFetch records consent and intent to sign, along with evidence such as timestamps, IP addresses, browser information, and a Certificate of Completion. It also binds the signed PDF to its record using a SHA-256 hash. Federal ESIGN law and state versions of UETA generally support binding electronic signatures.

Whether a particular agreement is valid or enforceable still depends on the document, the parties, and the applicable law. Some documents have special signing or witnessing requirements. When in doubt, ask a lawyer, not our FAQ!

Does the other person need a SigFetch account to sign?

No. Your recipient gets an email, opens the link, and signs in whatever browser they already have — phone, tablet, or laptop. There is no account to create, no app to install, and nothing to pay.

What can I put on a document in SigFetch?

Upload one PDF or several, then drag on signature, initial, date, text, and checkbox fields and drop them where they belong. Assign each field to a specific recipient when more than one person is signing.

Then, send to one signer or to several, either all at once or in sequence. Save any of it as a template and the fields are already placed the next time you need to use that document.

Can I send the same document to a whole group in SigFetch?

Yes. Save the document as a template, save the people as a contact group under Contacts (paste names and emails, or import a CSV), then send the template to the group. Each person gets their own separate copy to sign, with its own audit trail and Certificate of Completion.

Batches are capped at 50 recipients, and you can add a fixed signer, like a coach or a manager, to every copy. Each copy shows up as its own document in your list, so you can see who has signed and resend to anyone who hasn't.

What happens if someone doesn't sign?

If a signer has not responded after three days, SigFetch sends one automatic reminder. You can also resend the request with one click from the documents page, or void the document if the signature is no longer needed.

Unfinished documents expire about 30 days after they are sent. Signers can also decline and give a reason, which you'll see on the rejected document and in your email.

My signer says the SigFetch email never arrived. Now what?

Junk folder first — that's where it usually is. If it isn't there, the likely culprit is a corporate mail filter. Company filters hold mail from senders they haven't seen before, and a signature request from an unfamiliar domain is exactly the sort of thing they sit on for a while.

The permanent fix is for their IT team to allow-list SigFetch, which takes about a minute. Send them the SigFetch email deliverability page: it has the sending domains, the SPF and DKIM records they'll ask for, and the steps for Microsoft 365, Google Workspace, Sophos, Mimecast, and Proofpoint. In the meantime you can resend from the documents page, or copy the signing link and get it to them another way — the link works no matter how it reaches them.

What about HIPAA, QES, or 21 CFR Part 11?

SigFetch is not offered as HIPAA-compliant and does not support EU Advanced or Qualified Electronic Signatures or workflows designed for 21 CFR Part 11.

Those uses involve additional legal, identity, security, recordkeeping, or system-control requirements. Qualified electronic signatures are a specific category under the EU's eIDAS framework, while Part 11 applies to certain electronic records maintained under FDA requirements. SigFetch is built for ESIGN and UETA per U.S. standards.

What doesn't SigFetch do yet?

SigFetch does not currently support notarization or Remote Online Notarization, Form I-9 workflows, team accounts, or Zapier-style integrations.

There's no SOC 2 or ISO 27001 certification, and no two-factor authentication yet. The security page spells out what is and isn't true today.

If there are specific features you are looking for, please let me know at support@sigfetch.com. We build what people need most!

Does SigFetch have an API?

Yes. SigFetch's REST API is free with every account.

You can create documents/envelopes, upload PDFs, add recipients and fields, send documents, and void envelopes. HMAC-signed webhooks are available for sent, signed, completed, declined, voided, and expired events.

You can generate an API key under settings after you login. The API documentation is public without need for an account.

What happens to documents stored on SigFetch?

SigFetch stores documents encrypted at rest. Each completed document is bound to its signing record using a SHA-256 hash, allowing you to check whether the PDF has changed since it was signed.

However, SigFetch is a free signing service, not a permanent document archive. Please download completed documents and keep your own copies. We make no guarantee that documents will be maintained and available on our servers. See the Privacy Policy for details about storage and retention.

Who builds SigFetch?

Just me — one developer. SigFetch is an independent project which I started because I thought e-signatures should be available to anyone, and I believe that by producing something of value, people will pay what is fair. Call it “Tipware” if you like – tip us like you would your favorite bartender – not as subscription but as recognition of a job well done.