• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • 😌 This community is user driven. Be polite with other users.
    • πŸ‘‰ Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales).
    • πŸ’Έ Purchase a Pro Subscription to get access to active software support and faster ticket response times.

Age Verification + Country Restrictions During Registration (Another Duplicated... but check)

Status
Not open for further replies.

akchev

Chevereto Member
Hello,

it is very important in the USA that websites have a min/max age and country restrictions for their site. Especially when dealing with content such as images and if social.

That said, please considering implementing a min/max age and country restrictions feature for the Admin to set so that they ensure their users are all of legal age or in countries they can provide such sites.

As said several times, dating back to 2014; this isn't just a cool feature to have. It's mandatory (in some countries)

E.g., Only allow people from USA (or whatever countries you allow) to join + min age is 18 years of age or older.

*In time i have ran across several adult sites that use Chevereto; my set-up is nonadult. However, consider this -- it should be built-in and not something we need custom work done for.

Thanks
 
While I like the idea and understand why it's needed for adult sites, a one size fits all implementation of this seems like it could be a problem. Adult images can easily be marked as NSFW and not shown unless the users chooses to turn them. A proposed solution would be to, when they select to turn on NSFW keep a database option that they confirm they are 18 or older. (Example: Select the option, a popup window asks if you're 18+ if you select Yes, then you can turn NSFW on and it's kept in the database that you've chosen that... if no then NSFW is not turned on).

This be enough to accommodate the legalities of it in a mixed SFW-NSFW site.

Secondary option, that can easily be coded as a cosmetic upgrade is to simple cookie-based popup asking if you're over 18 (as many porn sites do). This can be implemented without much work on the part of the site owner and won't need to be a 'core' feature.
 
"Our Service does not address anyone under the age of 13 ("Children").
We do not knowingly collect personally identifiable information from children under 13.
If you are a parent or guardian and you are aware that your Children has provided us with Personal Information, please contact us.
If we become aware that we have collected Personal Information from a children under age 13 without verification of parental consent, we take steps to remove that information from our servers."

Our tos & privacy clearly says that under 13 years old minors not allowed in out site.
 
"Our Service does not address anyone under the age of 13 ("Children").
We do not knowingly collect personally identifiable information from children under 13.
If you are a parent or guardian and you are aware that your Children has provided us with Personal Information, please contact us.
If we become aware that we have collected Personal Information from a children under age 13 without verification of parental consent, we take steps to remove that information from our servers."

Our tos & privacy clearly says that under 13 years old minors not allowed in out site.
TOS does not exempt children under US Law. Nudity still requires security checks or you can be liable. You must make a good faith effort to PREVENT them. A popup asking to Enter/Exit or a toggle with confirmation will work. A line in a file does not.
 
TOS does not exempt children under US Law. Nudity still requires security checks or you can be liable. You must make a good faith effort to PREVENT them. A popup asking to Enter/Exit or a toggle with confirmation will work. A line in a file does not.
Yeah Nude.js implementation would be nice πŸ™‚.
 
I think that the best thing is just enable/disable a cookie based warning message that you can customize because the age restriction depends on the jurisdiction and the content. In that way you could be "sure" that the visitor was at least warned about the content.
 
Do you have examples where I can see this age verification?
 
All websites containing visuals require you to be at least 13 years old (that's the law).

Now, if the website allows ages 13+ (E.g., 13 to 99) -- all profiles of people aged 13 to 17 must not be accessible by people 18+

*This means min age required, no? Yup!

Some countries have different policies btw.

However, not only is that not implemented...

but if your website is Adult oriented (lets just say even non-adult sites are because there is nothing implemented to control ANY aged people uploading adult content...) it must be 18+ AND you must have a 2257 USC Record Keeping Requirements statement (google it) ANDDD you will go to jail if no "policy" and/or min age feature is set.

THIS IS ALL required by law; why are we questioning it? **just curious**

(This isnt Facebook; it's literally a image hosting script, meaning... if anything were to have it, it's this)

I hope I made sense. Please consider it --- thanks!
 
Last edited:
I understand what you need, I requested real world examples that's all.
 
Status
Not open for further replies.
Back
Top