This bug was already reported here: https://issuetracker.unity3d.com/is...tc-time-regardless-of-your-current-local-time Datetime.Now returns UTC times instead of local user times. I'd like to know if there is any estimated time of fix for this, as it's a major bug for us and breaks all our features relying on local user time. We're too far in using .NET to go back now. Quite surprised that it was reported back in August and not addressed yet, and that so few have voted on the issue. Is there any workaround that people have tried which have worked for them? I'm thinking if you grab the lat/long off the device using LocationServices, then use TimeZoneInfo to get the UTC offset, you can essentially calculate the local time, HOWEVER this requires extra location permissions on device which is really not ideal, and additionally this local time needs to be calculated before any other code is initialised. Advice is appreciated.