The model of regulation-compliance is this. It's not really about the specifics. Consent, privacy, kyc... Those may be initial motives for regulation, but by th

The model of regulation-compliance is this. It's not really about the specifics. Consent, privacy, kyc... Those may be initial motives for regulation, but by the time these exist in the world, they are a set of standard, rigid "compliance" protocols. From formulation stage, it allows two parallel realities. One in which "consent" or whatnot have an intuitive meaning. Politicians and activists live here. One in which "consent" is a specification for a compliant "3rd party solution." Businesses live here. Once functional, the bank, website or other complying business can claim the rules were made up by the regulator, and the regulator can either claim to be successful or blame businesses for problems. Being unremarkable, by copying or using 3rd party comliance plugins is more important than respecting the regulation's intent. By the time consumers are affected, "consent" has a technical specification. It no longer has much actual meaning. Think of the hoops, paperwork, informed consent signatures and such that you deal with at a bank. All those things had some regulatory logic behind them initially. Employees at the bank think this is government-required paperwork. What it is is compliance.