Sealpost Terms of Service

Effective date: set at launch Operator: DigiMar Inc (“Sealpost”, “we”, “us”)

1. What these terms cover

These terms are the agreement between DigiMar Inc and the business or person (“you”) that opens a Sealpost account, holds an API key, or sends documents through Sealpost. They cover the API, the developer dashboard, the MCP server, the signing pages and the sealpost.app website.

People who only sign a document someone sent them are “signers”. Signers do not agree to these terms. What applies to them is the e-signature disclosure shown before the document opens, and the privacy notice.

If you use Sealpost for a company, you agree to these terms for that company and confirm you may do so.

2. Accounts and API keys

• You must be at least 18 and give a working email address.
• Your API keys are yours to protect. Anything sent with your key counts as sent by you. If a key leaks, rotate it in the dashboard; the old key keeps working for 24 hours so your systems can switch over.
• Keys come in two kinds. sk_live_ keys send real documents and are billed. sk_test_ keys run the same API in test mode (section 5).
• One login can belong to several accounts. Each account’s data is separate from every other account’s.
• During early access, before self-serve signup exists, we create accounts by hand from the early-access form and may limit how many envelopes an account can send.

3. What Sealpost does

Sealpost sends a document to the people you name, collects their signatures, stamps the signatures onto the PDF, seals the finished PDF with a digital signature, and keeps a record of every event in the document’s life. We deliver the finished PDF and its audit record to you by API and to each signer by email.

The seal and the audit record show that the document was signed through Sealpost and has not changed since. Whether a signed document is enforceable depends on the law that applies to that document and to you. We do not give legal advice and we do not promise that a document signed through Sealpost is valid for every purpose in every place. See section 12 for the limits we need.

4. Price and billing

• $1.00 per envelope sent. An envelope is one send: one document set to one group of signers. You pay when you send it, whether or not everyone signs.
• Never charged: reminders, views, downloads, API reads, webhook deliveries, cancelled drafts, and anything sent in test mode.
• SMS authentication for signers is passed through at our cost from the carrier, shown per message on your usage page, and rounded up to the cent.
• Monthly cap. You set a dollar cap on your account. When usage reaches it, live sends return an error until the next month or until you raise the cap. The default cap for a new account is shown when you create it.
• Usage is metered as it happens and billed monthly through Stripe to the card on file. Your usage page and GET /usage show the same numbers we bill from.
• Prices are in US dollars and exclude any tax we are required to collect.
• Price changes. If we raise the per-envelope price, we tell you by email at least 30 days before it takes effect. Envelopes sent before that date are billed at the old price. There are no annual contracts and no minimums.
• Refunds. If an envelope fails to send because of a fault on our side, it is not billed. Beyond that, charges for envelopes already sent are not refunded. If you think a charge is wrong, write to billing@sealpost.app within 60 days and we will look at the usage record with you.

5. Test mode

A test-mode request behaves like a live one with four differences: every page of every PDF is watermarked, no email leaves the system, the seal is a test seal, and nothing is billed. Test documents are not binding and you must not present them to anyone as signed agreements. We may delete test-mode envelopes after 90 days.

6. Your content

• You keep every right to the documents you send and the data you collect. We get only the licence we need to send, store, process and deliver them as these terms describe.
• You are responsible for having the right to send each document to each signer, and for the content of what you send.
• We do not read your documents and do not use them to train anything. Our staff see document content only when you ask for help with a specific document, or when the law requires it.

7. Acceptable use

You must not use Sealpost to:

• send documents to people who have not agreed to receive them, or send bulk unsolicited mail of any kind;
• impersonate anyone, forge a signature, or present a test-mode document as a live one;
• send content that is illegal where you or the signer are, or that infringes someone else’s rights;
• probe, scan or load-test the service without written permission from security@sealpost.app (see the security page for how to report a vulnerability);
• offer Sealpost to others as a standalone e-signature product under your own name without a written agreement with us (embedding signing inside your own product, for your own users, is fine and is what the API is for);
• get around the monthly cap, rate limits, or test-mode restrictions.

Documents the service is not for. US federal law (the ESIGN Act, 15 U.S.C. §7003) excludes some records from electronic signing, and we do not want them here: wills, codicils and testamentary trusts; adoption, divorce and other family-law matters; court orders, notices and other court filings; notices cancelling utility service; notices of default, foreclosure, repossession or eviction for a person’s home; notices cancelling health or life insurance; product recalls; and documents that travel with hazardous materials. Do not send these through Sealpost.

If we see any of this we may pause the account, reject specific envelopes, or close the account (section 10). Where we can, we tell you first.

8. Signers

You are the one who chooses to send a document to a signer. You must:

• give each signer’s real name and a working email address or phone number;
• not send a document to a signer who has told you they do not want to sign electronically;
• make sure what you send complies with any law that applies to your industry or the document, including any rule that a contract be given in the language it was negotiated in (we show the signing page and the disclosure in English and Spanish; the document itself is yours).

We show every signer the e-signature disclosure before the document opens and record their acceptance. If a signer declines, we tell you why in the audit record and the document closes for that signer.

9. Availability and support

• No uptime guarantee at launch. We run the service on redundant infrastructure and publish incidents on a status page. We do not yet offer a service level agreement with credits. When we do, it will be a written addendum, not a change to these terms.
• We may take the service down for maintenance. We give notice on the status page for anything planned.
• Support is by email at support@sealpost.app. A person answers.
• We may change the API. Breaking changes get a new version and at least 90 days of notice by email and in the changelog. Additions that do not break existing requests can ship at any time.

10. Ending the agreement

• You can close your account at any time from the dashboard or by email. Closing stops billing at the end of the current month.
• We can close your account with 30 days’ notice for any reason, or at once if you break section 7, do not pay, or if the law requires it.
• Your right to export. At any time, including for 30 days after the account closes, you can export every finished document, every audit record and every envelope’s metadata by API or in bulk from the dashboard. There is no charge for export. We keep documents exportable for those 30 days even if the closure was our decision, unless a law, court order or law-enforcement request requires us to withhold or preserve them, in which case we tell you what we can.
• After export. Documents are then deleted on the schedule in the privacy notice, except that a sealed document under a retention lock you set is kept until the lock ends and then deleted.
• Sections 6, 11, 12, 13 and 14 keep applying after the account closes.

11. Privacy and data

How we handle personal data is in the privacy notice, which is part of these terms. We are the controller of your own account data. For your signers’ data we are your processor (your “service provider” or “contractor” in the words of the US state privacy laws), and this section is the written contract those laws require, so no separate addendum is needed at launch. For signer data we:

• process it only to provide the service to you and as these terms describe, never for our own purposes;
• do not sell it, share it for advertising, or combine it with data from anyone else;
• pass it only to the subprocessors listed in the privacy notice, each bound by written terms at least as strict as these, and tell you 30 days before adding one;
• keep it confidential, protect it as the security page describes, and tell you within 72 hours of confirming a breach that affects it;
• help you answer a signer’s privacy request, and act on it ourselves where we can;
• delete or return it when the agreement ends, subject to section 10 and the retention locks you set;
• tell you if we can no longer meet these commitments, and let you check our compliance by asking us reasonable questions in writing once a year.

If you need a separately signed data processing agreement, a copy of this section with signature blocks is available from legal@sealpost.app. Accounts that handle protected health information also sign a HIPAA business associate agreement (section 15).

12. Warranties and limits

• We provide the service “as is”. We do not promise it will be uninterrupted or error-free, or that a signed document will be enforceable for your particular purpose.
• To the extent the law allows, our total liability to you for anything arising from these terms or the service is limited to the amount you paid us in the 12 months before the claim. We are not liable for lost profits, lost data you could have exported, or indirect damages.
• Nothing here limits liability that cannot be limited by law, including for fraud or for death or injury caused by negligence.

13. Indemnity

You cover us for any third-party claim that comes from the content you send, from your breach of section 7 or 8, or from your use of the service in breach of a law that applies to you.

14. Governing law and disputes

These terms are governed by the laws of the State of Florida, without regard to its conflict-of-laws rules. Any dispute goes to the state or federal courts in Sarasota County, Florida, and you agree to their jurisdiction. Either side may instead bring a claim that qualifies in the small-claims court where they live. Before filing, either side writes to the other and we try to settle it within 30 days.

15. HIPAA

If you send documents that contain protected health information, you must tell us and sign our business associate agreement before the first such document. Accounts that have signed it run in HIPAA mode, which adds field-level encryption, masked email subjects and a longer minimum retention. Sending PHI without a signed agreement breaks section 7.

16. Changes to these terms

We may change these terms. Changes that reduce your rights or raise your obligations take effect 30 days after we email you; other changes take effect when posted. Each version is dated and the previous versions stay readable at the same address. If you keep using the service after a change takes effect, the new terms apply.

17. The rest

• These terms, the privacy notice and any signed addendum are the whole agreement.
• If a court finds one clause unenforceable, the rest stand.
• You cannot transfer this agreement without our written consent. We can transfer it to a successor of our business, and we will tell you if we do.
• Notices to us go to legal@sealpost.app. Notices to you go to the email on your account.

DigiMar Inc 2079 Global Ct, Sarasota, FL 34240 legal@sealpost.app