Bitbucket timestamps code check-ins using user's PC Date/Time instead of using its own time reference from cloud

While working with bit-bucket, if the user changes his PC date/time to a future date and then does a commit, the commit uses user's PC date/time instead of a cloud date/time.
Later while reviewing the list of commits, one can see strange date entries in the version history with words like 'Tomorrow' appearing in the version history.
(See attached screen-shot)

Steps to reproduce:

1. Change local PC date/time to the next day
2. Perform a code check-in
3. Restore PC time to current date/time
4. Review version history in bitbucket. You will notice 'Tomorrow' against the check-in done

Possible resolution:
Check-ins should be time-stamped ith cloud sourced time reference instead of time reference from user's PC