Ghostwriting plugin privacy
The quote form where the attachment is an unpublished confession naming people who never agreed to be in it
A ghostwriting quote can look like a sample chapter and a fee. It is also an intake that says "tell us your story" — and clients do: affairs, estrangements, the real reason the business sold. The quote attachment is often a draft of the most private document a person will ever produce, naming third parties who never consented to being written down. It can sit in the uploads folder before any NDA is signed. A project that dies quietly can leave the fullest record: an unpublished manuscript nobody is watching, describing everyone. Manuscript-upload, story-brief, named-person, project-title, and genre fields are configured, not documented defaults. Optional draft uploads go in the site uploads folder. A quote booking is not proof a book was written. A named-person answer is a stored note, not proof those people consented. A page request is not proof anyone hired a ghostwriter. The page URL can say ghostwriting 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 account pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a defamation claim, an NDA-enforcement claim, a blackmail claim, or a 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, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where quote bookings, manuscript intakes, and page tags go
Quote bookings and manuscript forms handled on your WordPress site
Check which manuscript-upload, story-brief, named-person, project-title, or genre fields you enable, who can open form entries and bookings, where uploaded drafts live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a project. Notification emails can also copy the same story brief and file link off-site. One table can name the client, the manuscript, and the third parties next to a project title, even when the book is never written. Ask your web vendor not to collect a full manuscript next to named people on the first public form, not to store story briefs next to contact details in one open submissions list, and to purge unused quote bookings after the date passes. A privacy-policy page does not by itself limit who can export a customer list. A stored booking is not proof a book was written.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the ghostwriting booking or account page. That page request can reach a vendor host before anyone submits. The page URL can say ghostwriting even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and account pages if you do not want that page request. A browser scan cannot inspect stored manuscripts, story briefs, or named people. An "author client" badge is not a verified storage path.
Ghostwriting booking, manuscript-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 publishing or rights-management software without a WordPress.org listing is outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| 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 ghostwriting consult is a booking you create; a service name such as memoir quote, book proposal, or sample chapter is a label you configure. Neither is a documented default. Manuscript-upload, story-brief, named-person, project-title, or genre questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked consult is not proof a manuscript was written, and a named-person answer is not proof those people consented. Cancelling or missing the slot later does not erase the story brief or named people already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a project is not a documented default of the plugin. 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. | Quote bookings, custom intake fields, and automatic confirmation emails on your WordPress site | 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. Manuscript-upload, story-brief, named-person, project-title, or genre questions are fields you add; they are not documented defaults. A draft manuscript is a file you accept; that file type is not a documented default. A quote request is not proof a book was written. A named-person answer is a stored note, not proof those people consented. A dead project still leaves the uploaded draft in the uploads folder. 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 an account row sits after a request that never became a project is not a documented default of the plugin. | Account and quote form entries stored in WordPress; file uploads in the site uploads/forminator folder | 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, 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 manuscript-upload, story-brief, or named-person field was sent. A page request from this script is not proof anyone hired a ghostwriter. The page URL can say ghostwriting even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and account pages. Keep marketing tags off those pages if you do not want that page request. A tagged ghostwriting page can re-confirm quote interest next to a stored manuscript; this row does not claim a project from that request. | 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. Manuscript-upload, story-brief, named-person, project-title, or genre fields often depend on the fields you configure. A quote booking is not proof a book was written. A manuscript upload is a file, not a verified confession. A marketing-tag page request is not proof anyone hired a ghostwriter. The page URL can say ghostwriting even when no form is submitted. The draft and the named people can sit after the project dies. This page is about an unpublished confession attachment, not a translation whole-document upload, not a genealogy family-secret confirmation, not an expungement re-record, and not a psychic listed-regrets intake. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or account page, and how long records and backups are kept. An "author client" 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 defamation, NDA enforcement, or blackmail. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and account pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-ghostwriting-plugin-privacy