Credit repair plugin privacy

The tri-bureau report and SSN uploaded to a contact form

Credit repair firms on WordPress can collect an intake that receives the single most financially sensitive bundle a consumer ever hands a small business — full tri-bureau credit report PDFs, Social Security number, every late payment and collection, dispute letters, and ID scans — through general-purpose form, upload, and marketing-tag plugins. The person uploading is often at their most vulnerable: denied a mortgage, post-collection, looking for a path back. A remarketing pixel on that intake page can fire before consent and treat credit-repair intent as an audience segment. This sample reviews three plugins' documentation. Check which identity and credit-history fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long intake rows, report PDFs, and backups are kept after the engagement ends.

Documentation review only. This is not legal advice, not an FCRA or CROA guide, not a credit-score or deletion-outcome promise, not a bureau-affiliation claim, and not a GDPR or other compliance assessment.

Scan your credit-repair intake page for third-party requests

The scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded credit report PDFs, dispute letters, email inboxes, staff permissions, vendor accounts, or backups.

Where credit report PDFs, SSNs, and intake-page tags are stored

Files and form entries handled on your WordPress site

Check which Social Security number, credit-report upload, dispute-letter, collection-history, 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, report PDFs, and backups are kept after the engagement ends. Notification emails can also copy intake answers off-site. An SSN next to late-payment and collection answers in the contact-form database is a tri-bureau financial strip-search on a marketing site.

Marketing tags on the credit-repair intake page

Some tools load a marketing pixel or tag on the same page as the credit-repair intake form. A page request can fire before anyone submits a Social Security number — and can treat credit-repair 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 credit report PDFs.

Credit repair 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 credit-repair 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 tri-bureau credit report PDFs, dispute letters, ID scans, or other intake files you accept depends on the fields you add; they are not fixed credit-repair defaults. Filenames chosen by visitors can include full legal names or Social Security 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. Social Security number, collection-history, dispute-status, or contact fields depend on the fields you add — they are not fixed credit-repair defaults. An intake form that stores an SSN next to late-payment and collection answers is a tri-bureau financial strip-search 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.

Credit-repair 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 Social Security number was sent. A page request from this script on a credit-repair intake page is not proof that a credit report or SSN was collected — and a pre-consent tag on that page can still treat credit-repair intent 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 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. Social Security number, credit-report upload, dispute-letter, or collection-history fields often depend on the fields you configure. An intake form is not a credit-score improvement, not a deletion guarantee, and not a bureau dispute outcome. A marketing-tag page request is not proof an SSN or credit report was collected. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess FCRA, CROA, credit-score outcomes, bureau affiliation, 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 credit report PDFs stay off the first contact form, whether SSN fields stay off the contact form, and whether “secure intake” badges match the storage path you can verify. Review stored records, uploaded reports, connected services, exports, notification emails, and backups.

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

Related pages

Scan your credit-repair intake page for third-party requests

/wp-credit-repair-plugin-privacy