Divorce-lawyer plugin privacy
Where are divorce intake files and consult bookings stored?
Family-law sites can use a contact form for custody worksheets and financial disclosures, a form builder that stores entries in WordPress, or a vendor scheduling widget for consults. This sample reviews three plugins' documentation. Check which fields you collect, who can open records, where uploaded files and emails go, where vendor hosts handle bookings, and how long entries, files, and backups are kept.
Documentation review only. This is not legal advice, or an attorney-ethics, privilege, GDPR, or other compliance assessment.
Scan your site for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where intake files and consult bookings are stored
Files and form entries handled on your WordPress site
Check which intake or file fields you enable, who can open entries, which files you accept, where temporary uploads live, which inboxes receive attachments, and how long records, files, and backups are kept. Notification emails can also copy the same answers off-site.
Bookings handled by a vendor
Some scheduling tools load a vendor widget when a visitor opens the consult page. That page request can reach a vendor host before anyone books. Review account access and retention there. A browser scan cannot inspect stored booking records.
Divorce intake, file-upload, and vendor-booking 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 law-firm CRM 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 |
|---|---|---|---|---|---|---|
| Contact Form 7 Documented self-hosted contact form (plugin version 6.2.2). The listing privacy notice states that, with the default configuration, the plugin does not write submitter personal data to the database and does not send data to external servers. File fields (file / file*) move an accepted upload to a temporary folder, default wp-content/uploads/wpcf7_uploads, attach it to the Mail tab email when the matching mail-tag is set, then remove the temporary copy. Custody worksheets, financial disclosures, or case-history questions are fields you add; they are not documented defaults. Optional reCAPTCHA, Akismet, Constant Contact, Brevo, Stripe, and Turnstile send data only when you enable them. Flamingo or other storage add-ons are separate plugins, not this default. Public form-page browser hosts are unverified. | Uploaded files attached to notification email; temporary copies in the site uploads folder | Browser hosts not verified | Not assessed | Not tested |
| |
| Ninja Forms Documented self-hosted form builder (plugin version 3.15.5). The listing states every submission is stored in the WordPress database, with admin view, search, edit, and CSV export, and that Ninja Forms does not collect those submissions. Custody, financial-disclosure, or case-history questions depend on the fields you build. File uploads are a paid add-on, not a free default. A free Signature field can capture a typed or drawn mark; that is not a court filing. Email notifications can copy field values to any recipients you set. Optional reCAPTCHA, hCaptcha, Turnstile, Akismet, and CRM add-ons send data only when you enable them. Public form-page browser hosts are unverified. | Form entries stored in your WordPress database | Browser hosts not verified | Not assessed | Not tested |
| |
| EMC – Embed Calendly Scheduling With Ease Connects WordPress to a Calendly scheduling URL (plugin version 5.9). The listing shortcode is [calendly url="https://calendly.com/example/call" type="1"]. Version 5.9 embed.php writes that URL onto a calendly-inline-widget (or popup) data-url and calls Calendly.initPopupWidget / initBadgeWidget. Invitee details are collected on the Calendly page, not as WordPress appointment rows. A consult, intake, or case-type question depends on the event type you configure in that Calendly account. Loading the widget can request calendly.com when a visitor opens the page. Review account access and retention there. Calendly API-key setup and admin notices are admin paths, not listed here as extra visitor-browser hosts. | Consult bookings handled through a Calendly scheduling page | calendly.com | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Custody worksheets, financial disclosures, or case-history notes often depend on the fields you configure. A custody worksheet is not a court filing. A consult booking is not proof of representation. Camera metadata and unlisted media URLs are described only when a plugin documents them. Consent timing, access controls, and retention have not been tested. This page describes storage paths only. 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
- WordPress file-upload plugin privacy
- Law-firm intake tracking
- All privacy guides
/wp-divorce-lawyer-plugin-privacy