Privacy notice
LandBinder is designed for property screening, not owner prospecting. It does not use owner names or mailing lists to support unsolicited outreach.
Effective August 1, 2026
Information the service processes
Public browsing does not require an account. When you create an account or sign in to analyze or save land, we process your name, email address, password hash, boundaries you draw or upload, report names, map interactions, saved reports, buyer-intent selections, due-diligence task statuses and notes. Support submissions include your account email, category, message and optional report identifier. Operational records may include request times, provider outcomes, cache usage, coarse request metadata, and error codes. LandBinder does not store your plaintext password.
External data requests
To build a report, boundary coordinates, representative points, bounding boxes, or search radii may be sent to the government sources identified in the report. An optional market search sends its center, radius, active status, and land property type to the named paid provider only after you request the search.
How information is used
Information is used to create and restore reports, isolate saved work by account, respond to support and correction requests, prevent abuse, cache repeat requests, measure source availability, troubleshoot failures, and operate the service.
Cookieless site analytics
LandBinder uses a self-hosted Umami installation to understand aggregate page use and whether core product steps work. The analytics tracker uses no advertising cookies or cross-site profile. It records approved page views and event names such as a report start or export; search queries and URL fragments are excluded. LandBinder never sends property addresses, coordinates, boundary names, report identifiers, account emails, or evidence values to analytics. The tracker honors a browser's Do Not Track preference. Ordinary web-server security logs may still process network metadata for a limited operational period.
Private due-diligence documents
You may upload transaction and research documents to an account-scoped document room. These files and their metadata are used only for your due-diligence workspace. They are not added to public reports, market search, owner-contact products, or public analytics. Do not upload documents you are not authorized to store. Remove unnecessary personal information before uploading when practical.
Retention
Saved reports, due-diligence state and private documents remain until the associated saved area is deleted or a future account-retention policy applies. Deleting an uploaded document removes its stored object and metadata. Short-lived analysis-rate records are scheduled for seven-day retention. Provider and market operational records are scheduled for 90-day retention. Expired or revoked private-share revisions are scheduled for removal after 30 days. Resolved support requests are scheduled for removal after 180 days. Provider caches have their own stated expiration.
Owner information and outreach
The public-evidence report does not require owner names, owner phone numbers, or owner mailing addresses. The service is not intended to create owner contact lists or automate unsolicited messages.
Your controls
You can rename, duplicate, or delete saved areas, update checklist state, and add or remove private documents in the application. Deleting a saved area removes its saved analyses, buyer workspace, private due-diligence documents and associated job records. Some limited operational records may remain until their retention period expires.
Security and changes
Secrets are kept server-side, optional providers fail closed, and sensitive responses are not publicly cached. This notice may change as account, billing, sharing, or public-launch features are introduced; the effective date above will be updated.