Great question, and we've seen this happening actually, when some payments-based features used in scoring, data leakage. We are not doing "hard" constraints on

Great question, and we've seen this happening actually, when some payments-based features used in scoring, data leakage. We are not doing "hard" constraints on this, but there are 2 ways for the user to identify this: first one is feature importance built automatically, so the user will see these features immediately second one is the process of building inference. The same data prep/transformation pipeline assumed to be used as API or for batch processing before model application, and at this point they will definitely realise that they just don't have these features yet for new customers!