Privacy
Updated November 6, 2026
This page says what Paddock20 Sign collects, why, and who helps us run it.
What we collect
For staff: name, work email and a password kept only as a one-way hash.
For signers: name, email address, optionally a phone number if the sender chose texts, the language, and each step they take.
For the audit trail: the time, the internet address and the device description (browser and system) at each step.
Documents and files the sender uploads, and files a signer attaches when a sender asks for one.
Why
To deliver the agreement, confirm who is signing, keep a reliable record, show the sender where things stand, and keep the service secure. We do not sell personal data and we do not use documents for advertising.
Who helps us
Vercel hosts the application. Neon stores the database. Resend delivers email when a customer's sending is switched on. An independent timestamp authority receives only a fingerprint (hash) of the document, never the document. Text messages go through Twilio only when a sender turns them on, and photo ID checks go through Stripe only when a sender requires one.
Who sees what
A customer's staff see that customer's agreements. Signers see their own agreement. Paddock20 staff can reach the system to run it and help a customer, and do not read documents otherwise.
Your choices
A signer can ask the sender for a paper copy or to withdraw before signing, and can ask for a copy of their record. A staff member can ask the account owner to correct or remove their login. Records that are part of a completed agreement are kept as set out on the retention page.
Security
Connections are encrypted. Signing links carry a secret that is stored only as a hash, codes work once and expire, certificates are stored encrypted, and the record of events is linked so changes show.
Contact
Questions about this page: use the access form on the home page, or email gavin@paddock20.com.
