...
Currently, there’s a toggle on sanity for the following static pages: Terms of Service, Privacy Policy, and Privacy Policy RBI. It turns the user acceptance required, and if it’s toggled on, any changes on the three pages will generate a new popup to be accepted by the user.
...
If this feature flag is turned on and any of these dates are in the future compared against sanity upadted_at date, the date from sanity will be ignored, the date from the feature flag will be considered a priority, and in comparison with the DynamoDB (database), it will look like the user has still a new version of the terms to accept.
Workaround
There is a solution for this case: we can consider the date from the feature flag to be in DynamoDB as well, but it can impact in an unethical way because it will look like the user has accepted some agreements that didn't exist.