Medical billing advocate plugin privacy

The upload that pairs the diagnosis with the debt it caused

To dispute a bill, a patient often uploads the bill — an itemized hospital statement is a diagnosis list with prices. Intake can pair the medical event with the financial aftermath: balance, collections status, what you can afford per month. EOBs, CPT codes, and hardship letters can sit in a contact form as configured fields or stored files. Balance, collections-status, afford-per-month, EOB, CPT-code, hardship-letter, diagnosis-line, patient-name, phone, email, and bill-upload fields are configured, not documented defaults. An uploaded bill is a stored file, not proof a diagnosis is accurate or that a dispute succeeded. A CPT code or EOB field is a configured input or uploaded document, not a clinical or coverage determination. A hardship letter is a stored file or textarea, not proof of eligibility. A medical-billing-advocate intake is not proof anyone hired an advocate. A page request is not proof anyone submitted. The page URL can say medical billing advocate even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which inboxes and mailers receive copies, and how long records, bill files, emails, and backups are kept.

Documentation review only. This is not legal advice, a HIPAA claim, a diagnosis claim, a bill-dispute-outcome claim, a debt-settlement claim, a credit-repair claim, a Medicaid-planning claim, a workers-comp 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, uploaded bills, email inboxes, mailer logs, staff permissions, vendor accounts, or backups.

Where bills, EOBs, and balances go

Medical-billing intake and bill uploads handled on your WordPress site

Check which balance, collections-status, afford-per-month, CPT-code, diagnosis-line, patient-name, phone, email, EOB, hardship-letter, or bill-upload fields you enable, who can open form entries and uploaded files, which inboxes receive copies, and how long records, emails, and backups are kept after an intake that never became a dispute. Notification emails can also copy the same bill lines, balances, and hardship text off-site. One table can name the patient, the balance, and a collections-status note next to an uploaded itemized statement. Ask your web vendor not to collect a diagnosis line next to a balance on the first public form unless you need it, not to store those fields next to patient names in one open submissions list, and to purge unused intake rows after the dispute window closes. A privacy-policy page does not by itself limit who can export a submissions list. A stored bill upload is not proof a diagnosis is accurate.

Notification emails leaving the site through a mailer

Some email/SMTP tools relay form notification messages — including bill or EOB attachments — through an outside mail provider you configure. Review which mailer is selected, whether Pro email logging keeps copies on WordPress or at the provider, and how long those copies are kept. A browser scan cannot inspect stored form entries, uploads, or mailer logs that never load in the visitor browser. An "encrypted email" badge is not a verified storage path for the uploaded bill.

Medical billing advocate form, upload, and 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 medical-billing advocacy SaaS tools without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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. Balance, collections-status, afford-per-month, CPT-code, diagnosis-line, patient-name, phone, or email questions are fields you add; they are not documented defaults. Optional bill, EOB, or hardship-letter uploads are files you accept; those file types are not documented defaults. An uploaded bill is a stored file, not proof a diagnosis is accurate or that a dispute succeeded. A CPT code or EOB field is a configured input or uploaded document, not a clinical or coverage determination. A hardship letter is a stored file or textarea, not proof of eligibility. A medical-billing-advocate form is not proof anyone hired an advocate. Notification emails can copy field values and file links off-site — including itemized bill lines, balances, and hardship text. 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 intake that never became a dispute is not a documented default of the plugin.

Medical-billing intake entries stored in WordPress; bill and EOB uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 itemized hospital statement, EOB PDF, or hardship letter is a file you accept; that file type is not a documented default. An uploaded bill is a stored file, not proof a diagnosis is accurate or that a dispute succeeded. An EOB upload is a stored document, not a coverage determination. 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.

Bill, EOB, and hardship-letter uploads stored under the site wp-content pathBrowser hosts not verifiedNot assessedNot tested
  • None
WP Mail SMTP

Documented WordPress SMTP / mailer plugin. When a mailer is configured, WordPress sends the message (recipients, subject, content, headers, and attachments) plus the credentials you entered to that provider. Covers password resets and other wp_mail() traffic, including form notification emails that can carry medical-billing intake field values and bill or EOB attachments. Email logging is Pro. This row covers an outside-provider configuration. With custom SMTP, the destination depends on the host you enter. Server-side — not a visitor browser host. A relayed notification is a mail-delivery path, not proof anyone hired an advocate or that a dispute succeeded. How long a mailer or Pro log keeps a copy of a bill attachment after an intake that never became a dispute is not a documented default of the free plugin path reviewed here.

Notification and intake emails relayed through a configured outside mailerNo visitor-browser host documented for this medical-billing-advocate path. Other page requests are not covered.Not assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Balance, collections-status, afford-per-month, EOB, CPT-code, hardship-letter, diagnosis-line, patient-name, phone, email, or bill-upload fields often depend on the fields you configure. An uploaded bill is a stored file, not proof a diagnosis is accurate or that a dispute succeeded. A CPT code or EOB field is a configured input or uploaded document, not a clinical or coverage determination. A hardship letter is a stored file or textarea, not proof of eligibility. A medical-billing-advocate intake is not proof anyone hired an advocate. A page request is not proof anyone submitted. The page URL can say medical billing advocate even when no form is submitted. The bill upload, the balance, and the collections-status note can sit after an intake that never became a dispute. This page is about the upload that pairs the diagnosis with the debt it caused, not a general debt-settlement intake, not a credit-repair file, not a Medicaid-planning eligibility form, and not a workers-comp attorney intake. Ask your web vendor who can open entries and uploads, whether bill files remain reachable by direct URL, which mailers receive notification copies, and how long records and backups are kept. A "secure patient portal" 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 HIPAA, diagnosis accuracy, bill-dispute outcomes, debt settlement, credit repair, Medicaid planning, or workers-comp representation. Review stored records, uploads, connected mailers, exports, notification emails, and backups.

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

Related pages

Scan your site for third-party requests

/wp-medical-billing-advocate-plugin-privacy