Privacy Policy

Last updated: September 2026

Data sent only when you click “Report”

When you explicitly click Report, the extension sends a diagnostic report to help debug problems. That report may include:

• Browser and user agent information
• Extension version and configuration version
• Site identifier (e.g. www.zillow.com)
• Sanitized page URL path — numeric IDs are stripped before sending (e.g. /indianapolis-in/, never a full listing URL)
• Listing card detection counts
• Detection-method statistics and data-availability counts
• The active CSS selector and the names of data fields found on the page — field names only, never their values
• An optional comment you type yourself

What is never included: property addresses, listing prices, saved searches, account credentials, contact information, browsing history, or any database of listings.

Anonymous usage measurement

To understand which real-estate markets the extension is used in — and how reliably it detects day counts in each — the extension sends a small anonymous event on a search results page: one when the page loads, and one if you run a filter. Each event contains:

• The event name (search_view when a search page loads, search_scan when you run a filter)
• A coarse market identifier derived from the search page, at city-and-state level only (for example indianapolis-in)
• A random installation identifier, generated locally on first run
• A random session identifier for the current search
• How many listing cards were found on the page, and — for search_scan — how many of them had a day count
• A timestamp

What this deliberately does not include: ZIP codes, ZPIDs or any property identifier, street addresses, the full page URL, individual property pages you open, your IP address, or your physical location. ZIP-only searches are not resolved to a market at all.

The installation identifier is a random value with no connection to you, your browser profile, or any account. It cannot be linked back to a person, is not shared across devices, and is deleted when you remove the extension. It exists only to avoid counting one person's repeated searches as many different users.

At most one of each event is sent per search. Scrolling, re-filtering, and page re-renders do not generate additional events.

Configuration updates

To keep working when listing sites change their markup, the extension periodically fetches a small configuration file (CSS selectors and data field names) from the developer's server, at most once every 30 minutes. This request contains no personal data and no information about the page you are viewing. As with any web request, the server receives your IP address as a normal part of delivering the response; it is not logged for tracking, profiling, or advertising.

How the data is used

Diagnostic data is used solely to identify and fix bugs in the extension. It is not sold, not used for advertising, and not used to build user profiles.

Where the data is stored

Diagnostic reports are transmitted to and stored on the developer's server and database provider. No data is shared with any other third party.

Normal use

All filtering, configuration caching, and settings storage happen within your browser using chrome.storage.local. Your filter settings and panel position never leave your device. Apart from the anonymous market measurement described above, no browsing activity or listing data is transmitted.

Contact

For questions about this policy, contact chromedomfilter@gmail.com.