fwiw after some renaming I just noticed that it doesn't quite fit under privacy policy any more. I don't think it fits in any of the others (though maybe the Terms one), and a new section could be overkill.

I'll leave it to your judgement where it fits best.

@ThiefMaster it might not be quite perfect yet, but this is ready for a new round of reviews. See context in #5923

@ThiefMaster I've hit a snag on this while debugging something else and could use your advice:

This approach seems to fail for urls that have @allow_signed_url. In the intercepting signal there is a check for session.user, which calls indico.web.util's get_request_user, which will fail because g.rh is not yet set, so it can't actually see that the controller has _ALLOW_SIGNED_URL.

Is there a way to do this interception later, or a better way to check for the user at this stage?

Do you mean the time when _handle_terms_changed runs? If yes, you could move it into the RH class right after self._check_csrf()

Do you mean the time when _handle_terms_changed runs? If yes, you could move it into the RH class right after self._check_csrf()

Yeah, this works much better. It feels a little unclean, but I'll leave that to the review if it works out good enough :)

@ThiefMaster also friendly reminder for this comment: #5925 (comment)

All current review comments taken care of :)