Homi Metrics privacy policy

Last updated: 28 August 2026

Homi Metrics is a Chrome extension that adds sold-price, rent, and GP-score context to Rightmove listing pages, plus a local shortlist, a compare view, and Goblin's Dream Home.

This policy covers the whole extension: what it keeps on your device, what it sends over the network, and what it never touches. Questions go to homimetrics@gmail.com.

The short version

• Your shortlist, notes, tags, and Dream Home stay in your own browser. They are never uploaded.
• To show area statistics, the extension asks our own server about the postcode of the listing you are viewing. It does not say which listing you are on.
• Usage analytics are opt-in. The only thing recorded before you say yes is which way you answered: one event, carrying nothing that identifies you. Turning analytics back off deletes the identifier behind them.
• We never collect the listings you look at, what you write about them, or your browsing history.

If you have never been asked to turn analytics on, nothing has been collected from your browser.

What stays on your device

Everything below is held in Chrome extension storage on the browser profile you are using. There is no Homi Metrics account, no server-side copy, and no sync between your devices.

• Shortlist: for each saved listing, its Rightmove listing ID and URL, address, price, property facts, the statistics snapshot taken when you saved it, and the URL of the main listing photo.
• Notes and tags you write against a saved listing.
• Dream Home: which of the six pieces you have collected, and the source listing URL and photo URL behind each one.
• Preferences: your sort order, filters, compare selection, and whether you have dismissed an onboarding prompt.

Homi Metrics stores photo URLs, not copies of the images. Removing the extension, or clearing its data from Chrome, deletes all of it. We cannot recover it for you, because we never had it.

Area statistics requests

Sold prices, rent trends, and GP scores are not bundled with the extension, so it fetches them. When you open a supported listing page, the extension sends our own AWS endpoint:

• the postcode context you are looking at — the outward code, sector, or full postcode, depending on the scope you select
• the kind of query being run (sold prices or rent)

That is the whole request. No listing ID, no listing URL, no identifier, and nothing about you is attached. Like any web request, it reaches the server with your IP address; we do not use it to identify you or to build a profile, and it is not joined to analytics.

Usage analytics

The Chrome Web Store category

Under Google's Chrome Web Store data categories, Homi Metrics collects one category: User activity — clicks and interaction patterns inside the extension. No other category is collected.

What is collected

• The event name — the extension became active, a feature was used, or a panel errored
• Which feature was used
• Which extension surface it was used from — a listing page, the popup, or the compare page
• Which panel or render stage errored
• When the event happened, recorded as an event timestamp
• The extension version
• A randomly generated installation identifier, created only once you have opted in and the extension has something to send. The two answer events described below are the things sent without one: in place of an identifier each carries a fixed word, the same on every copy of the extension, which identifies nothing
• A timestamp-derived session identifier used to group events from one period of activity. It is not tied to your identity, and the session ends after 30 minutes of inactivity. The two answer events carry a random one instead, made for that single request and never stored.

What is never collected

• Listing IDs or listing URLs
• Postcodes
• Prices
• Your saved notes or tags
• Photo URLs
• Your browsing history, inside or outside Rightmove
• Your name, email address, or any other personal identifier

Those fields are the whole analytics payload. There is no way to reconstruct which properties you looked at from what we receive.

It is off until you turn it on

Analytics are opt-in. Homi Metrics asks once, on a Rightmove listing page. Until you answer, no installation identifier is created and no usage event is recorded or sent.

When you answer, the extension sends one event recording which way you answered — that somebody said yes, or that somebody said no. Nothing else. Neither event carries an installation identifier: that field holds a fixed word, identical on every copy of the extension, so the event cannot be linked to you, to your device, or to anything else you do. Nothing is stored in your browser to send it and nothing is read from your browser to build it, and there is no retry: if it does not get through, it is simply lost.

We send both to learn whether the prompt is working — a count of refusals means nothing without a count of the answers it is a share of. Counting the refusal rests on our legitimate interest, since someone who said no has consented to nothing; counting the acceptance is covered by the consent just given, and is sent the same anonymous way so that the two numbers can be compared. Like any web request, each reaches us with your IP address, which we do not use to identify you and do not join to anything else.

Beyond those two events, your consent is the only basis on which anything is collected — and saying yes does not by itself create your installation identifier. That is still made only when there is a first real usage event to send.

Choosing no is final — the extension keeps working, and it does not ask again.

Withdrawing consent

Open the Homi Metrics popup, choose Settings, and switch usage analytics off. When you do:

• the installation identifier and current session identifier are deleted
• any events still waiting to be sent are discarded
• nothing further is recorded or sent

If you later switch analytics back on, new installation and session identifiers are generated. They are not linked to the old ones, so the history does not follow you.

Where the data goes

Events are sent from the extension to our own endpoint on AWS, which forwards them to Google Analytics. The AWS step exists so the Google Analytics credential never ships inside the extension; it forwards events and does not keep its own copy. Once forwarded, the data is processed by Google under their terms.

How long it is kept

Google Analytics deletes event-level data after 14 months, which is the maximum retention its event data allows. We do not keep a separate copy.

Permissions

Homi Metrics requests these Chrome permissions:

• storage to keep your shortlist, Dream Home, preferences, and analytics consent in your browser
• alarms to retry delivery of opt-in analytics after a temporary delivery failure

The alarms permission only wakes the extension's background worker for that retry. It does not read browser history or grant access to another site.

It also requests access to:

• rightmove.co.uk so it can read a supported listing page you open
• d1pnq63bv3cggs.cloudfront.net, our statistics endpoint, so it can fetch area statistics
• tm52ga8tzb.execute-api.eu-west-2.amazonaws.com, our analytics ingest endpoint, so it can send usage analytics after you opt in

It does not request access to your browsing history or to any other site.

Changes to this policy

When this policy changes, the date at the top changes with it. The version published here is the one in force; there is no earlier version still applying to data already collected.

Contact

Email homimetrics@gmail.com with any question about this policy or about the data described here.