Last Updated: April 2026
This Privacy Policy explains how NSW Property Insight (“the Extension”) handles information when you use it to research Sydney property market data. Our goal is to be fully transparent about what we collect, why, and for how long.
When you click Analyze Market Match, the following data is sent to and stored on our secure backend (hosted on Render):
| Data field | Stored? | Why |
|---|---|---|
| Full property address | Yes | To look up suburb-level historical price benchmarks and calculate the Market Match Index. The full address is retained so that repeated queries for the same property can be deduplicated and suburb-level demand trends can be built accurately |
| Suburb (extracted from address) | Yes | To power suburb-level demand heat maps |
| Budget | Yes | To compare your target price against comparable suburb sales |
| Bedrooms (optional) | Yes, if provided | Helps select the right apartment price cluster for units and contributes to anonymised apartment-type tagging in future suburb reports |
| Hashed session ID | Yes | Your device generates an anonymous UUID and hashes it locally using SHA-256 before transmission. Only the hash is sent to our backend and used solely to enforce the 5 free checks per day limit. The hash cannot be reversed to identify you |
| Timestamp | Yes | To support 6-month data retention and time-series trend analysis |
Search records are aggregated across all users to produce suburb-level demand heat maps showing which Sydney suburbs are receiving research interest in real time.
We do not collect, store, or have access to:
Stored search records (full address, suburb, bedrooms, budget, hashed session ID, and timestamp) are retained for 6 months to maintain the relevance of market trend data, after which they are permanently and automatically deleted from our systems.
Calculated results such as the Market Match Index score, market sentiment, and clearance rate are never persisted — they are computed fresh on each request and exist only in your browser session.
Your local usage counter (chrome.storage.local) remains only on your device and is never synced to our servers.
The Extension stores the following data locally on your device only:
| Stored value | Purpose |
|---|---|
| Anonymous session ID | Randomly generated UUID used to count your daily free checks. Stored locally on your device; only its one-way SHA-256 hash is transmitted |
| Daily usage counter | Number of checks used today |
Neither value is used to identify you personally.
We use the following services solely to provide the Extension’s analytical functions:
| Service | Purpose | User data received |
|---|---|---|
| Render | Backend API hosting — all analysis requests are processed here | Address, suburb, budget, bedrooms (optional), hashed session ID |
| Google Places API (via our backend proxy) | Address autocomplete. Requests are proxied through our backend; the API key is never exposed to the browser | Address search string |
| Google Gemini API | Generates the plain-English “Quick Read” market summary shown in the result card | Address, budget, and aggregated statistical outputs (Market Match Index score, clearance rate, auction count, comparable sale details). No personally identifying information is included |
If you have questions about this policy, please contact us through the Chrome Web Store support link.
Disclaimer: This tool is for educational and research purposes only and does not constitute financial, legal, or real estate advice.