Hi
I'm a developer working at www.realeastate.com.au in Australia. The team has recently noticed one of our data serving APIs (hosted as "pexa.realestate.com.au") was added to the EasyPrivacy block list about 11months ago (https://github.com/easylist/easylist/co ... 8473f6aea7).
This is causing issues serving our web experience due to the client-side rendering approach that we take. You can see this by going to https://www.realestate.com.au/vic/armadale-3143/ & clicking on one of the surrounding suburbs listed at the bottom of the page.
Can PEXA please be removed from the list? 
It is used to serve data related to property and suburbs on our site. It does not capture user data in any form.
Regarding https://www.realestate.com.au/sold/property-house-nsw-camperdown-135886518 (the page referenced when adding PEXA to the privacy list), this page makes a client-side request to PEXA in order to match the sale listing to our other site section & provide a link (for example - that listing matches to https://www.realestate.com.au/property/134-mallett-st-camperdown-nsw-2050).
We protect the API so you won't be able to check it directly yourself but you can use browser network tools to see how it is being used in the two pages.
Thanks!
Alyssa
