FinalSeal
Privacy Policy
Last updated October 22, 2026
This Privacy Policy describes how Joy Software Studio LLC (“Joy Software Studio,” “we,” “us”) collects, uses, and shares information when you use FinalSeal, the website, API, and related services at finalseal.io (the “Service”). FinalSeal is a product of Joy Software Studio LLC. Our address is 100 N Howard St #7669, Spokane, WA 99201, United States.
Questions: support@finalseal.io.
1. Information we collect
Account. Email address, password (stored as a one-way hash), optional full name, and a hashed 4-digit kiosk PIN if you set one. We do not store your password or PIN in plaintext.
Documents you upload. PDF templates, field layouts, and the envelopes you send, including recipient names and email addresses and the values signers submit (signatures, initials, dates, and typed text).
Signers. Signers do not create accounts. When someone opens a signing link or submits, we record their name and email as you provided them, the fields they filled, and audit metadata: IP address, user agent, and timestamps (viewed, signed).
Developer integrations. API keys (shown once; we store a hash and prefix) and webhook endpoint URLs and secrets that you configure.
Public verify. If someone uploads a PDF to /verify, we hash the file to look up a sealed document. We do not use that upload as a new stored contract beyond what is needed to perform the check.
Technical data. Session cookies (including CSRF), and, during in-person kiosk, same-origin flags so other tabs show the PIN pad. Server logs may include IP address and request metadata.
2. How we use information
- Provide the Service: accounts, templates, sending, signing, sealing, and download.
- Email signing invites and sealed-copy / completion notices to the addresses you supply.
- Build the Certificate of Completion and the public verify record (SHA-256 of the sealed PDF).
- Authenticate you (session or API key) and lock the owner session during kiosk handoff.
- Deliver webhooks to URLs you register.
- Operate, secure, and debug the Service.
- Measure which pages and controls people use, with Google Analytics.
We do not sell your personal information.
3. How we share information
People you involve. Recipients see the document and their assigned fields. Completion copies go to signers at the emails you entered. Public verify for a completed envelope may show sender, recipients, and signer list — not signing tokens or the full private audit timeline.
Your integrations. If you use webhooks or the API, event payloads go to systems you control.
Processors. Hosting, object storage (document files), email delivery, Google Analytics, and, if you use them, Google or Apple sign-in. They process data only to provide those functions. Analytics events include the page and the control you used. They do not include document contents, passwords, PINs, signing links, or API keys.
Legal. We may disclose information if required by law or to protect the Service, our users, or the public.
4. Cookies and local storage
We use a session cookie and a CSRF cookie so you can stay signed in and submit forms safely. During kiosk, we use same-origin storage so other tabs lock to the PIN pad. We use Google Analytics cookies to count visits and record which pages and controls are used. We do not use advertising cookies.
5. Retention
We keep account data, templates, envelopes, sealed PDFs, and audit records for as long as your account exists and as needed to provide “keep” and “prove” (re-download and integrity check). You may ask us to delete an account or specific records at support@finalseal.io. Some sealed documents and hashes may be retained longer if they are part of an integrity record you or a verifier still rely on, or if we must keep them for legal reasons.
6. Security
Passwords and kiosk PINs are hashed. Signing links use time-limited tokens. API keys are hashed at rest. No method of transmission or storage is 100% secure.
7. Your choices
You can update account details while signed in, void pending envelopes, and contact us to access or delete personal information. Signers who want a change to data captured on a document should contact the sender; we process signer data on the sender’s behalf to complete that envelope.
8. Children
The Service is not directed to children under 16. We do not knowingly collect personal information from them.
9. International transfers
The Service may be hosted in the United States or other regions. If you use it from elsewhere, you understand that information may be processed in those locations.
10. Changes
We may update this policy. The “Last updated” date will change. Continued use after an update means you accept the revised policy.
