Questions people actually ask.

Mostly some version of “what's the catch?” Here is the long form of the answer, including the parts where SigFetch isn't the right tool.

Is SigFetch really free? What's the catch?

SigFetch is really free — no envelope limit, no recipient limit, no card on file, and no trial clock. The only catch is that I hope some users donate.

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 prevent a signature or contract from being denied legal effect solely because it is electronic.

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. For anything high-stakes, ask a lawyer — not a landing page.

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.

The account is only for the person sending. That side is free too.

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.

Send to one signer or to several, either all at once or in sequence so each person signs in turn. Save any of it as a template and the fields are already placed the next time.

What happens if someone doesn't sign?

If a signer has not responded after three days, SigFetch sends one automatic reminder. After that it's up to you: resend the request with one click from the envelope page, or void the envelope if the deal moved on.

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

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.

If you need one of those standards, use a specialized provider. I'd rather tell you here than after you've sent something.

What doesn't SigFetch do yet?

SigFetch does not currently support notarization or Remote Online Notarization, Form I-9 workflows, bulk sending, team accounts, or Zapier-style integrations. It supports outbound webhooks, but accounts are single-user for now.

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.

Does SigFetch have an API?

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

You can create 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.

Generate an API key in your settings. The documentation is public, and you do not need an account to read it.

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.

But SigFetch is a free signing service, not a permanent document archive. Download completed documents and keep your own copies of anything important. See the Privacy Policy for details about storage and retention.

Who builds SigFetch?

Just me — one developer. SigFetch is an independent project, not a startup with a growth team.

And when you email support@sigfetch.com, it goes to an actual person.

Still wondering something?

Email support@sigfetch.com and I'll answer. If the answer turns out to be useful, it ends up on this page.