Interpreter plugin privacy

The booking that stores someone else's appointment in a language they didn't choose to disclose

An interpreter booking page can look like a calendar and a contact form. The same form often asks for a language pair, an appointment type, a setting (medical, legal, or school), a client name, and special instructions — plus case-document or meeting-agenda uploads — and stores those answers next to the booker's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold "ASL, oncology follow-up, Tuesday" or "Dari, asylum interview" — a sensitive biography in three fields — typed by a clinic, school, or law office for someone who never saw the form, into a vendor table next to a marketing pixel. A booking request is not a confidentiality agreement. An appointment-type field is the booker's description, not the subject's disclosure. A client-name field is a third person who never saw the form. An uploaded agenda is the institution's document in a site uploads folder, not the subject's consent. A page request is not proof anyone needed an interpreter. The page URL can say interpreter even when no form is submitted. Ask what happens to the client name and the language pair after the assignment — the booking stores someone else's appointment in a language they did not choose to disclose, and the row outlives the meeting. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, an interpreter-certification claim, an ADA or Section 1557 interpreter-mandate claim, a court-interpreter-law claim, a confidentiality-code-enforcement 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 assignment bookings, proxy-subject intakes, and page tags go

Intakes and bookings on your WordPress site

Check which language-pair, appointment-type, setting, client-name, or special-instructions fields you enable, who can open form entries and assignment bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the booking stores someone else's appointment in a language they did not choose to disclose. Notification emails can also copy those fields off-site. One table can list every third party whose name sat next to a language pair and an oncology or asylum appointment type. Ask your web vendor not to keep client names next to language pairs in one open submissions list longer than operations need, and to purge intake rows when the assignment closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored appointment is not a confidentiality agreement. An uploaded agenda is not the subject's consent.

Page tags handled by a vendor

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

Assignment, proxy-subject 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 interpreter-dispatch SaaS platforms without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. An assignment booking is a booking you create; a service name such as ASL medical, Dari legal, or Spanish IEP meeting is a label you configure. Neither is a documented default. Language-pair, appointment-type, setting, client-name, or special-instructions questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a confidentiality agreement — and a CSV export of assignment visits next to a client name and a language pair is still a proxy-subject row after an institution booked for someone who never saw the form. Emails can include those custom fields and copy the appointment off-site. 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.

Interpreter assignment bookings stored 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. Language-pair, appointment-type, setting, client-name, or special-instructions questions are fields you add; they are not documented defaults. Completing the form can store a client name next to a language pair, an appointment type, a medical or legal or school setting, special instructions, and optional case-document or meeting-agenda uploads — typed once by an institution for someone who never saw the form into the same tables as a newsletter signup. A booking request is not a confidentiality agreement. An appointment-type field is the booker's description, not the subject's disclosure. A client-name field is a third person who never saw the form. An uploaded agenda is the institution's document in uploads/forminator, not the subject's consent — and a staff login can open "ASL, oncology follow-up" next to a name the patient never typed. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified.

Proxy-subject intake entries stored in WordPress; optional case-document and meeting-agenda 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 language-pair, appointment-type, setting, client-name, or special-instructions field was sent. A page request from this script is not proof anyone needed an interpreter. The page URL can say interpreter even when no form is submitted. Consent timing has not been tested. Review which tags you enable on assignment booking pages.

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. Language-pair, appointment-type, setting, client-name, or special-instructions fields often depend on the fields you configure. A booking request is not a confidentiality agreement. An appointment-type field is the booker's description, not the subject's disclosure. A client-name field is a third person who never saw the form. An uploaded agenda is the institution's document in a site uploads folder, not the subject's consent. A marketing-tag page request is not proof anyone needed an interpreter. The page URL can say interpreter even when no form is submitted. The booking stores someone else's appointment in a language they did not choose to disclose — that is a storage path next to a client name, not a feature these plugins claim. This page is about that proxy-subject intake, not a translation-service document upload, an immigration-lawyer hearing file, an immigration intake, a court process-server calendar, or a daycare IEP roster. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "confidential interpreting" 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 interpreter certification standards, ADA or Section 1557 interpreter mandates, court-interpreter law, or confidentiality-code enforcement. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-interpreter-plugin-privacy