Age verification is a complicated topic where no simple solution exists. I wish it did.
At a minimum, I think you need some kind of legal representation to tell you exactly where you sit in regard to compliance. The same could be said for questions related to 2257s in the US, model releases, etc. I'm not a lawyer, and I don't think many of the posters here are lawyers either.
None of the content you're showing appears to be blocked in the United States. So it seems they are doing some kind of geolocation work here. There are EU laws being discussed now, so maybe they're preemptively blocking locations they deem risky. Did you ask them?
Geolocation is something you can integrate at the server level and also at the backend level. There are various services that perform this, some for a fee, others are free (and there is an inherent risk in inaccuracy.)
Most of the systems that I have become familiar with that perform age verification as a service require a developer to integrate. Some software already has age verification integration as part of their system. How that works is up to them, and if you want something custom, generally you have to pay for it.
It's a really messy time for age verification, because there is no official, international, fully vetted standard.
|