Tax preparer plugin privacy
That W-2 in the uploads folder — is the SSN already in the filename?
Independent tax preparers and small CPA firms on WordPress can collect a document-intake form that receives W-2s, 1099s, prior-year returns, and driver's licenses — sometimes with the SSN in the uploaded filename — through general-purpose form, upload, and marketing-tag plugins. A full return answers everything a fraudster needs for refund fraud. Retained entries and public uploads can keep those files across an unmaintained off-season. This sample reviews three plugins' documentation. Check which document fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long intake rows, files, and backups are kept after the engagement.
Documentation review only. This is not tax advice, not an IRS filing guide, and not a tax-practice, GDPR, or other compliance assessment.
Scan your tax-office intake page for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded W-2s or returns, email inboxes, staff permissions, vendor accounts, or backups.
Where tax documents and intake answers are stored
Files and form entries handled on your WordPress site
Check which W-2, 1099, prior-year return, driver's-license, filing-status, 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, files, and backups are kept after the engagement — including across the off-season. Notification emails can also copy identity and tax answers off-site. A return in a public uploads path is a complete identity-theft kit in one PDF.
Marketing tags on the get-started or upload page
Some tools load a marketing pixel or tag on the same page as the document-intake form. A page request can fire before anyone submits a W-2 — and can treat income bracket or filing status 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 tax documents.
Tax-office document-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 tax-portal SaaS tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| 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 W-2s, 1099s, prior-year returns, driver's licenses, or other tax documents you accept depends on the fields you add; they are not fixed tax-office defaults. Filenames chosen by clients can include SSNs. 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/uploads | Browser hosts not verified | Not assessed | Not tested |
| |
| 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. Filing-status answers, document-type fields, refund preferences, SSN or ID fields, or contact fields depend on the fields you add — they are not fixed tax-office defaults. Optional payment, CRM, or spam-protection integrations send data only when enabled. Retention of entry rows after the engagement — including across the off-season — is not specified as a default purge. Public form browser hosts are unverified. | Document-intake form entries stored in your WordPress database | 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, 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 W-2 or return was sent. A page request from this script on a document-intake page is not proof that a return or SSN was collected — and a pre-consent tag on that page can still treat income bracket or filing status as an audience segment. 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 get-started and document-upload pages. | 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. W-2s, returns, ID scans, or filing-status answers often depend on the fields you configure. A document-upload form is not tax advice and is not an IRS filing. A marketing-tag page request is not proof a return or SSN was collected. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess IRS, tax-practice, GDPR, or other compliance status. Ask your web vendor where entries and uploads live, whether tax documents stay off the public web, whether portal links expire, whether rows purge after season, whether the site is patched in the off-season, and whether "secure client portal" claims match the storage path you can verify. Review stored records, uploaded files, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
Scan your tax-office intake page for third-party requests/wp-tax-preparer-plugin-privacy