MMarket Rights Lab
Privacy

Clear data handling for property intake.

How Market Rights Lab handles property URLs, buyer contact details, browser logs, saved browser data, listing help, PDFs, and admin logging.

Updated June 15, 2026 ~3 min read 7 sections

1What We Collect

When you use the portal, we may collect the property URL you enter, listing facts returned by the property helper, buyer contact details you submit for a report request, local workflow events such as PDF generation, and technical details such as browser user agent and a hashed IP value.

Buyer email addresses and phone numbers are minimized in operational logs where possible. The admin log keeps email domain and phone last four digits rather than the full contact details. Netlify Forms and the server-side match request workflow may still store the full report request you intentionally submit so Market Rights Lab can respond and route the file.

2How Listing Help Works

The server first tries to read public listing facts. If a listing site blocks that read, the portal can ask you to help with a few clear choices:

  • Try from this browser: asks your browser to read the listing when the source website allows it.
  • One-click page snapshot: runs only when you choose it on the listing page you are already viewing and sends the visible listing snapshot to Market Rights Lab for fact review.
  • Paste listing text: lets you paste page source, saved HTML, or visible listing text into the portal.
  • Approved reading service: when you leave the consent box enabled, the listing URL may be sent to a configured reading service to recover public page text.
  • Smart fact review: when the consent box is enabled and a server-side review key is configured, captured listing evidence may be sent to the configured review provider to structure property facts. Buyer email and phone are not sent to the property reader.
  • Trusted property records: when a licensed provider key is configured, the reader may use the property address to request property records, active listing facts, or valuation estimates. Buyer email and phone are not sent to the property data provider.
Listing-help results are intake aids. Confirm listing facts before relying on savings estimates, reports, or matching decisions.

3Local Storage

The portal stores recent property-read memory and local admin events in your browser so repeated reads can be faster and so you can see local activity before server persistence is enabled. You can clear these records from the admin console or your browser settings.

4Server Logs And Persistence

Market Rights Lab can store sanitized events such as page views, property-link checks, browser-assisted reads, PDF generation, and report requests. Match requests may store the buyer contact details and savings file you intentionally submit. Persistent global logging and matching use server-only database credentials, access-controlled tables, and no public client policies.

5How We Use Information

We use information to build buyer savings files, improve property-read quality, diagnose blocked listing pages, respond to report and match requests, operate the admin console, and improve the buyer intake workflow.

6What We Do Not Do

We do not treat reader output as legal, tax, lending, brokerage-compliance, or investment advice. We do not guarantee savings, below-list pricing, NEGOTIATOR® availability, financing outcomes, or settlement outcomes.

7Contact

For privacy questions, contact info@marketrightslab.com.