Just tested 10.1.7 GDPR release and it works well.

Can you provide steps to reproduce the issue for the time zone issue you are seeing?

1. Fly to a different time zone (;-)) India for instance
2. Enable new Terms and Conditions and click on Update
3. Register a new user immediately

You will see that the new user is prompted the agreement twice

1. During the regular sign up
2. When entering after signed it says: You need to agree to the new terms

1. Fly to a different time zone (;-)) India for instance
2. Enable new Terms and Conditions and click on Update
3. Register a new user immediately

You will see that the new user is prompted the agreement twice

1. During the regular sign up
2. When entering after signed it says: You need to agree to the new terms

None of the dates are provided by the user--all retrieved and stored in UTC. The only way I can reproduce this is if I'm in a multi-server environment with mismatched server clocks and update the terms on the server that is in the future relative to other servers so that when the user is created the current UTC time is still earlier than the UTC time of the server on which I updated the terms of service date.

The date check is currently precise to the millisecond. After accepting the terms in your step 2, are you prompted again? If it were a timezone issue, I would expect you to be asked repeatedly until the user's timezone catches up to the server's timezone.