Service dog training plugin privacy

The application that documents the disability the dog is for

A service-dog application can store the diagnosis, the physician letter upload, and an essay about the worst day that made the dog necessary. Waitlists can run years, so the record can outlive addresses and marriages; a training-progress portal can pair a handler's name and photo with their medical need. Diagnosis, physician-letter-upload, worst-day-essay, waitlist-status, handler-name, handler-photo, training-progress-note, phone, address, and membership-account fields are configured, not documented defaults. A diagnosis answer is a stored select or textarea, not a medical determination. A physician-letter upload is a stored file, not a verified disability. A worst-day essay is a stored textarea, not proof of harm. A waitlist row is a stored status, not proof a dog was awarded. A handler photo next to a medical need is a stored pairing, not a public registry claim. A service-dog application is not proof anyone received a dog. A page request is not proof anyone applied. The page URL can say service dog even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open applications, uploads, and member lists, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a disability determination, an ADA eligibility claim, a service-dog outcome claim, a bite-history claim, a boarding claim, a prosthetics claim, an IEP claim, or a GDPR, HIPAA, 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, membership lists, email inboxes, staff permissions, vendor accounts, uploaded files, or backups.

Where diagnosis answers, physician letters, and member portals go

Applications and uploads handled on your WordPress site

Check which diagnosis, physician-letter-upload, worst-day-essay, waitlist-status, handler-name, handler-photo, training-progress-note, phone, address, or membership-account fields you enable, who can open form entries, uploads, and member lists, which inboxes receive copies, and how long records, emails, files, and backups are kept after an application that never became a placement. Notification emails can also copy the same diagnosis answers, physician-letter links, and handler photos off-site. One table can name the handler, the diagnosis, and a physician letter next to a phone, even when no dog is placed. Ask your web vendor not to collect a diagnosis next to a handler photo and a physician letter on the first public form, not to store those uploads next to member names in one open list, and to purge unused application rows after the waitlist window closes. A privacy-policy page does not by itself limit who can export an application list. A stored diagnosis answer is not a medical determination.

Membership checkout handled through a payment vendor

Some membership tools load Stripe.js / Elements on the public checkout page when that gateway is selected. That page request can reach Stripe hosts before anyone finishes checkout. Review which gateways you enable, account access, and retention there. Keep checkout scripts off application pages if you do not want that page request. A browser scan cannot inspect stored diagnosis answers or physician letters. A "confidential application" badge is not a verified storage path.

Service-dog application, upload, and membership 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 service-dog 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. Diagnosis, physician-letter-upload, worst-day-essay, waitlist-status, handler-name, phone, or address questions are fields you add; they are not documented defaults. Optional physician-letter PDFs or handler photos are files you accept; those file types are not documented defaults. A diagnosis answer is a stored select or textarea, not a medical determination. A physician-letter upload is a stored file, not a verified disability. A worst-day essay is a stored textarea, not proof of harm. A service-dog application form is not proof anyone received a dog. 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 application that never became a placement is not a documented default of the plugin.

Application entries stored in WordPress; optional physician-letter uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
Iptanus File Upload

Documented frontend upload form (formerly WordPress File Upload; plugin version 5.2.1). 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. Physician-letter PDFs and handler photos are files you accept; those file types are not documented defaults. A physician-letter upload is a stored file, not a verified disability. A handler photo is a stored image, not a public registry entry. A service-dog upload form is not proof anyone received a dog. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. How long an uploaded physician letter sits after an application that never became a placement is not a documented default of the plugin.

Physician-letter and handler-photo uploads stored on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
Paid Memberships Pro

Documented membership plugin (plugin version 3.2.2). Member accounts, levels, and related profile fields are managed in WordPress. Handler-name, handler-photo, training-progress-note, waitlist-status, diagnosis, phone, or address fields on a member profile or application are fields you configure; they are not documented defaults. A diagnosis on a member profile is a stored field, not a medical determination. A handler photo next to a medical need is a stored pairing, not a public registry claim. A membership account is not proof anyone received a service dog. When the Stripe gateway is selected, Paid Memberships Pro Stripe gateway docs describe checkout using Stripe.js / Elements on the public membership checkout page — a visitor-browser path that can load Stripe hosts (stripe.com / stripe.network). Review which gateways you enable, who can open member lists, and retention of member rows after an application that never became a placement. Consent timing has not been tested. Keep checkout scripts off application pages if you do not want that page request.

Member accounts on WordPress; Stripe.js on public checkout when that gateway is selectedstripe.com, stripe.networkNot assessedNot tested

What this table does and does not prove

This is a documentation review, not a test of your site. Diagnosis, physician-letter-upload, worst-day-essay, waitlist-status, handler-name, handler-photo, training-progress-note, phone, address, or membership-account fields often depend on the fields you configure. A diagnosis answer is a stored select or textarea, not a medical determination. A physician-letter upload is a stored file, not a verified disability. A worst-day essay is a stored textarea, not proof of harm. A waitlist row is a stored status, not proof a dog was awarded. A handler photo next to a medical need is a stored pairing, not a public registry claim. A service-dog application is not proof anyone received a dog. A page request is not proof anyone applied. The page URL can say service dog even when no form is submitted. The diagnosis, the physician letter, and the handler photo can sit after an application that never became a placement. This page is about the application that documents the disability the dog is for, not dog-behaviorist bite-history intake, not dog-boarding reservations, not prosthetics cause-as-biography, and not special-education IEP advocacy. Ask your web vendor who can open applications, whether uploads land in wp-uploads or a cloud destination, and how long member rows and backups are kept. A "confidential application" 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 disability status, ADA eligibility, service-dog outcomes, bite history, boarding, prosthetics, or IEP claims. Review stored records, connected services, exports, notification emails, upload destinations, membership gateways, and backups.

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

Related pages

Scan your site for third-party requests

/wp-service-dog-training-plugin-privacy