Technical debt like knowingly shipping privileged information to the client by design? I mean, it is true that 'perfect' is the enemy of the good. But 'terrible

Technical debt like knowingly shipping privileged information to the client by design? I mean, it is true that 'perfect' is the enemy of the good. But 'terrible' is also the enemy of the good. I would question whether a computerized test with these problems is actually better than a paper test. But more than that, I would question whether people have an obligation to make other products worse just to accommodate bad coding. I don't think anyone is demanding perfection by (correctly) pointing out that not designing a product to deliberately leak secure information is kind of the bare minimum bar in a secure testing environment.