Veterans benefits plugin privacy

The DD-214 and rating letter in the uploads folder

Veterans-benefits consultants and VSO intake sites on WordPress can collect a full service-and-medical dossier in one upload field — DD-214, disability rating letter, diagnoses, unit history, and the personal statement describing the worst day of someone's service — through general-purpose form, upload, and marketing-tag plugins. It lands in a WordPress contact-form database because that is how small claims-help practices take intakes. A remarketing pixel on that intake page can fire before consent and treat disability-claims intent as an audience segment — and visiting a disability-claims page is itself a sensitive fact about a veteran. This sample reviews three plugins' documentation. Check which service and medical fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long intake rows, DD-214s, rating letters, and backups are kept after the engagement ends.

Documentation review only. This is not legal advice, not a VA accreditation or claims-process guide, not a benefits-outcome or rating-increase promise, and not a GDPR or other compliance assessment.

Scan your veterans-benefits intake page for third-party requests

The scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded DD-214s, rating letters, email inboxes, staff permissions, vendor accounts, or backups.

Where DD-214s, rating letters, and intake-page tags are stored

Files and form entries handled on your WordPress site

Check which DD-214 upload, rating-letter, diagnosis, unit-history, personal-statement, ID-scan, or contact fields you enable, who can open entries, which uploads you accept, where temporary uploads live, which inboxes receive attachments, and how long records, service PDFs, and backups are kept after the engagement ends. Notification emails can also copy intake answers off-site. A rating letter next to a personal statement in the contact-form database is a full service-and-medical dossier on a marketing site.

Marketing tags on the veterans-benefits intake page

Some tools load a marketing pixel or tag on the same page as the veterans-benefits intake form. A page request can fire before anyone submits a DD-214 — and can treat disability-claims intent as an audience segment. Review which tags you enable, which consent filters you use, and what those platforms retain. A browser scan cannot inspect stored form entries or uploaded service records.

Veterans benefits intake 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 veterans-benefits SaaS tools without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Drag and Drop Multiple File Upload for Contact Form 7

Documented Contact Form 7 upload extension (plugin version 1.4.0). The free-version listing states uploaded files move to a temporary folder under /wp-content/uploads/wp_dndcf7_uploads, attach to mail, then are removed from that temporary folder after submission — the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which DD-214 PDFs, disability rating letters, diagnosis records, unit-history files, personal statements, or other intake files you accept depends on the fields you add; they are not fixed veterans-benefits defaults. Filenames chosen by visitors can include full legal names or service-number fragments. Pro documents Media Library storage, custom upload folders, auto-delete timers, and remote storage options. Public form-page browser hosts are unverified.

Uploaded files attached to email; temporary copies under wp-content/uploadsBrowser hosts not verifiedNot assessedNot tested
  • None
Formidable Forms

Documented self-hosted form builder (plugin version 6.35). The listing states every form submission is stored in the WordPress database, with back-end entry access, CSV export, and email notifications or autoresponders you configure. DD-214 upload, rating-letter, diagnosis, unit-history, personal-statement, or contact fields depend on the fields you add — they are not fixed veterans-benefits defaults. An intake form that stores a rating letter next to a personal statement about the worst day of service is a full service-and-medical dossier parked in the same contact-form database as ordinary lead capture. Optional payment, CRM, or spam-protection integrations send data only when enabled. Retention of entry rows after the engagement ends is not specified as a default purge. Public form browser hosts are unverified.

Veterans-benefits intake form entries stored in your WordPress databaseBrowser 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, OpenAI Pixel, 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 DD-214 was sent. A page request from this script on a veterans-benefits intake page is not proof that a claim file was collected — and a pre-consent tag on that page can still treat disability-claims intent as an audience segment. Visiting a disability-claims page is itself a sensitive fact about a veteran. The listing describes consent-plugin filters; that is not a legal-compliance assessment. Consent timing has not been tested. Review which tags you enable on intake and document-upload 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. DD-214 upload, rating-letter, diagnosis, or personal-statement fields often depend on the fields you configure. An intake form is not a claims outcome, not a rating increase, and not VA accreditation. A marketing-tag page request is not proof a DD-214 or rating letter was collected. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess VA accreditation, claims outcomes, rating increases, legal advice, GDPR, or other compliance status. Ask your web vendor where entries and uploads live, whether post-engagement intake rows purge, whether portal links expire, whether marketing pixels stay off intake pages, whether DD-214s and rating letters stay off the first contact form, and whether “secure intake” badges match the storage path you can verify. Review stored records, uploaded service files, connected services, exports, notification emails, and backups.

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

Related pages

Scan your veterans-benefits intake page for third-party requests

/wp-veterans-benefits-plugin-privacy