Waiverly

Self-hosted digital waivers with a minor/guardian gate and tamper-evident records.

The problem it solves

Gyms, clinics, salons, and tattoo studios hand out the same liability waiver every day, but generic e-signature tools skip three record-keeping details: a guardian signature for minors, the exact wording each person saw, and a check that shows if a record was changed. Whether a waiver holds up is a question for your lawyer: checking that a minor has a parent's signature, proving exactly which wording someone agreed to, and showing whether a record was altered afterward. Renting a signing service also means a recurring fee and trusting someone else with participant data.

• No age/guardian check on generic e-sign tools
• No proof a record wasn't edited after signing
• Recurring fees for a form you fill out constantly

Every feature

• The signer gets their own copy. On signing, the signer can be emailed what they already know — waiver title, date, expiry, their reference code and the public verify link. Never the signature image, hash or IP. Off by default, through your own SMTP, with the outcome shown on the record.
• Minor / guardian gate. Age is computed from date of birth; anyone under your set minor age cannot submit without a parent/guardian name and second signature.
• Immutable versioned text. Editing a template publishes a new version — every past record stays bound to the exact wording on screen when that person signed.
• Tamper-evident records. Each record carries a SHA-256 fingerprint that is re-checked on every view; an edit made outside the app shows as TAMPERED.
• Expiry & re-sign. Set an expiry so status automatically derives to valid, expired, or needs re-sign with correct calendar math.
• Verify by code. Every record gets a short, no-lookalike-character code to confirm the record exists, is on the current version and its fingerprint still matches.
• Kiosk + public-link signing. Capture signatures at a front-desk kiosk or via a public link people sign on their phone before they arrive.
• Installable mobile app (PWA). Add it to a phone or tablet home screen straight from the browser — a full-screen app served from your own server, with no app store involved. Business data is not stored offline on the device; what you see is read live.
• Ask your own questions. Emergency contact, medical conditions, experience level: text, yes/no, date or a choice, each optional or required.
• Questions that appear when they matter. "Tell us more" shows only after "yes" to medical conditions.
• A separate marketing-consent box. Unticked by default and apart from the waiver.
• Answers you can stand behind. Every answer and the consent are sealed into the signed record's SHA-256 fingerprint, so an edited answer shows TAMPERED.
• Check people in against their waiver. The desk sees at a glance whether a waiver stands; only a valid one checks in.
• Photo at signing, if you want it. Optional or required per waiver, sealed into the record.
• Mailing list, with consent. Export only the signers who ticked the box, ready for Mailchimp; or send each signing to Zapier, Make or n8n.
• One kiosk for every waiver. Guests pick the waiver they need on the tablet, sign, and the screen comes back for the next guest.
• Sign for a child straight after your own waiver. The parent's details are filled in as the guardian, and the child's record links to the parent's.
• Updates from inside the app. The Updates page installs a new release with your license key: Ownware's signature is checked, a backup is taken first, and the app puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. It never checks by itself.
• Backups by themselves. Automatic backups, an optional copy to S3-compatible storage you own, and a weekly check that the latest backup reads back. The Health page names anything that needs attention.
• The signing link by text. Text a waiver's signing link to a number the person gave you for it, through your own SMS gateway, and, if they agreed, one reminder before their visit. Every text ends with a stop link, and a stopped number is never texted again.
• Own It 4.0.1 — fixes and an up-to-date manual. For Waiverly, 4.0.1 fixes an installer that had lost its styling, a rollback that a page opened during an update could stop and a command-line update that ended in an error after putting the previous version back. Its manual, FAQ and QUICKSTART now cover everything 4.0 added, including two Nginx rules that keep the data folder private. Your license covers it: press Check for updates on the Updates page, or download it from your order page.
• Own It 4.0.2 — the installer opens on every host. For Waiverly, 4.0.2 fixes a fresh install on an Apache host: the one-page setup at /install/ looped back to itself and never opened, and now it opens. Your license covers it: press Check for updates on the Updates page, or download it from your order page.

Release notes in full

• Own It 4.1: the signing link by text. For Waiverly, 4.1 adds the signing link by text through your own SMS gateway, with one reminder before the visit if the person agreed. An Extended license bought from October 4, 2026 covers up to ten client installations, one per client project: hand each one over to the client or host it for them, with the client's logo and colors from the app's branding settings. The API reference now shows how to connect Waiverly to Zapier, Make or n8n, using its own webhooks and API key. Your license covers the update: press Check for updates on the Updates page, or download it from your order page.
• Own It 4.0: it updates and backs itself up. For Waiverly, 4.0 means updates from inside the app: the Updates page checks for a new release with your license key, verifies Ownware's signature, takes a backup and puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. A new install can start with a sample business and remove it in one click; backups run by themselves, with an optional offsite copy and a weekly check that the latest one reads back; and the Health page says whether the install is looking after itself.
• Own It 3.2: the waiver asks what you need to know. For Waiverly, 3.2 meant your own questions on the waiver, shown only when they matter and sealed into the signed record, a separate marketing-consent box, an optional photo at signing, check-in against a valid waiver, one kiosk for every waiver, and a child signed for straight after the parent. Each change is a card above.
• Own It 3.1: it writes to the people you serve. The 3.1 wave gave the catalog a way to reach the other side of the transaction: counterparty email through your own SMTP server, calendar feeds your own calendar subscribes to, attachments filed where the paperwork belongs, and export presets other people's software imports. Each outbound feature ships switched off and runs on your own credentials; a failed send is recorded, and the action that triggered it stands. What this app gained is listed at the top of this section.
• Own It 3.0: works for your AI, not just for you. Every MCP tool is read-only by design: an agent can search the register, pull a waiver with the text exactly as signed and hand out a signing link, but it cannot manufacture a signature. A due list tracks everything expiring or expired, with one click to mint a fresh signing link — re-signing never edits the old record.
• Own It 2.0: API, 2FA, backups, dark mode. Waiverly 2.0 adds the 2.0 owner layer. Upgrade by replacing the files — the database migrates itself, and it is still the same one-time purchase.