Skip to main content
LANDLORD RECORD

Privacy

Collect what is needed. Keep roles and purposes narrow.

This notice describes the privacy practices of the Landlord Record service. The product is built around public-record research and is not intended to become a broad personal-data directory.

Information you provide

Information generated by use of the service

Performance telemetry is designed so its dedicated performance table does not store the raw search query. Other operational records may contain property addresses or source records needed to provide the requested service.

Public-record information

Landlord Record may process information made available by government and other sanctioned public sources. Public availability does not remove the need to preserve context, documented role, source restrictions, or applicable privacy rights.

Browser storage

The service may use local storage and session storage for saved research, report-access tokens, comparison receipts, and related product state. Clearing browser storage can remove locally saved state and may affect access recovery.

Service providers

Infrastructure and payment providers process information on behalf of the service. The current payment flow uses Square for card handling and payment authorization, and the site is deployed using Netlify infrastructure. Additional operational providers may be used as the service evolves.

Requests and choices

Depending on where you live and which law applies, you may have rights to request access, correction, deletion, or other treatment of certain personal information. Use the contact form and select Privacy request. Landlord Record may need to verify the request and may retain records where legally permitted or required.

Data minimization

Landlord Record's product direction excludes broad phone, personal email, relatives, household-member, and current-resident people-search features. Tenant/current-resident information must not be inferred into a landlord role.

Changes to this notice

This notice may change as the product, vendors, and applicable requirements evolve. Material revisions should update the effective date and the checkout terms version where relevant.

Effective: August 31, 2026