We are very much in support of this initiative, and your Nearmap information is secure.
Who is affected and how?
This change does not affect
Our MapBrowser Classic runs on HTTP and as such is subject to this user interface change. The only difference is the visual . Our login pages are and always have been HTTPS, our New MapBrowser is running only on HTTPS, and all our new APIs will support only HTTPS going forward.
The Google Chrome change is only the visual indicator of "Not Secure" in the URL bar, the underlying security of MapBrowser has not changed. no underlying changes to the information security were made. MapBrowser is as secure as it always has been.
The following URLs will show the new indicator:
We are focusing our energy on the New MapBrowser and new APIs, which among other improvements, will also be running fully on HTTPS.
Information from Google: