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, including the public land catalog when enabled, 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, email-verification state, boundaries you draw or upload, report names, map interactions, saved reports and parcel-shortlist links, buyer-intent selections, due-diligence task statuses and notes. Support and beta-feedback submissions include the fields you choose to submit. Operational records may include allowlisted event names, request times, provider outcomes, cache usage, coarse request metadata, durations, and error codes. Product events do not contain email, property search text, addresses, geometry, coordinates, report evidence, Copilot questions or answers. LandBinder does not store your plaintext password.
Payment information
The free public-beta trial does not require a payment card and cannot automatically convert into a paid plan. LandBinder is not accepting payments and does not collect payment-card details. The account database can display an empty credit, entitlement and purchase-history ledger so the commercial workflow can be tested safely. If payments are introduced later, card details will be handled by a named payment processor rather than stored by LandBinder, and this notice will be updated before activation.
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. When you explicitly request a mapped parcel boundary, LandBinder sends the selected coordinate to the configured parcel source. When you search a supported official parcel-number connector, LandBinder sends the state, county, and parcel number you entered to that public record service. Owner names, owner contacts and mailing-address fields are not requested or exposed in LandBinder's parcel response. The optional nationwide catalog matcher requests only parcel geometry, provider and local parcel identifiers, jurisdiction codes, acreage, update date and dataset release from an allowlisted response. If an optional parcel map or basemap layer is enabled, its tile coordinates are sent as you pan and zoom. 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. Public catalog searches and page views read normalized stored records and do not make a new paid listing or parcel request. Professional listing-agent or office details, when licensed and available, are disclosed only after a bounded contact action and are not embedded in public page metadata.
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.
Account and support email
Account verification and password recovery use single-use expiring links. LandBinder stores only keyed hashes of those tokens. When transactional email is enabled, the destination address and message are sent to the named email-delivery processor solely to deliver the requested account message. A support submission is stored in LandBinder and may also be sent through that processor to the configured support mailbox, including the submitting email, selected category, optional report identifier, and message. Resetting a password revokes every earlier signed-in session.
Cookieless site analytics
LandBinder does not currently load a public analytics tracker. If the planned self-hosted Umami service is enabled, it will use no advertising cookies or cross-site profile and will record only approved page views and event names such as a report start or export; search queries and URL fragments will be excluded. LandBinder never sends property addresses, coordinates, boundary names, report identifiers, account emails, or evidence values to analytics, and the tracker will honor 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.
Private Concept Studio
If your account is invited to Concept Studio, LandBinder processes the selected saved analysis, concept prompt, normalized land-use brief, editable placement geometry, source-linked screening snapshot, generated variants and private-share controls to operate your project. Raw prompts, parcel-linked concepts, generated images and generated videos are not sent to product analytics, sold, used for advertising, or used to train or fine-tune a model. Rendering is local by default; an invited beta may use a disclosed video provider only after the applicable provider and privacy review. Provider inputs exclude the raw prompt, account identity, address, parcel number, GPS metadata and evidence text. Exports remove account identifiers, address, parcel number and GPS metadata; a non-personal provenance identifier and model information may remain in signed Content Credentials. A private share is created only when you request one and is revocable, non-indexed and expiring.
Retention
Saved reports, parcel-shortlist links, due-diligence state, private documents and Concept Studio project history remain until the associated project, saved property or account is deleted. Deleting a concept project removes its prompts, variants, artifacts and share links. Normalized public listing and parcel snapshots may be retained as permitted by the source agreement to preserve status history, corrections, attribution and inactive canonical records; provider takedowns and rights changes can suppress them. Short-lived analysis-rate records are scheduled for seven-day retention. Provider and market operational records are scheduled for 90-day retention. Expired account-action tokens are removed after a one-day grace period. Privacy-safe product events and resolved support or beta-feedback records are scheduled for removal after 180 days. Expired or revoked private-share revisions are scheduled for removal after 30 days. Provider caches have their own stated expiration.
Owner information and outreach
The public-evidence report and catalog do not require owner names, owner phone numbers, or owner mailing addresses. A land listing may identify its professional listing agent or office and, when permitted, provide the business contact details supplied by the listing source. That is separate from parcel ownership data. The service is not intended to create owner or professional contact lists, harvest contact details, or automate unsolicited messages.
Your controls
You can rename, duplicate, or delete saved properties, update checklist state, add or remove private documents, delete concept projects and revoke concept shares in the application. Deleting a saved property removes its saved analyses, buyer workspace, private due-diligence documents, concept projects and associated job records. The Account page provides password-confirmed deletion of the complete account, owner-scoped reports, histories, documents, concepts, feedback and private objects. Unlinkable security-rate records and aggregate account-deletion counts may remain until their documented 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.