Thanks @Team DEMP, I can understand that there are people who may want it to stay the same, and I would be happy for an option for people to switch the behaviour on and off if that's deemed a suitable alternative by @Nic Hubbard.
Logging caches on the web site also logs them with what I consider the "wrong" date as well - as, again, it logs the find with whatever the date and time are at GC HQ. For those of us "down under", this is quite often the "previous day" until late afternoon when the US catches up to the right day.
So, unless something can be added to the app to make it use the local date/time when logging a cache, it will always be logging them at the GC HQ date/time which completely throws any stats generated out, and also can screw up cache streaks as, while I may have found a cache "yesterday" and "today" my time, the "HQ time" may show them both being on the same day due to the time difference - this means going back on-line on the web site and manually editing cache logs to get them to be logged on the correct day. This was particularly painful the other day when I was using Cachly offline in a non-phone reception area all day and had to go back and edit 60+ cache logs individually to correct them all.
The Geosphere app appears to have some fix for this, and logs things at the local date/time it is told to. GSAK also seems to use the dates it is set to use as well from what I have seen. If I can just use one app to log everything correctly, then that'll make life much easier. I'm keen to try the "fixed" version in the beta @Nic Hubbard sent me tomorrow to see how it fares.