Tenant screening plugin privacy
The application that stores the eviction you explained away
A rental application can look like a form and a background check. It is also an intake that hands eviction history, pay stubs, and identity documents to a landlord you have never met — and the denial reason can sit in the entries table long after you found somewhere else to live. Small landlords often run this through a generic form plugin, not a FCRA-grade system. Eviction-history, pay-stub, identity-document, employment, income, landlord-reference, and denial-reason fields are configured, not documented defaults. Optional pay stubs and ID scans go in the site uploads folder. An application is not proof an eviction happened. A denial note is a stored label, not a verified FCRA adverse-action notice. A page request is not proof anyone applied. The page URL can say tenant screening even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which CRM tags load on application and account pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, an FCRA claim, a fair-housing claim, a credit-scoring claim, or a 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, CRM accounts, or backups.
Where rental applications, document uploads, and CRM tags go
Application forms and document uploads handled on your WordPress site
Check which eviction-history, pay-stub, identity-document, employment, income, landlord-reference, or denial-reason fields you enable, who can open form entries, where uploaded pay stubs and ID scans live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after an application that never became a lease. Notification emails can also copy the same eviction explanation and file link off-site. One table can name the applicant, the eviction note, and the denial reason next to a pay stub, even when the unit went to someone else. Ask your web vendor not to collect an eviction explanation next to ID scans on the first public form, not to store denial reasons next to contact details in one open submissions list, and to purge unused applications after the decision date. A privacy-policy page does not by itself limit who can export an applicant list. A stored application is not proof an eviction happened.
CRM tags handled by a vendor
Some CRM tools load a vendor script when a visitor opens the rental-application or account page. That page request can reach a vendor host before anyone submits. The page URL can say tenant screening even when no form is submitted. Review which CRM tags you enable, account access, and retention there. Keep CRM tracking off application and account pages if you do not want that page request. A browser scan cannot inspect stored eviction notes, pay stubs, or denial reasons. An "applicant" badge is not a verified storage path.
Tenant-screening form, document-upload, and CRM 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 tenant-screening or credit-bureau software without a WordPress.org listing is outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| 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. Eviction-history, pay-stub, identity-document, employment, income, landlord-reference, or denial-reason questions are fields you add; they are not documented defaults. A pay stub or ID scan is a file you accept; that file type is not a documented default. An application is not proof an eviction happened. A denial-reason answer is a stored note, not a verified FCRA adverse-action notice. A denied application still leaves the eviction explanation and uploaded stubs in the submissions list. 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 an application row sits after a request that never became a lease is not a documented default of the plugin. | Application form entries stored in WordPress; file uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| Iptanus File Upload Documented frontend upload form (formerly WordPress File Upload). 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. A pay stub, driver license, or passport scan is a file you accept; that file type is not a documented default. An uploaded ID is a file, not proof identity was verified. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. | Identity and income document uploads stored under the site wp-content path | Browser hosts not verified | Not assessed | Not tested |
| |
| HubSpot Documented official HubSpot plugin when a portal is connected. The plugin enqueues a site-wide tracking script from js.hs-scripts.com on front-end pages. Forms and live chat are extra embeds and are not this row. Automated events do not by themselves prove that an eviction-history, pay-stub, or denial-reason field was sent. A page request from this script is not proof anyone applied for a rental. The page URL can say tenant screening even when no form is submitted. Consent timing has not been tested. Review which CRM tags you enable on application and account pages. Keep CRM tracking off those pages if you do not want that page request. A tagged application page can re-confirm rental interest next to a stored eviction explanation; this row does not claim a lease from that request. | CRM page tags handled through a connected HubSpot portal | js.hs-scripts.com | Not assessed | Not tested |
What this table does and does not prove
This is a documentation review, not a test of your site. Eviction-history, pay-stub, identity-document, employment, income, landlord-reference, or denial-reason fields often depend on the fields you configure. A rental application is not proof an eviction happened. A denial note is a stored label, not a verified FCRA adverse-action notice. A CRM page request is not proof anyone applied. The page URL can say tenant screening even when no form is submitted. The eviction explanation and the uploaded stubs can sit after the applicant found somewhere else to live. This page is about a generic-form rental application, not a real-estate buy-side funnel, not a mortgage lending file, and not a roommate peer-to-peer profile. Ask your web vendor who can open entries, where uploaded files live, whether a CRM tag loads on the application or account page, and how long records and backups are kept. An "applicant" 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 FCRA, fair-housing, or credit scoring. Review stored records, uploaded files, connected services, exports, notification emails, CRM tags on application and account pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress forms privacy
- WordPress file upload plugin privacy
- WordPress CRM plugin privacy
- All privacy guides
/wp-tenant-screening-plugin-privacy