Common Questions

Frequently Asked Questions

Everything people ask most, from what signID is to how signatures hold up legally, comparisons, and API basics.

What is signID? signID is an API-first, white-label electronic signature platform for sending, signing, sealing, and verifying documents online.

Who built signID? signID is built by brandID and is part of the brandID product family (which includes Ainfluencer, DMpro, ContactID, and Bookme).

How do you write the name? Always as signID, lowercase “s”, uppercase “ID”. Not “SignID”, not “signid”.

Where is signID hosted? The production app runs at signid.brandid.app.

In most jurisdictions, yes. signID produces Simple Electronic Signatures (SES), which are legally binding under:

US ESIGN Act and UETA
EU eIDAS (as SES; not AES or QES)
UK Electronic Communications Act
Most other developed-country e-signature laws

Every sealed envelope has an audit trail (IPs, timestamps, signer identifiers), a SHA-256 hash for tamper evidence, and a public verify page for independent confirmation. Together, these form the primary evidence of a valid signature.

Note. This is general information, not legal advice. For high-stakes contracts or specific regulatory requirements, consult a lawyer. See Security & Compliance for the honest scope of what signID can and cannot claim.

No. Signers open a secure signing link, sign, and receive a copy, all without creating an account or downloading an app. This is one of signID’s core design commitments.

Optional: signers can access their document history across every workspace that ever sent them an envelope via the signer portal at /my-documents. Sign-in is via email OTP (no password required). Fully optional, not required for signing.

PDF only. signID accepts PDF files as the source format for envelopes. If your document is in another format:

Word / Google Docs / Pages: export as PDF first (File → Export or Print → Save as PDF)
Images: combine into a PDF using any PDF tool
Scanned documents: save as PDF (image-based PDFs work fine, though field placement is spatial, not text-anchored)

signID does not accept .docx, .doc, .pages, .txt, .rtf, or image formats directly.

Depends on your plan:

Solopreneur (free): ~5 MB max upload
PAYG: similar to Solopreneur
Business: significantly higher (typically 50 MB+)
Enterprise: highest, custom on request

signID is engineered to handle very large PDFs (targeting up to ~2 GiB / 10,000 pages) via direct-to-S3 uploads and windowed rendering. For envelopes over ~100 pages, the send process is asynchronous to keep the UI responsive.

The signID UI (Desk and signer app) supports multiple languages, with English as the default. Additional languages roll out over time.

Document content is language-agnostic, meaning signID handles PDFs in any language, script, or writing system (English, Persian, Arabic, Chinese, Cyrillic, etc.) as long as the PDF renders correctly.

Tip. When bulk-sending via CSV with non-ASCII names or emails, save the CSV as UTF-8 to preserve characters correctly.

Yes. The Solopreneur plan is free and includes:

1 seat (just you)
Up to 3 signers per envelope
~5 MB max upload per file
~7 envelopes per month
Basic signing features, public verification, downloads

Free-tier limits do not include API access, webhooks, custom branding, bulk send, or embedded signing. For those, see Plans & Billing.

signID is a modern alternative to DocuSign designed for three use cases DocuSign handles less well:

API-first and embedded. signID’s signer UI is meant to be dropped into your product via iframe with white-label branding. DocuSign supports embedded signing but it’s not the primary product surface.
Mobile-first, no-account signing. Signers never sign up. DocuSign tends to push signers toward accounts.
Pricing. signID has a free tier and PAYG option that DocuSign doesn’t match, especially for occasional senders.

Honest note. DocuSign is more mature, has more enterprise-specific features (SSO, custom domains, advanced admin), and holds certifications signID does not (SOC 2 Type II, HIPAA BAA availability, eIDAS QES via qualified trust service providers). If those matter to you, DocuSign or a similarly certified provider may be a better fit today.

Yes. signID’s Partner API is documented via OpenAPI 3.1 with an interactive reference in-app. Key endpoints:

Create envelopes
Fetch status and details
Download sealed files
Mint embedded signing sessions
Public verify (unauthenticated)

Authentication is via Bearer API keys (sk_live_...) with rate limiting per key and per endpoint. API access is gated by plan (Business and Enterprise). See Partner API.

Yes, though it’s rolling out rather than long-shipped. Embedded signing includes:

Chromeless signer UI at /embed/sign/:token
Iframe-friendly with responsive layouts
Origin-bound embed tokens (short-lived, allow-listed hosts)
Hosted embed.js loader for simple integration
Versioned postMessage protocol for host-iframe communication

The founding use case is Ainfluencer, where influencers sign campaign contracts inside the marketplace without ever leaving. See Embedded Signing.

No, and we don’t claim otherwise. signID’s practices align with SOC 2 principles (encryption, access controls, audit logging), but signID has not undergone a third-party SOC 2 audit.

signID is not a HIPAA Business Associate and should not be used for signing envelopes containing PHI (Protected Health Information) subject to HIPAA.

eIDAS: signID produces Simple Electronic Signatures (SES), not Advanced (AES) or Qualified (QES) signatures.

If certification matters for your use case, either wait for signID to obtain the relevant certification or use a provider that already has it.

Once the last signer completes:

signID merges all signatures into the PDF and flattens the result
The document is linearized (via qpdf) for fast web viewing
SHA-256 hash is computed
Sealed PDF is encrypted and stored in S3
All parties receive a sealed-receipt email with the sealed PDF, verify link, and hash
If you configured webhooks, an envelope.signed event fires to your endpoint
The envelope’s status becomes signed (terminal)

Downloads (signed PDF, completion certificate, complete bundle) are available from the Desk and via API. See Downloads & Sealed Documents.

Two ways:

Web: visit signid.brandid.app/v/<envelopeId> or use the /verify lookup page. Anyone can access these, no account needed. See Public Verification.
API: call GET /api/v1/verify/<envelopeId> (unauthenticated) to get metadata as JSON.

To confirm the PDF itself hasn’t been tampered with, compute the SHA-256 of the file and compare to the hash on the verify page. If they match, the file is byte-identical to what signID sealed.

signID’s AI Contract Studio lets you draft contracts from scratch with AI assistance rather than uploading a pre-existing PDF. Three modes:

Wizard: answer structured questions specific to your contract type
Prompt: describe what you need in plain language
Template: start from one of 15 built-in contract types (NDA, service agreement, employment agreement, etc.)

Once you have a draft, use per-clause AI actions (rewrite, expand, shorten, explain) to refine, then convert to a PDF envelope for signing. AI Contract Studio is rolling out, meaning implementation is complete but not yet released across all plans. See AI Contract Studio.