Prenup attorney plugin privacy

The intake that inventories two estates while the engagement is still a secret

A prenup consult can store both parties' assets, debts, and income next to a wedding date, even when only one of them filled out the form. The fiance is a named third party whose net worth, inheritance notes, and separate-property list can sit in a form plugin entries table before they know a prenup is being considered. The consult date itself timestamps that interest against a wedding date. Requester-name, fiance-name, wedding-date, consult-date, asset-list, debt-list, income, inheritance-expectation, separate-property-list, financial-statement, and phone fields are configured, not documented defaults. Optional financial statements, tax returns, and property-title PDFs go in the site uploads folder. A fiance name is a stored third-party name, not consent. An asset, debt, or income list is a stored field, not proof of net worth. An inheritance expectation is a stored note, not proof of an estate. A separate-property list is a stored list, not proof of title. A wedding date is a stored date, not proof of an engagement. A consult date is a stored date, not proof of doubt. A financial statement is an upload, not a sworn inventory. A prenup booking is not proof anyone is considering a prenup. A page request is not proof anyone booked a consult. The page URL can say prenup even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on booking and intake pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a prenup-success claim, an enforceability claim, a divorce claim, a name-change claim, a guardianship claim, a matchmaking claim, or a GDPR or other compliance assessment.

Scan your site for third-party requests

The scan checks browser requests on the pages it visits. It cannot inspect form entries, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where prenup-intake rows, uploaded files, and page tags go

Prenup bookings and forms handled on your WordPress site

Check which requester-name, fiance-name, wedding-date, consult-date, asset-list, debt-list, income, inheritance-expectation, separate-property-list, financial-statement, or phone fields you enable, who can open form entries and bookings, where uploaded financial statements, tax returns, and property-title PDFs live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a consult is missed. Notification emails can also copy the same requester names, fiance names, wedding dates, consult dates, asset lists, and financial-statement files off-site. One table can name both parties' estates next to a wedding date, even when the other party never visited the site. Ask your web vendor not to collect a fiance name next to an asset list and a wedding date on the first public form, not to store those files next to a consult date in one open submissions list, and to purge unused pairings after the consult date passes. A privacy-policy page does not by itself limit who can export an intake list or republish an upload. A stored fiance name is not consent.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the prenup-attorney booking or intake page. That page request can reach a vendor host before anyone submits. The page URL can say prenup even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and intake pages if you do not want that page request. A browser scan cannot inspect stored fiance names, asset lists, or financial-statement uploads. A "confidential consult" badge is not a verified storage path.

Prenup-attorney booking, intake, and marketing-tag 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 prenup case-management software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Easy Appointments

Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A prenup consult is a booking you create; a service name such as prenup consult, prenuptial agreement, or marital-property planning is a label you configure. Neither is a documented default. The stored service name can say prenup in plain text before anyone signs an agreement. Requester-name, fiance-name, wedding-date, consult-date, asset-list, debt-list, income, inheritance-expectation, separate-property-list, or phone questions are custom fields you add (textarea, select, or input); they are not documented defaults. A fiance name is a stored third-party name, not consent. An asset, debt, or income list is a stored field, not proof of net worth. An inheritance expectation is a stored note, not proof of an estate. A separate-property list is a stored list, not proof of title. A wedding date is a stored date, not proof of an engagement. A consult date is a stored date, not proof of doubt. A booked slot is not proof anyone is considering a prenup, and is not proof an agreement was drafted. Cancelling or missing the slot later does not erase the fiance name, wedding date, consult date, or asset list already stored next to a requester name, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never produced an agreement is not a documented default of the plugin. The appointments list can show who is booked this week and against which wedding date. An optional GDPR setting can auto-remove customer data older than six months; that is not a default purge. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified.

Prenup consult bookings, custom intake fields, and automatic confirmation emails on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
Forminator Forms – Contact Form, Payment Form & Custom Form Builder

Documented self-hosted form builder (plugin version 1.58.1). The listing states Forminator stores and organizes submissions so you can sort, analyze, and manage responses, and includes a free file-upload field with multi-file support. Version 1.58.1 helper-fields.php forminator_upload_root() writes under the WordPress uploads directory plus /forminator/, with per-form hashed subfolders from forminator_get_upload_path(). upload.php stores files through that path. Requester-name, fiance-name, wedding-date, consult-date, asset-list, debt-list, income, inheritance-expectation, separate-property-list, or phone questions are fields you add; they are not documented defaults. Financial statements, tax returns, and property-title PDFs are files you accept; those file types are not documented defaults. A fiance name is a stored third-party name, not consent. An asset, debt, or income list is a stored field, not proof of net worth. An inheritance expectation is a stored note, not proof of an estate. A separate-property list is a stored list, not proof of title. A wedding date is a stored date, not proof of an engagement. A consult date is a stored date, not proof of doubt. A financial statement is an upload, not a sworn inventory. A prenup booking is not proof anyone is considering a prenup. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long a pairing sits after a consult is missed is not a documented default of the plugin.

Prenup-intake entries stored in WordPress; file uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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, and Head and Footer scripts load only when you enable them. Automated events include form submissions; those events do not by themselves prove that a fiance-name, wedding-date, or asset-list field was sent. A page request from this script on a prenup-attorney intake page is not proof anyone booked a consult, and a pre-consent tag on that page can still treat prenup interest as an audience segment from the URL alone. The page URL can say prenup even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake pages. Keep marketing tags off those pages if you do not want that page request. A tagged intake page can re-confirm prenup interest next to a stored fiance name; this row does not claim an agreement was drafted from that request.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Requester-name, fiance-name, wedding-date, consult-date, asset-list, debt-list, income, inheritance-expectation, separate-property-list, financial-statement, or phone fields often depend on the fields you configure. A fiance name is a stored third-party name, not consent. An asset, debt, or income list is a stored field, not proof of net worth. An inheritance expectation is a stored note, not proof of an estate. A separate-property list is a stored list, not proof of title. A wedding date is a stored date, not proof of an engagement. A consult date is a stored date, not proof of doubt. A financial statement is an upload, not a sworn inventory. A prenup booking is not proof anyone is considering a prenup. A marketing-tag page request is not proof anyone booked a consult. The page URL can say prenup even when no form is submitted. Both parties' assets can sit after a consult is missed. This page is about a prenup intake that inventories two estates while the engagement is still a secret, not a divorce worksheet, not a post-decree rename, not an incompetency petition, and not a matchmaking membership. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or intake page, and how long records and backups are kept. A "confidential consult" badge is not a verified storage path. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess prenup-success, enforceability, divorce, name-change, guardianship, or matchmaking claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and intake pages, and backups.

Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-prenup-attorney-plugin-privacy