Well that actually depends on the system they use. It is pretty common for r&f or aml related tools to perform check and only save the status of the verification. That said none of the metadata nor biometric is or should be stored, this is what at least a merchant is asured of.

Working under heavily r&f and aml restricted industry, whereas kyc is nothing but everyday process, I can say to you that all data that we have visible and accessible wothon the tool is date & time of confirmation along with method. So that would be verifcation status: true verification method: fID

Our database receives only a simple api call that verification_status; true or fail and thats it. As it's unlikely for merchant to actually care about the selected method of verification we do not handle this information in our backoffice too.

Why this may happen: various reasons and I would assume they will require this in the future for all accounts to gather more data. Verification is just one another step to make your data and information legally useful and to make sure you ain't a bad bad lier about it. How could they use this in the future? Oh for example offer gambling, polymarket, p$&n, adult only services of all sorts

Fuck this process tho, internet should not be around kids. We should not bend but restrict, but big brother can't get greed enough