Debt-settlement plugin privacy
Where are hardship letters and account numbers stored?
Hardship-intake forms can collect creditor names, account numbers, balances, and a hardship narrative before anyone enrolls. File fields can store bank statements or collection letters in the site uploads folder. Marketing tags on those pages can also send a page request to a vendor host. This sample reviews three plugins' documentation. Check which fields you collect, who can open records, where uploaded files land, which tags load on the intake page, and how long entries, files, and backups are kept.
Documentation review only. This is not legal or financial advice, or a FCRA, GDPR, or other compliance assessment.
Scan your site for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where hardship answers, files, and page tags go
Answers and files handled on your WordPress site
Check which hardship or file fields you enable, who can open entries, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept. Notification emails can also copy the same answers off-site.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the consultation or hardship-intake page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. A browser scan cannot inspect stored form entries.
Debt-settlement inquiry, file-upload, and marketing-tag 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 debt-relief CRMs without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder Documented self-hosted form builder (plugin version 3.3.3). The listing states unlimited form submissions with entry collection inside WordPress, plus a setting to disable storing entries in the WordPress database. File Upload is a free field. Version 3.3.3 WpFileHandler.php sets the upload base to the WordPress uploads directory plus /bitforms. FileHandler.php uses wp_handle_upload and a temp folder at uploads/bitforms/temp. Creditor, account-number, balance, or hardship questions are fields you add; they are not documented defaults. Notification emails can copy field values to any recipients you set. Optional Google Sheets, HubSpot, Zapier, and other integrations send data only when you enable them. Public form-page browser hosts are unverified. | Form entries stored in your WordPress database; file uploads in the site uploads/bitforms folder | Browser hosts not verified | Not assessed | Not tested |
| |
| 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. Creditor, account-number, balance, or hardship questions are fields you add; they are not documented defaults. Notification emails can copy field values off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Form entries stored in WordPress; file uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| Meta pixel for WordPress Documented Meta Pixel plugin (plugin version 5.2.2). The listing states the plugin installs a Meta Pixel to capture actions such as Lead, ViewContent, AddToCart, InitiateCheckout, and Purchase, with optional Conversions API. Version 5.2.2 class-facebookpixel.php loads https://connect.facebook.net/en_US/fbevents.js. A noscript image uses https://www.facebook.com/tr. A page request or Lead event from this script is not proof that creditor names, account numbers, or a hardship letter were sent. Consent timing has not been tested. Review which tags you enable on consultation and hardship-intake pages. | Marketing tags handled through Meta Pixel and Conversions API | 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. Creditor names, account numbers, balances, or hardship notes often depend on the fields you configure. A hardship letter is not a credit report. A marketing-tag page request is not proof that account numbers were collected. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the intake page, and how long records and backups are kept. A portal label is not a verified storage path. Camera metadata and unlisted media URLs are described only when a plugin documents them. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess FCRA or other legal status. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on intake pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress file-upload plugin privacy
- WordPress ads plugin privacy
- WordPress insurance plugin privacy
- All privacy guides
/wp-debt-settlement-plugin-privacy