|
I think there is a little misinformation in this thread. I agree that age verification will have a net negative effect on the industry and I think webmasters will suffer financially for it. Then again, Discord is doing it in certain regions so it might be less impactful than we think.
However, both the age verification service (or Know Your Customer company,) and the team implementing that age verification service, have equal responsibility as to how effective AVS is. Not to mention that no matter who you go with, you need to do the research to ensure that it meets your legal requirements, since you are ultimately responsible for that.
With my software package, LoginBlue, and the two firms that I chose to integrate (so far,) iDenfy and VerifyMy, the user has a fairly seamless experience which is permanently tied to their user account.
Once they verify, unless there is some reason to void that verification, the user's "age status" is permanently tied to their account, and the age verification service is trusted to retain the proof, not my implementation.
Here's the flow I implemented: After they sign in, they are asked to two-factor, and after that, they are asked to verify their identity. I find that age estimation is kind of a worthless implementation and is not safe to use. I don't think this will work for everyone, and if you wanted to do something like this, you would need your lawyer to sign off on it.
There are a lot of poor implementations that I've come across, but as I said, AVS is half service selection, and half developer team implementation.
|