Signed waivers and upload folders
Is the signed waiver PDF sitting in /uploads?
Waiver plugins can write completed liability PDFs into your WordPress uploads directory or finish signing on a vendor waiver service. What personal fields a form collects depends on the template you publish. Check where signed files live, whether those URLs are web-reachable, and who can open them. General contract e-signature tools and gym membership records have separate pages. Compare the documented setups below.
Based on plugin documentation, not tests of your site. Storage path, URL access, and account roles decide who can open signed waivers. This is not legal advice or a compliance rating.
Scan your site for third-party requestsThis scan checks requests made by a visitor's browser on a waiver or signature page, including vendor widgets when they load. It does not list PDF files under uploads, prove whether a signed-document URL is protected, or assess retention in a vendor waiver account.
Local waiver PDFs vs vendor signing
Signed files stored on your WordPress site
Check which uploads subdirectory holds completed PDFs, whether direct file URLs work, how filenames are generated, and who can download agreements from the admin. Review retention after a season or membership ends. Template fields decide what identity details each PDF carries.
Hosted waiver widgets and e-sign services
Some setups embed a vendor waiver widget or send the signature step to an outside e-sign service. Server-side PDF paths may not appear in a browser page scan. Review each vendor account, completed-waiver access, and retention before you rely on a pop-up widget alone.
Waiver and release setups
No paid placement. Site-hosted waiver tools appear first, followed by any vendor-connector group, then unreviewed rows. Site-hosted tools may still email completed PDFs or use license SDKs when enabled. Review template fields separately. Names are alphabetical within each group.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| signwpdf PDF Sign & Fill Documented self-hosted PDF sign-and-fill tools. The listing says signed agreements are stored in WordPress and PDF processing runs on your server. Version 1.1.2 writes signed documents under wp-content/uploads/swpdf-signed-docs/ and PDF templates under wp-content/uploads/psf-templates/, and adds an .htaccess on the templates directory that grants direct access to PDF files. Review whether signed-document URLs are web-reachable, how filenames are generated, who can download completed agreements, and retention after a season ends. Which fields a waiver carries depend on the PDF template you upload. Browser hosts were not verified for this snapshot. | Signed waivers stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| Electronic Signature (SwiftCloud) Documented SwiftCloud e-sign shortcodes for WordPress, including liability-waiver setup examples. The listing states that the actual signature step happens on SwiftCloud servers even when the document shows your branding, then can return the visitor to WordPress. Completed signatures are handled through that service rather than as local upload PDFs alone. Review which fields your waiver doc collects, who can open completed signatures in SwiftCloud, and retention there. Browser hosts were not verified for this snapshot. | Signed waivers handled through a vendor service | Browser hosts not verified | Not assessed | Not tested |
| |
| Smartwaiver Waiver Widget Documented Smartwaiver widget for WordPress. The listing describes converting paper waivers into interactive digital documents and embedding a pop-up widget so customers sign from your site using a Smartwaiver account. Completed waivers are handled through Smartwaiver rather than as local WordPress upload files. Review which fields your Smartwaiver template collects, who can open completed waivers in that account, and Smartwaiver retention settings. Browser hosts were not verified for this snapshot because the plugin pastes account-generated JavaScript. | Signed waivers handled through a vendor service | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This table describes documented waiver workflows, not tests of your site. Consent timing, live URL exposure of specific PDFs, and retention after expiry have not been assessed. Medical, DOB, or minor fields are not assumed — they depend on the template you publish. Check where signed files live, who can open them, and vendor account settings. General contract e-signature tools and gym membership plugins are covered on their own pages.
Documentation snapshot: Oct 8, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-waiver-plugin-privacy