Tenant files inside WordPress

Where does the rental application that never became a lease go?

Property-management and tenant tools can keep rental applications, identification documents, resident portal accounts, or work-order attachments on your WordPress site. Compare where those records are kept, which optional map or email connectors you enable, and what happens after an applicant is declined or a lease ends.

Based on plugin documentation, not tests of your site. Which application fields you enable, who can open tenant screens, connector settings, and backup inclusion decide who can see applicant and resident records. This is not legal advice or a compliance rating.

Scan your site for third-party requests

This scan checks requests made by a visitor's browser on a listing page, application form, resident portal, or map embed, including scripts when they load. It does not inspect application databases, identification uploads, declined-applicant archives, or resident portal rows stored only on the server, test staff permissions, or assess whether backups include those tables.

Applications and tenant files vs membership paywalls

Applications and tenant records on your WordPress site

Check which identity, income, reference, or contact fields you keep, which roles can open applicant and tenant screens, and whether exports or uploads expose them. Review retention of declined applications and whether backups include those tables. A membership paywall without rental applications is a different surface.

Hosted screening and optional connectors

Some landlord tools keep screening off-site. Optional maps, payments, SMS, or SMTP may share other data when enabled. A browser scan cannot inspect stored applications or server-to-server screening transfers.

Property-management and tenant setups

No paid placement. Site-hosted property tools appear first, followed by any vendor-connector group, then unreviewed rows. Site-hosted tools may still use optional map, payment, SMS, or SMTP connectors when enabled. Names are alphabetical within each group.

This is a small documentation sample of early-stage property-management and resident-portal plugins, not a survey of the whole landlord-software market.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Flat Renter Listing Management Backend

Documented landlord backend for renter records: personal information, contact details, identification documents, and family-member fields as a custom post type that the listing says is never displayed on the frontend. Admin PDF export of renter information is documented. No visitor-browser third-party hosts are cited. Retention after a declined application or move-out is not documented. Browser hosts have not been verified.

Renter identity documents stored in WordPress admin; frontend display off by designBrowser hosts not verifiedNot assessedNot tested
  • None
LeaseFox

Documented property-management suite with tenant tracking, online applications, invoicing, CSV import, and a password-protected tenant portal on the site WordPress install. The privacy section says LeaseFox does not collect, transmit, or store data outside your WordPress site by default (no diagnostics check-in). Optional Google Maps embeds (admin-configured API key) can send a property address to Google on public property detail pages when enabled. Paid Basic/Pro add-ons describe Stripe Auto Pay, Twilio SMS, e-signatures, and AI screening-application summaries; those paid connectors were not reviewed here. Retention or deletion of declined or abandoned applications is not documented. Browser hosts have not been verified for the free path.

Tenant applications and invoices stored on WordPress; declined-application retention not documentedBrowser hosts not verifiedNot assessedNot tested
  • None
Softtara Resident Management Portal

Documented resident/work-order portal (maintenance and inquiries, not a rental-application screener): stores resident and technician name, email, phone, apartment number, profile photo, work-order details, and up to five attachments per request in the WordPress database. Soft delete with trash/restore/permanent delete is documented for work orders. The listing says the plugin does not connect to any external API by default; optional custom SMTP (password encrypted at rest) may send notification email through an admin-chosen provider. Charts are self-hosted SVG. Retention keyed to lease end or rejected applicants is not documented because the free surface is resident operations, not applicant screening. Browser hosts have not been verified.

Resident accounts and work-order attachments on WordPress; optional SMTP when configuredBrowser hosts not verifiedNot assessedNot tested
  • None

What this table does and does not prove

This table describes documented property-management and resident-portal workflows, not tests of your site. Consent timing, whether access controls work, and exact retention of declined applications have not been assessed. Check which applicant fields you collect, who can open tenant tools, portals, exports, connectors, and whether backups include those tables when records are site-hosted.

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

Related pages

Scan your site for third-party requests

/wp-property-management-plugin-privacy