Notary plugin privacy
Is that will — sitting next to the ID scan — already in your uploads folder?
Mobile notaries and signing agents on WordPress can collect a booking intake that pairs a government-ID scan with the document type being notarized, an unsigned draft, and a home address for the visit — through general-purpose form, upload, and marketing-tag plugins. Document type alone can disclose a life event before anyone stamps anything. This sample reviews three plugins' documentation. Check which ID and document fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long booking rows, files, and backups are kept after the signing.
Documentation review only. This is not a notarial, legal-practice, GDPR, or other compliance assessment, and it is not a legal opinion.
Scan your notary booking page for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded ID or document files, email inboxes, staff permissions, vendor accounts, or backups.
Where booking uploads and document-type answers are stored
Files and form entries handled on your WordPress site
Check which ID-scan, document-type, unsigned-draft, visit-address, or contact fields you enable, who can open entries, which uploads you accept, where temporary uploads live, which inboxes receive attachments, and how long records, files, and backups are kept after a signing. Notification emails can also copy identity and document-type answers off-site. The metadata — "power of attorney, Tuesday, this address" — can leak a life event even when the document file never does.
Marketing tags on the booking or intake page
Some tools load a marketing pixel or tag on the same page as the booking form. A page request can fire before anyone submits an ID or draft — and can treat "estate planning" or "divorce signing" as an audience segment. Review which tags you enable, which consent filters you use, and what those platforms retain. A browser scan cannot inspect stored form entries or uploaded ID files.
Notary booking and signing-intake setups
No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.
Three plugins reviewed from public documentation. Specialty notary-scheduling SaaS tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Drag and Drop Multiple File Upload for Contact Form 7 Documented Contact Form 7 upload extension (plugin version 1.4.0). The free-version listing states uploaded files move to a temporary folder under /wp-content/uploads/wp_dndcf7_uploads, attach to mail, then are removed from that temporary folder after submission — the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which government-ID scans or unsigned document drafts you accept depends on the fields you add; they are not fixed notary defaults. Pro documents Media Library storage, custom upload directories, auto-delete timers, and remote storage options. Public form-page browser hosts are unverified. | Uploaded files attached to email; temporary copies under wp-content/uploads | Browser hosts not verified | Not assessed | Not tested |
| |
| Formidable Forms Documented self-hosted form builder (plugin version 6.35). The listing states every form submission is stored in the WordPress database, with back-end entry access, CSV export, and email notifications or autoresponders you configure. Government-ID references, document-type answers (will, power of attorney, divorce settlement, loan modification, advance directive), mobile-visit addresses, or contact fields depend on the fields you add — they are not fixed notary defaults. Optional payment, CRM, or spam-protection integrations send data only when enabled. Retention of entry rows after the signing is not specified as a default purge. Public form browser hosts are unverified. | Booking and signing-intake form entries stored in your WordPress database | Browser hosts not verified | Not assessed | Not tested |
| |
| PixelYourSite – Your smart PIXEL (TAG) & API Manager Documented pixel and tag manager (plugin version 11.4.2.1). When a Meta Pixel ID is saved, version 11.4.2.1 dist/scripts/public.js loads https://connect.facebook.net/en_US/fbevents.js. A noscript image uses https://www.facebook.com/tr. Google Analytics 4, Google Tag Manager, OpenAI Pixel, and Head and Footer scripts load only when you enable them. Automated events include form submissions; those events do not by themselves prove that an ID scan or document draft was sent. A page request from this script on a notary booking page is not proof that a named document was collected — and a pre-consent tag on that page can still treat "estate planning" or "divorce signing" as an audience segment. The listing describes consent-plugin filters; that is not a legal-compliance assessment. Consent timing has not been tested. Review which tags you enable on booking and signing-intake pages. | Marketing tags handled through Meta, Google, or other configured platforms | connect.facebook.net | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. ID scans, document types, or unsigned drafts often depend on the fields you configure. A booking form is not a notarial act. A marketing-tag page request is not proof a named document was collected. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess notarial, legal-practice, GDPR, or other compliance status. Ask your web vendor where entries and uploads live, whether ID scans stay off the public web, whether document type is a dropdown rather than free text, whether rows purge after signing, and whether "encrypted booking" claims match the storage path you can verify. Review stored records, uploaded files, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress immigration plugin privacy
- Legal intake compliance
- WordPress file-upload plugin privacy
- All privacy guides
/wp-notary-plugin-privacy