GDPR compliance

[Wayne Luke]

Hey Wayne,

Is this something that we should expect soon for vb5 connect? Do you know of the time frame to see this? Lastly, What version number should we expect these changes to appear in?

https://www.vbulletin.com/forum/foru...3-release-here

Data Compliance would be in 5.4.3. This will be the next release of vBulletin and should be available in July.

[amart79196]

In addition to the above, vBulletin 5 is receiving a GDPR compliance sub-system with GEO-Location and Guest compliance support in the next version to be released. The Mobile Apps are also being updated to work with GDPR when used with vBulletin 5.

Hey Wayne,

Is this something that we should expect soon for vb5 connect? Do you know of the time frame to see this? Lastly, What version number should we expect these changes to appear in?

[Wayne Luke]

This is actually for both.

[gsk8]

This is for new registrations, right? How does one set up a way to do the same for existing users?

They wouldn't be able to save their profile unless they update the field.

If it were my site I would:

1. Create a Notice stating that the new field is required (regardless of location).
2. Give a deadline to comply.
3. If they don't set it to Yes by the deadline, move them to a usergroup that doesn't have access to post in the site.
4. Show another notice to this Usergroup so they are reminded of GDPR.
5. If they don't answer within a set time period, say 30 days, update their username to be non-identifying (to update posts) and then delete their account.

[jagtpf]

Delighted, except it was Wayne who posted that.

My pleasure, I like to spread happiness around

(as they say in the UK, should have gone to Specsavers!)

[Mark.B]

Thanks Mark - I think!

Delighted, except it was Wayne who posted that.

[jagtpf]

They wouldn't be able to save their profile unless they update the field.

If it were my site I would:

1. Create a Notice stating that the new field is required (regardless of location).
2. Give a deadline to comply.
3. If they don't set it to Yes by the deadline, move them to a usergroup that doesn't have access to post in the site.
4. Show another notice to this Usergroup so they are reminded of GDPR.
5. If they don't answer within a set time period, say 30 days, update their username to be non-identifying (to update posts) and then delete their account.

Thanks Wayne - I think!

[Wayne Luke]

They wouldn't be able to save their profile unless they update the field.

If it were my site I would:

1. Create a Notice stating that the new field is required (regardless of location).
2. Give a deadline to comply.
3. If they don't set it to Yes by the deadline, move them to a usergroup that doesn't have access to post in the site.
4. Show another notice to this Usergroup so they are reminded of GDPR.
5. If they don't answer within a set time period, say 30 days, update their username to be non-identifying (to update posts) and then delete their account.

[jagtpf]

".....you can already create custom profile fields and require that they are answered at registration and/or login."

I can understand how that works with registration, but how does it work for existing members?
Or is it simply that adding a new profile field to the existing ones automatically 'forces' a field to be responded to. But then how do we cater for those outside the EU?

[kgroneman]

Thanks Wayne. That's what I need to know. - Kim

[Wayne Luke]

vBulletin 4 is end of life and will not be receiving updates for for GDPR compliance. With the software, you can already create custom profile fields and require that they are answered at registration and/or login. You can use the phrase system to update the rules of your site and link to your privacy policy. You can also add a privacy policy under the Site Name / URL / Contact Details section of the site.

In addition to the above, vBulletin 5 is receiving a GDPR compliance sub-system with GEO-Location and Guest compliance support in the next version to be released. The Mobile Apps are also being updated to work with GDPR when used with vBulletin 5.

[kgroneman]

I did some searching of the forums and blogs here but didn't see anything that answers my question of how GDPR will/should be handled in vBulletin. Are there any patches or updates in 4x or any other version of vBulletin that addresses or helps with GDPR compliance? Is it as simple as you find the user, remove them, and let their content be assigned to an anonymous user? Thanks in advance for any thoughts or direction on this. - Kim