I think the point the member was raising earlier was about how this would impact the practice. If I correctly understand the example reference made, there's already an existing payment system that would manage these issues. However, of course, the point the department is trying to raise here is that the payment processing system is predicated on our system of laws, including PIPEDA. In other words, PIPEDA, in the way that it's currently constructed, and the CPPA, in the way it was proposed to be put forward, enable these existing systems and processes when they are appropriate, lawful and rely on appropriate uses of consent.
The point that I think Mr. Schaan was raising earlier is that if we modify the definition of “sensitive information” in the way that's being proposed by the BQ subamendment, which the committee is considering right now, it would obviate the ability for those payment processing systems to rely on the current approaches they use. That's why it's particularly critical that we get the definition of “sensitive information” right.
I'll refer the committee back to the OPC's preferred formulation on this, which is to start with a reference to the notion that it depends on context. The context of the collection, use or disclosure is critical. Following that, we could put forward a list that is not exhaustive or exclusive and that gives an indication of the types of zones we're talking about. The current formulation of the BQ subamendment does not provide for the contextual analysis, nor does it provide any space for considerations of what could be on the list. It is, as Mr. Schaan already pointed out, a firm and final listing.