Court reporting plugin privacy
The booking that names both sides of the lawsuit before the docket does
A court-reporting booking form can look like a date and a conference room. It is also a roster of the fight. Before any testimony is taken, the form asks for the case caption, both parties, the deponent, and the attorneys on each side. Case-caption, party-names, deponent, attorney, and exhibit-upload fields are configured, not documented defaults. Nothing in this row is about the person typing it. A scheduler books a deposition and exposes two litigants and a case caption who never touched the form. The deponent never consented to appear in this row. The deposition calendar is a map of the fight: whose testimony is being compelled, and when, in a dispute that may still be confidential. It sits next to a name, an email, and a marketing pixel, and it can outlive the appointment. A booking is not proof a deposition occurred or that a case exists. A party-name field is a client's entry, not a docket record. An uploaded exhibit is a client document, not a filed one. A page request is not proof any firm booked. The page URL can say court reporting or deposition 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 court-procedure claim, a civil-procedure-rules claim, a transcript-admissibility claim, a protective-order claim, an attorney-client-privilege 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 deposition bookings, party names, and page tags go
Deposition bookings and intakes handled on your WordPress site
Check which case-caption, party-names, deponent, attorney, or exhibit-upload fields you enable, who can open form entries and bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a booking that never became a deposition. Notification emails can also copy the same caption and party list off-site. One table can name both sides of a lawsuit next to a deposition date, even when only a scheduler typed. Ask your web vendor not to collect a full party list or exhibit upload on the first public form, not to store that roster next to a caption in one open submissions list, and to purge unused bookings after the date passes. A privacy-policy page does not by itself limit who can export an intake list. A stored booking is not proof a deposition occurred.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the court-reporting booking or intake page. That page request can reach a vendor host before anyone submits. The page URL can say court reporting or deposition 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 case captions. A "confidential deposition" badge is not a verified storage path.
Court-reporting 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 court-reporting or transcript 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 deposition or transcription session is a booking you create; a service name such as deposition, videographer, or realtime feed is a label you configure. Neither is a documented default. Case-caption, party-names, deponent, or attorney questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked deposition is not proof a session happened and is not a docket record of anyone named in the intake. The person who typed the booking is often a scheduler, not a litigant. Cancelling or missing the session later does not erase the party names already stored next to a caption, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a deposition 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. | Deposition and transcription 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. Case-caption, party-names, deponent, attorney, or exhibit-upload questions are fields you add; they are not documented defaults. An exhibit PDF, a notice of deposition, or an audio file is a file you accept; none of those file types is a documented default. A booking is not proof a deposition occurred or that a case exists. A party-name field is a client's entry, not a docket record. People named in it are third parties who never consented. An uploaded exhibit is a client document, not a filed one. 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 intake sits after a request that never became a deposition is not a documented default of the plugin. | Intake and exhibit-upload 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 case-caption, party-names, deponent, attorney, or exhibit-upload field was sent. A page request from this script is not proof any firm booked. The page URL can say court reporting or deposition 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 booking page can re-confirm interest next to a stored case caption; this row does not claim a deposition outcome 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. Case-caption, party-names, deponent, attorney, or exhibit-upload fields often depend on the fields you configure. A booking is not proof a deposition occurred or that a case exists. A party-name field is a client's entry, not a docket record. People named in it are third parties who never consented. An uploaded exhibit is a client document, not a filed one. A marketing-tag page request is not proof any firm booked. The page URL can say court reporting or deposition even when no form is submitted. The deposition calendar can sit after the date passes. This page is about a booking that names both sides of a lawsuit before a docket does, not a criminal-defense intake, a mediation both-sides form, a process-server job, an employment-lawyer consult, or a translation document upload. 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" or "attorney work product" 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 court procedure, civil-procedure rules, transcript admissibility, protective orders, or attorney-client privilege. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and intake pages, and backups.
Documentation snapshot: Oct 14, 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-court-reporting-plugin-privacy