This is needed for case when there is a gap between publishing policy and running script, if within this time range eg. a new user will signs in, we don't want to force him to do it again.
If this is too minor case and there is no possibility this can be removed.

I assume that as in D5309 this one is also intended to be one-time script so I am not going to pursue my idea of iterating over policies array. Nevertheless defining const policy = policyTypes.tosAndPrivacyPolicy (specific policy) and using it in function called forcePolicyAcknowledgment (suggests policies in general) doesn't seem right to me. We should either call this function forceTosAndPrivacyPolicyAcknowledgement or parameterize it with policy.

I assume that as in D5309 this one is also intended to be one-time script so I am not going to pursue my idea of iterating over policies array. Nevertheless defining `

It's not a one-time script, it will be executed every time a policy will be updated and we will need another confirmation from users (I don't think all policies will be updated at once that's why there is no iterating).

const policy = policyTypes.tosAndPrivacyPolicy` (specific policy) and using it in function called forcePolicyAcknowledgment (suggests policies in general) doesn't seem right to me. We should either call this function forceTosAndPrivacyPolicyAcknowledgement or parameterize it with policy.

Looking through other scripts in keyserver I think this is the way of parametrization, by setting a const and then running a script.

Thanks! Will keep this in mind, my bad for not search trough the codebase deep enough to find patterns we should use.