Elopement officiant plugin privacy
The booking that files a wedding the families have not been told about
An elopement-officiant WordPress stack is not only a calendar — it is often the only written record that a quiet wedding is coming. Every confirmed booking can store two full names, the date, the location, and planning notes about who knows and which family complications to avoid. A confirmation email can copy that packet to a shared inbox before anyone arrives. A page request is not proof anyone booked. A who-knows answer is a stored note, not proof of secrecy. An elopement booking is not proof anyone married. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, which inboxes receive confirmation copies, where optional license scans land, and how long past bookings, emails, and backups are kept.
Documentation review only. This is not legal advice, a marriage-validity claim, a family-conflict claim, a counseling claim, a GDPR or other compliance assessment, or a judgment about officiants.
Scan your site for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, bookings, confirmation emails, email inboxes, staff permissions, vendor accounts, or backups.
Where elopement bookings, planning notes, and confirmation emails go
Entries, bookings, and confirmation emails on your WordPress site
Check which couple-name, who-knows, family-complications, or license-checklist fields you enable, who can open form entries and ceremony bookings, which inboxes receive automatic confirmation emails, where optional license scans live in the uploads folder, and how long past bookings, emails, and backups are kept after a ceremony that never happened. Notification emails can also copy the same couple identity off-site.
Uploads or connected destinations off your WordPress site
Some upload tools can send files to FTP, SFTP, or cloud destinations you enable. Review which destinations you turn on, account access, and retention there. A browser scan cannot inspect stored form entries, bookings, or who read a confirmation email. A "private elopement" badge is not a verified storage path.
Elopement-officiant booking, intake, and confirmation-email 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 wedding SaaS platforms without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Easy Appointments Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. A license scan or ID photo is a file you accept; that file type is not a documented default. An uploaded scan is a stored file, not proof a marriage was filed. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. | License-scan or ID uploads stored under the site wp-content path | Browser hosts not verified | Not assessed | Not tested |
| |
| 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. Reason-for-appraisal, rush-order, access-instructions, lockbox-code, owner-at-work, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional interior-photo or document uploads are files you accept; those file types are not documented defaults. A reason-for-appraisal answer is a stored select, not proof a divorce was filed. A rush order is a stored priority label, not proof a crisis happened. An interior-photo upload is a stored file, not a valuation. Access instructions are stored text, not proof anyone entered the home. A elopement-officiant form is not proof anyone completed an appraisal. 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 an appraisal that never happened is not a documented default of the plugin. | Appraisal intake and reason-for-appraisal entries stored in WordPress; optional uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| Iptanus File Upload Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. An interior photo, floor plan, or prior appraisal PDF is a file you accept; that file type is not a documented default. An uploaded interior photo is a stored file, not a valuation. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. How long an interior-photo file sits after an appraisal that never happened is not a documented default of the plugin. | Interior-photo and document uploads stored under the site wp-content path | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Couple-names, who-knows notes, family-complications fields, or license-checklist ticks often depend on the fields you configure. A who-knows answer is a stored note, not proof of secrecy. A license-checklist tick is a stored field, not proof a marriage was filed. An elopement booking is not proof anyone married. A page request is not proof anyone booked. The page URL can say elopement officiant even when no form is submitted. Ask your web vendor who can open entries, which inboxes receive confirmation emails, and how long records and backups are kept. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess marriage validity, family conflict, or ceremony quality. Review stored records, confirmation emails, connected services, exports, and backups.
Documentation snapshot: Oct 20, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress email plugin privacy
- All privacy guides
/wp-elopement-officiant-plugin-privacy