Matt

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Do you have a community but are looking to move to a more modern and feature rich platform?
There's a lot of ways Invision Community can breathe new life into your community. With our engagement features, advanced promotion features and mobile ready responsive themes, your members are going to love the changes.
Invision Community can power your entire site, from the content management front end right through to your download areas and shopping carts.
Imagine not having to juggle a dozen plug-ins and make several different applications talk to each other.
We offer a range of migration tools for vBulletin, xenForo, phpBB, Vanilla, bbPress and more. These tools convert your data such as members, passwords, forums, topics, posts and more across to Invision Community.
But first, let's look at how to make your migration a success.
Take our demo for a spin
Hands down the best way to get a feel for Invision Community is to take out a free demo. Once you are comfortable with the suite and know what it can do, the more confident you will be in discussing it with your members.
There's a lot of functionality to discover. Keep in touch with our sales team to get the most from the demo.  We recommend that you consider three uses.
Your community. Look at how they will settle in with the new interface and how they will use the new features on offer.
Your moderators. Take a moment to look in the Moderator Control Panel. Run through all the tools that are available, such as the warning system and content review system.

Moderator Tools
Your administrators. Probably the largest change between platforms will be in the Admin Control Panel. It's worth spending a little time getting familiar with it and looking at what's new, and where common tools are such as forum and member management.

Tip: Invision Community's Admin Control Panel has a global search bar to look for settings, members, invoices and more. If you ever feel a little lost, enter in what you're looking for.
Make your plan
Using the demo and speaking to our sales team will help you draw up a migration plan. You'll know which apps you'll need, and what data can be migrated over.
You may want to browse the marketplace to look for apps, plugins and themes to extend the functionality even further.

Tip: We offer a VIP migration service where we work closely with you to draw up your plan and take care of the conversion for you.
Educate your community
Keep your community up to date with your migration plan. Show them the platform they'll be using. Take videos and screenshots showing them the exciting new features coming soon. Make it a positive and fun experience.
Post something new every few days to get your community used to the idea and get them involved by asking them if they have any questions. Our sales and support teams are here to help you if you have any further questions at this point.
Getting the majority of your community excited about the change is the best way to make the transition a smooth one.
Make sure you explain the benefits of the switch too. If there's a good reason for it, your community will get behind it quickly.
Some benefits may be:
It works better on your mobile device and tablets, so you don't need to struggle with pinch and zoom to get around.

Mobile ready out of the box
The built in embed system allows you to post images, YouTube videos more easily and you can preview it instantly as you type.
The crowd sourced moderation makes reporting bad content more beneficial. It'll help to keep the community clean from undesirable comments and moving a positive direction.
More features on the way. Invision Community is always adding new functionality based on our customers' wishes. These releases happen often so there's always something to be excited about.
Pick a day
The best migrations are planned down to the date and time when the data conversion will occur. Our team can give you a rough idea of how long the data conversion will take. It will vary but we can give you a ballpark. 
Your members will feel happy knowing what is going to happen and when. There will be some downtime while the data is converted, so it's always best to announce this well ahead of time.
Set up a test site
Once you are committed to switching, set up a test site. A single Invision Community license can be used for a development installation as well as a live installation.
This is the perfect time to work on your theme and look at any tweaks you'd like to make.
Invite in your team and a trusted few from your community to offer feedback and advice. It's worth taking the time here to make sure everything is perfect for when you do the final conversion.
Make it comfortable
Take some time to theme your new Invision Community so it has a similar look and feel to your existing community. Change resistant members will feel more comfortable if there are areas that are familiar to them.
Ensuring your branding is up, and the colours match what you had before is a good start.
The easy mode theme editor is a great place to start.
Mind your language!
There are always little differences in the interface language that may throw some of your older members off. For example, some systems use "threads" instead of topics and "messages" instead of posts.

The easy language editor
Invision Community has a built in translation system so you can change our interface language to match your existing site.
Help your members
Set up a temporary questions and answer forum where your members can ask how the new system works and give you feedback.
Pin a handful of topics explaining where common items are now, such as how to edit your profile, how to send personal messages, how to mark the site as read and so on. Think about the daily activities your members make and explain how to do them with Invision Community.
You can use the pre-move time to ask your community what actions they do daily and may need assistance with on the new platform.
Be patient
Some of us dislike change. We are creatures of habit. You may find some members are very resistant. That's OK, they'll come around in time as long as you continue to make them feel valued and understood. Take the time to explain how the new system works and what the benefits of Invision Community are.
In our experience, members love the following Invision Community features:
Notifications
Invision Community has a variety of granular notification options, from browser to email so you're sure to not miss a thing.
Mobile Friendly
We're mobile friendly right out of the box. Our theme has a responsive framework, which means that it resizes perfectly to any device you're using. No need for extra themes or styles, it's all baked in.
Gamification
We all love a little friendly competition don't we? Invision Community has features like the leaderboard and member titles to reward activity. Who doesn't want to win the day?

 
Reactions
Liking content is fun, but being able to express thanks, laughter and more is even better. It's all baked into the system ready to use.
Educate your team
Invision Community has a whole host of moderation tools that your team will love as it makes their daily routines much easier.
From the comprehensive warning system, to the crowd sourced moderation feature, which can automatically hide content and notify moderators once it has been reported multiple times, Invision Community makes your moderators lives easier.
The best approach is to pin topics in a team area that explains how to use these new features and where to find them.
Summary
Investing in a new community platform and migrating your community across is a big decision. With the right planning and forethought, it will be a smooth and positive migration with lots to look forward to once complete.
We offer free conversion tools for you to use, or we offer a VIP conversion service where we take care of it for you and you get one-to-one help and support throughout the process.
We'd love to hear from those who have successfully migrated across from other platforms and how they made it a positive experience for their members.

 

Do you have a community but are looking to move to a more modern and feature rich platform?
There's a lot of ways Invision Community can breathe new life into your community. With our engagement features, advanced promotion features and mobile ready responsive themes, your members are going to love the changes.
Invision Community can power your entire site, from the content management front end right through to your download areas and shopping carts.
Imagine not having to juggle a dozen plug-ins and make several different applications talk to each other.
We offer a range of migration tools for vBulletin, xenForo, phpBB, Vanilla, bbPress and more. These tools convert your data such as members, passwords, forums, topics, posts and more across to Invision Community.
But first, let's look at how to make your migration a success.
Take our demo for a spin
Hands down the best way to get a feel for Invision Community is to take out a free demo. Once you are comfortable with the suite and know what it can do, the more confident you will be in discussing it with your members.
There's a lot of functionality to discover. Keep in touch with our sales team to get the most from the demo.  We recommend that you consider three uses.
Your community. Look at how they will settle in with the new interface and how they will use the new features on offer.
Your moderators. Take a moment to look in the Moderator Control Panel. Run through all the tools that are available, such as the warning system and content review system.

Moderator Tools
Your administrators. Probably the largest change between platforms will be in the Admin Control Panel. It's worth spending a little time getting familiar with it and looking at what's new, and where common tools are such as forum and member management.

Tip: Invision Community's Admin Control Panel has a global search bar to look for settings, members, invoices and more. If you ever feel a little lost, enter in what you're looking for.
Make your plan
Using the demo and speaking to our sales team will help you draw up a migration plan. You'll know which apps you'll need, and what data can be migrated over.
You may want to browse the marketplace to look for apps, plugins and themes to extend the functionality even further.

Tip: We offer a VIP migration service where we work closely with you to draw up your plan and take care of the conversion for you.
Educate your community
Keep your community up to date with your migration plan. Show them the platform they'll be using. Take videos and screenshots showing them the exciting new features coming soon. Make it a positive and fun experience.
Post something new every few days to get your community used to the idea and get them involved by asking them if they have any questions. Our sales and support teams are here to help you if you have any further questions at this point.
Getting the majority of your community excited about the change is the best way to make the transition a smooth one.
Make sure you explain the benefits of the switch too. If there's a good reason for it, your community will get behind it quickly.
Some benefits may be:
It works better on your mobile device and tablets, so you don't need to struggle with pinch and zoom to get around.

Mobile ready out of the box
The built in embed system allows you to post images, YouTube videos more easily and you can preview it instantly as you type.
The crowd sourced moderation makes reporting bad content more beneficial. It'll help to keep the community clean from undesirable comments and moving a positive direction.
More features on the way. Invision Community is always adding new functionality based on our customers' wishes. These releases happen often so there's always something to be excited about.
Pick a day
The best migrations are planned down to the date and time when the data conversion will occur. Our team can give you a rough idea of how long the data conversion will take. It will vary but we can give you a ballpark. 
Your members will feel happy knowing what is going to happen and when. There will be some downtime while the data is converted, so it's always best to announce this well ahead of time.
Set up a test site
Once you are committed to switching, set up a test site. A single Invision Community license can be used for a development installation as well as a live installation.
This is the perfect time to work on your theme and look at any tweaks you'd like to make.
Invite in your team and a trusted few from your community to offer feedback and advice. It's worth taking the time here to make sure everything is perfect for when you do the final conversion.
Make it comfortable
Take some time to theme your new Invision Community so it has a similar look and feel to your existing community. Change resistant members will feel more comfortable if there are areas that are familiar to them.
Ensuring your branding is up, and the colours match what you had before is a good start.
The easy mode theme editor is a great place to start.
Mind your language!
There are always little differences in the interface language that may throw some of your older members off. For example, some systems use "threads" instead of topics and "messages" instead of posts.

The easy language editor
Invision Community has a built in translation system so you can change our interface language to match your existing site.
Help your members
Set up a temporary questions and answer forum where your members can ask how the new system works and give you feedback.
Pin a handful of topics explaining where common items are now, such as how to edit your profile, how to send personal messages, how to mark the site as read and so on. Think about the daily activities your members make and explain how to do them with Invision Community.
You can use the pre-move time to ask your community what actions they do daily and may need assistance with on the new platform.
Be patient
Some of us dislike change. We are creatures of habit. You may find some members are very resistant. That's OK, they'll come around in time as long as you continue to make them feel valued and understood. Take the time to explain how the new system works and what the benefits of Invision Community are.
In our experience, members love the following Invision Community features:
Notifications
Invision Community has a variety of granular notification options, from browser to email so you're sure to not miss a thing.
Mobile Friendly
We're mobile friendly right out of the box. Our theme has a responsive framework, which means that it resizes perfectly to any device you're using. No need for extra themes or styles, it's all baked in.
Gamification
We all love a little friendly competition don't we? Invision Community has features like the leaderboard and member titles to reward activity. Who doesn't want to win the day?

 
Reactions
Liking content is fun, but being able to express thanks, laughter and more is even better. It's all baked into the system ready to use.
Educate your team
Invision Community has a whole host of moderation tools that your team will love as it makes their daily routines much easier.
From the comprehensive warning system, to the crowd sourced moderation feature, which can automatically hide content and notify moderators once it has been reported multiple times, Invision Community makes your moderators lives easier.
The best approach is to pin topics in a team area that explains how to use these new features and where to find them.
Summary
Investing in a new community platform and migrating your community across is a big decision. With the right planning and forethought, it will be a smooth and positive migration with lots to look forward to once complete.
We offer free conversion tools for you to use, or we offer a VIP conversion service where we take care of it for you and you get one-to-one help and support throughout the process.
We'd love to hear from those who have successfully migrated across from other platforms and how they made it a positive experience for their members.

 

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

Do you have a community but are looking to move to a more modern and feature rich platform?
There's a lot of ways Invision Community can breathe new life into your community. With our engagement features, advanced promotion features and mobile ready responsive themes, your members are going to love the changes.
Invision Community can power your entire site, from the content management front end right through to your download areas and shopping carts.
Imagine not having to juggle a dozen plug-ins and make several different applications talk to each other.
We offer a range of migration tools for vBulletin, xenForo, phpBB, Vanilla, bbPress and more. These tools convert your data such as members, passwords, forums, topics, posts and more across to Invision Community.
But first, let's look at how to make your migration a success.
Take our demo for a spin
Hands down the best way to get a feel for Invision Community is to take out a free demo. Once you are comfortable with the suite and know what it can do, the more confident you will be in discussing it with your members.
There's a lot of functionality to discover. Keep in touch with our sales team to get the most from the demo.  We recommend that you consider three uses.
Your community. Look at how they will settle in with the new interface and how they will use the new features on offer.
Your moderators. Take a moment to look in the Moderator Control Panel. Run through all the tools that are available, such as the warning system and content review system.

Moderator Tools
Your administrators. Probably the largest change between platforms will be in the Admin Control Panel. It's worth spending a little time getting familiar with it and looking at what's new, and where common tools are such as forum and member management.

Tip: Invision Community's Admin Control Panel has a global search bar to look for settings, members, invoices and more. If you ever feel a little lost, enter in what you're looking for.
Make your plan
Using the demo and speaking to our sales team will help you draw up a migration plan. You'll know which apps you'll need, and what data can be migrated over.
You may want to browse the marketplace to look for apps, plugins and themes to extend the functionality even further.

Tip: We offer a VIP migration service where we work closely with you to draw up your plan and take care of the conversion for you.
Educate your community
Keep your community up to date with your migration plan. Show them the platform they'll be using. Take videos and screenshots showing them the exciting new features coming soon. Make it a positive and fun experience.
Post something new every few days to get your community used to the idea and get them involved by asking them if they have any questions. Our sales and support teams are here to help you if you have any further questions at this point.
Getting the majority of your community excited about the change is the best way to make the transition a smooth one.
Make sure you explain the benefits of the switch too. If there's a good reason for it, your community will get behind it quickly.
Some benefits may be:
It works better on your mobile device and tablets, so you don't need to struggle with pinch and zoom to get around.

Mobile ready out of the box
The built in embed system allows you to post images, YouTube videos more easily and you can preview it instantly as you type.
The crowd sourced moderation makes reporting bad content more beneficial. It'll help to keep the community clean from undesirable comments and moving a positive direction.
More features on the way. Invision Community is always adding new functionality based on our customers' wishes. These releases happen often so there's always something to be excited about.
Pick a day
The best migrations are planned down to the date and time when the data conversion will occur. Our team can give you a rough idea of how long the data conversion will take. It will vary but we can give you a ballpark. 
Your members will feel happy knowing what is going to happen and when. There will be some downtime while the data is converted, so it's always best to announce this well ahead of time.
Set up a test site
Once you are committed to switching, set up a test site. A single Invision Community license can be used for a development installation as well as a live installation.
This is the perfect time to work on your theme and look at any tweaks you'd like to make.
Invite in your team and a trusted few from your community to offer feedback and advice. It's worth taking the time here to make sure everything is perfect for when you do the final conversion.
Make it comfortable
Take some time to theme your new Invision Community so it has a similar look and feel to your existing community. Change resistant members will feel more comfortable if there are areas that are familiar to them.
Ensuring your branding is up, and the colours match what you had before is a good start.
The easy mode theme editor is a great place to start.
Mind your language!
There are always little differences in the interface language that may throw some of your older members off. For example, some systems use "threads" instead of topics and "messages" instead of posts.

The easy language editor
Invision Community has a built in translation system so you can change our interface language to match your existing site.
Help your members
Set up a temporary questions and answer forum where your members can ask how the new system works and give you feedback.
Pin a handful of topics explaining where common items are now, such as how to edit your profile, how to send personal messages, how to mark the site as read and so on. Think about the daily activities your members make and explain how to do them with Invision Community.
You can use the pre-move time to ask your community what actions they do daily and may need assistance with on the new platform.
Be patient
Some of us dislike change. We are creatures of habit. You may find some members are very resistant. That's OK, they'll come around in time as long as you continue to make them feel valued and understood. Take the time to explain how the new system works and what the benefits of Invision Community are.
In our experience, members love the following Invision Community features:
Notifications
Invision Community has a variety of granular notification options, from browser to email so you're sure to not miss a thing.
Mobile Friendly
We're mobile friendly right out of the box. Our theme has a responsive framework, which means that it resizes perfectly to any device you're using. No need for extra themes or styles, it's all baked in.
Gamification
We all love a little friendly competition don't we? Invision Community has features like the leaderboard and member titles to reward activity. Who doesn't want to win the day?

 
Reactions
Liking content is fun, but being able to express thanks, laughter and more is even better. It's all baked into the system ready to use.
Educate your team
Invision Community has a whole host of moderation tools that your team will love as it makes their daily routines much easier.
From the comprehensive warning system, to the crowd sourced moderation feature, which can automatically hide content and notify moderators once it has been reported multiple times, Invision Community makes your moderators lives easier.
The best approach is to pin topics in a team area that explains how to use these new features and where to find them.
Summary
Investing in a new community platform and migrating your community across is a big decision. With the right planning and forethought, it will be a smooth and positive migration with lots to look forward to once complete.
We offer free conversion tools for you to use, or we offer a VIP conversion service where we take care of it for you and you get one-to-one help and support throughout the process.
We'd love to hear from those who have successfully migrated across from other platforms and how they made it a positive experience for their members.

 

Do you have a community but are looking to move to a more modern and feature rich platform?
There's a lot of ways Invision Community can breathe new life into your community. With our engagement features, advanced promotion features and mobile ready responsive themes, your members are going to love the changes.
Invision Community can power your entire site, from the content management front end right through to your download areas and shopping carts.
Imagine not having to juggle a dozen plug-ins and make several different applications talk to each other.
We offer a range of migration tools for vBulletin, xenForo, phpBB, Vanilla, bbPress and more. These tools convert your data such as members, passwords, forums, topics, posts and more across to Invision Community.
But first, let's look at how to make your migration a success.
Take our demo for a spin
Hands down the best way to get a feel for Invision Community is to take out a free demo. Once you are comfortable with the suite and know what it can do, the more confident you will be in discussing it with your members.
There's a lot of functionality to discover. Keep in touch with our sales team to get the most from the demo.  We recommend that you consider three uses.
Your community. Look at how they will settle in with the new interface and how they will use the new features on offer.
Your moderators. Take a moment to look in the Moderator Control Panel. Run through all the tools that are available, such as the warning system and content review system.

Moderator Tools
Your administrators. Probably the largest change between platforms will be in the Admin Control Panel. It's worth spending a little time getting familiar with it and looking at what's new, and where common tools are such as forum and member management.

Tip: Invision Community's Admin Control Panel has a global search bar to look for settings, members, invoices and more. If you ever feel a little lost, enter in what you're looking for.
Make your plan
Using the demo and speaking to our sales team will help you draw up a migration plan. You'll know which apps you'll need, and what data can be migrated over.
You may want to browse the marketplace to look for apps, plugins and themes to extend the functionality even further.

Tip: We offer a VIP migration service where we work closely with you to draw up your plan and take care of the conversion for you.
Educate your community
Keep your community up to date with your migration plan. Show them the platform they'll be using. Take videos and screenshots showing them the exciting new features coming soon. Make it a positive and fun experience.
Post something new every few days to get your community used to the idea and get them involved by asking them if they have any questions. Our sales and support teams are here to help you if you have any further questions at this point.
Getting the majority of your community excited about the change is the best way to make the transition a smooth one.
Make sure you explain the benefits of the switch too. If there's a good reason for it, your community will get behind it quickly.
Some benefits may be:
It works better on your mobile device and tablets, so you don't need to struggle with pinch and zoom to get around.

Mobile ready out of the box
The built in embed system allows you to post images, YouTube videos more easily and you can preview it instantly as you type.
The crowd sourced moderation makes reporting bad content more beneficial. It'll help to keep the community clean from undesirable comments and moving a positive direction.
More features on the way. Invision Community is always adding new functionality based on our customers' wishes. These releases happen often so there's always something to be excited about.
Pick a day
The best migrations are planned down to the date and time when the data conversion will occur. Our team can give you a rough idea of how long the data conversion will take. It will vary but we can give you a ballpark. 
Your members will feel happy knowing what is going to happen and when. There will be some downtime while the data is converted, so it's always best to announce this well ahead of time.
Set up a test site
Once you are committed to switching, set up a test site. A single Invision Community license can be used for a development installation as well as a live installation.
This is the perfect time to work on your theme and look at any tweaks you'd like to make.
Invite in your team and a trusted few from your community to offer feedback and advice. It's worth taking the time here to make sure everything is perfect for when you do the final conversion.
Make it comfortable
Take some time to theme your new Invision Community so it has a similar look and feel to your existing community. Change resistant members will feel more comfortable if there are areas that are familiar to them.
Ensuring your branding is up, and the colours match what you had before is a good start.
The easy mode theme editor is a great place to start.
Mind your language!
There are always little differences in the interface language that may throw some of your older members off. For example, some systems use "threads" instead of topics and "messages" instead of posts.

The easy language editor
Invision Community has a built in translation system so you can change our interface language to match your existing site.
Help your members
Set up a temporary questions and answer forum where your members can ask how the new system works and give you feedback.
Pin a handful of topics explaining where common items are now, such as how to edit your profile, how to send personal messages, how to mark the site as read and so on. Think about the daily activities your members make and explain how to do them with Invision Community.
You can use the pre-move time to ask your community what actions they do daily and may need assistance with on the new platform.
Be patient
Some of us dislike change. We are creatures of habit. You may find some members are very resistant. That's OK, they'll come around in time as long as you continue to make them feel valued and understood. Take the time to explain how the new system works and what the benefits of Invision Community are.
In our experience, members love the following Invision Community features:
Notifications
Invision Community has a variety of granular notification options, from browser to email so you're sure to not miss a thing.
Mobile Friendly
We're mobile friendly right out of the box. Our theme has a responsive framework, which means that it resizes perfectly to any device you're using. No need for extra themes or styles, it's all baked in.
Gamification
We all love a little friendly competition don't we? Invision Community has features like the leaderboard and member titles to reward activity. Who doesn't want to win the day?

 
Reactions
Liking content is fun, but being able to express thanks, laughter and more is even better. It's all baked into the system ready to use.
Educate your team
Invision Community has a whole host of moderation tools that your team will love as it makes their daily routines much easier.
From the comprehensive warning system, to the crowd sourced moderation feature, which can automatically hide content and notify moderators once it has been reported multiple times, Invision Community makes your moderators lives easier.
The best approach is to pin topics in a team area that explains how to use these new features and where to find them.
Summary
Investing in a new community platform and migrating your community across is a big decision. With the right planning and forethought, it will be a smooth and positive migration with lots to look forward to once complete.
We offer free conversion tools for you to use, or we offer a VIP conversion service where we take care of it for you and you get one-to-one help and support throughout the process.
We'd love to hear from those who have successfully migrated across from other platforms and how they made it a positive experience for their members.

 

Do you have a community but are looking to move to a more modern and feature rich platform?
There's a lot of ways Invision Community can breathe new life into your community. With our engagement features, advanced promotion features and mobile ready responsive themes, your members are going to love the changes.
Invision Community can power your entire site, from the content management front end right through to your download areas and shopping carts.
Imagine not having to juggle a dozen plug-ins and make several different applications talk to each other.
We offer a range of migration tools for vBulletin, xenForo, phpBB, Vanilla, bbPress and more. These tools convert your data such as members, passwords, forums, topics, posts and more across to Invision Community.
But first, let's look at how to make your migration a success.
Take our demo for a spin
Hands down the best way to get a feel for Invision Community is to take out a free demo. Once you are comfortable with the suite and know what it can do, the more confident you will be in discussing it with your members.
There's a lot of functionality to discover. Keep in touch with our sales team to get the most from the demo.  We recommend that you consider three uses.
Your community. Look at how they will settle in with the new interface and how they will use the new features on offer.
Your moderators. Take a moment to look in the Moderator Control Panel. Run through all the tools that are available, such as the warning system and content review system.

Moderator Tools
Your administrators. Probably the largest change between platforms will be in the Admin Control Panel. It's worth spending a little time getting familiar with it and looking at what's new, and where common tools are such as forum and member management.

Tip: Invision Community's Admin Control Panel has a global search bar to look for settings, members, invoices and more. If you ever feel a little lost, enter in what you're looking for.
Make your plan
Using the demo and speaking to our sales team will help you draw up a migration plan. You'll know which apps you'll need, and what data can be migrated over.
You may want to browse the marketplace to look for apps, plugins and themes to extend the functionality even further.

Tip: We offer a VIP migration service where we work closely with you to draw up your plan and take care of the conversion for you.
Educate your community
Keep your community up to date with your migration plan. Show them the platform they'll be using. Take videos and screenshots showing them the exciting new features coming soon. Make it a positive and fun experience.
Post something new every few days to get your community used to the idea and get them involved by asking them if they have any questions. Our sales and support teams are here to help you if you have any further questions at this point.
Getting the majority of your community excited about the change is the best way to make the transition a smooth one.
Make sure you explain the benefits of the switch too. If there's a good reason for it, your community will get behind it quickly.
Some benefits may be:
It works better on your mobile device and tablets, so you don't need to struggle with pinch and zoom to get around.

Mobile ready out of the box
The built in embed system allows you to post images, YouTube videos more easily and you can preview it instantly as you type.
The crowd sourced moderation makes reporting bad content more beneficial. It'll help to keep the community clean from undesirable comments and moving a positive direction.
More features on the way. Invision Community is always adding new functionality based on our customers' wishes. These releases happen often so there's always something to be excited about.
Pick a day
The best migrations are planned down to the date and time when the data conversion will occur. Our team can give you a rough idea of how long the data conversion will take. It will vary but we can give you a ballpark. 
Your members will feel happy knowing what is going to happen and when. There will be some downtime while the data is converted, so it's always best to announce this well ahead of time.
Set up a test site
Once you are committed to switching, set up a test site. A single Invision Community license can be used for a development installation as well as a live installation.
This is the perfect time to work on your theme and look at any tweaks you'd like to make.
Invite in your team and a trusted few from your community to offer feedback and advice. It's worth taking the time here to make sure everything is perfect for when you do the final conversion.
Make it comfortable
Take some time to theme your new Invision Community so it has a similar look and feel to your existing community. Change resistant members will feel more comfortable if there are areas that are familiar to them.
Ensuring your branding is up, and the colours match what you had before is a good start.
The easy mode theme editor is a great place to start.
Mind your language!
There are always little differences in the interface language that may throw some of your older members off. For example, some systems use "threads" instead of topics and "messages" instead of posts.

The easy language editor
Invision Community has a built in translation system so you can change our interface language to match your existing site.
Help your members
Set up a temporary questions and answer forum where your members can ask how the new system works and give you feedback.
Pin a handful of topics explaining where common items are now, such as how to edit your profile, how to send personal messages, how to mark the site as read and so on. Think about the daily activities your members make and explain how to do them with Invision Community.
You can use the pre-move time to ask your community what actions they do daily and may need assistance with on the new platform.
Be patient
Some of us dislike change. We are creatures of habit. You may find some members are very resistant. That's OK, they'll come around in time as long as you continue to make them feel valued and understood. Take the time to explain how the new system works and what the benefits of Invision Community are.
In our experience, members love the following Invision Community features:
Notifications
Invision Community has a variety of granular notification options, from browser to email so you're sure to not miss a thing.
Mobile Friendly
We're mobile friendly right out of the box. Our theme has a responsive framework, which means that it resizes perfectly to any device you're using. No need for extra themes or styles, it's all baked in.
Gamification
We all love a little friendly competition don't we? Invision Community has features like the leaderboard and member titles to reward activity. Who doesn't want to win the day?

 
Reactions
Liking content is fun, but being able to express thanks, laughter and more is even better. It's all baked into the system ready to use.
Educate your team
Invision Community has a whole host of moderation tools that your team will love as it makes their daily routines much easier.
From the comprehensive warning system, to the crowd sourced moderation feature, which can automatically hide content and notify moderators once it has been reported multiple times, Invision Community makes your moderators lives easier.
The best approach is to pin topics in a team area that explains how to use these new features and where to find them.
Summary
Investing in a new community platform and migrating your community across is a big decision. With the right planning and forethought, it will be a smooth and positive migration with lots to look forward to once complete.
We offer free conversion tools for you to use, or we offer a VIP conversion service where we take care of it for you and you get one-to-one help and support throughout the process.
We'd love to hear from those who have successfully migrated across from other platforms and how they made it a positive experience for their members.

 

Do you have a community but are looking to move to a more modern and feature rich platform?
There's a lot of ways Invision Community can breathe new life into your community. With our engagement features, advanced promotion features and mobile ready responsive themes, your members are going to love the changes.
Invision Community can power your entire site, from the content management front end right through to your download areas and shopping carts.
Imagine not having to juggle a dozen plug-ins and make several different applications talk to each other.
We offer a range of migration tools for vBulletin, xenForo, phpBB, Vanilla, bbPress and more. These tools convert your data such as members, passwords, forums, topics, posts and more across to Invision Community.
But first, let's look at how to make your migration a success.
Take our demo for a spin
Hands down the best way to get a feel for Invision Community is to take out a free demo. Once you are comfortable with the suite and know what it can do, the more confident you will be in discussing it with your members.
There's a lot of functionality to discover. Keep in touch with our sales team to get the most from the demo.  We recommend that you consider three uses.
Your community. Look at how they will settle in with the new interface and how they will use the new features on offer.
Your moderators. Take a moment to look in the Moderator Control Panel. Run through all the tools that are available, such as the warning system and content review system.

Moderator Tools
Your administrators. Probably the largest change between platforms will be in the Admin Control Panel. It's worth spending a little time getting familiar with it and looking at what's new, and where common tools are such as forum and member management.

Tip: Invision Community's Admin Control Panel has a global search bar to look for settings, members, invoices and more. If you ever feel a little lost, enter in what you're looking for.
Make your plan
Using the demo and speaking to our sales team will help you draw up a migration plan. You'll know which apps you'll need, and what data can be migrated over.
You may want to browse the marketplace to look for apps, plugins and themes to extend the functionality even further.

Tip: We offer a VIP migration service where we work closely with you to draw up your plan and take care of the conversion for you.
Educate your community
Keep your community up to date with your migration plan. Show them the platform they'll be using. Take videos and screenshots showing them the exciting new features coming soon. Make it a positive and fun experience.
Post something new every few days to get your community used to the idea and get them involved by asking them if they have any questions. Our sales and support teams are here to help you if you have any further questions at this point.
Getting the majority of your community excited about the change is the best way to make the transition a smooth one.
Make sure you explain the benefits of the switch too. If there's a good reason for it, your community will get behind it quickly.
Some benefits may be:
It works better on your mobile device and tablets, so you don't need to struggle with pinch and zoom to get around.

Mobile ready out of the box
The built in embed system allows you to post images, YouTube videos more easily and you can preview it instantly as you type.
The crowd sourced moderation makes reporting bad content more beneficial. It'll help to keep the community clean from undesirable comments and moving a positive direction.
More features on the way. Invision Community is always adding new functionality based on our customers' wishes. These releases happen often so there's always something to be excited about.
Pick a day
The best migrations are planned down to the date and time when the data conversion will occur. Our team can give you a rough idea of how long the data conversion will take. It will vary but we can give you a ballpark. 
Your members will feel happy knowing what is going to happen and when. There will be some downtime while the data is converted, so it's always best to announce this well ahead of time.
Set up a test site
Once you are committed to switching, set up a test site. A single Invision Community license can be used for a development installation as well as a live installation.
This is the perfect time to work on your theme and look at any tweaks you'd like to make.
Invite in your team and a trusted few from your community to offer feedback and advice. It's worth taking the time here to make sure everything is perfect for when you do the final conversion.
Make it comfortable
Take some time to theme your new Invision Community so it has a similar look and feel to your existing community. Change resistant members will feel more comfortable if there are areas that are familiar to them.
Ensuring your branding is up, and the colours match what you had before is a good start.
The easy mode theme editor is a great place to start.
Mind your language!
There are always little differences in the interface language that may throw some of your older members off. For example, some systems use "threads" instead of topics and "messages" instead of posts.

The easy language editor
Invision Community has a built in translation system so you can change our interface language to match your existing site.
Help your members
Set up a temporary questions and answer forum where your members can ask how the new system works and give you feedback.
Pin a handful of topics explaining where common items are now, such as how to edit your profile, how to send personal messages, how to mark the site as read and so on. Think about the daily activities your members make and explain how to do them with Invision Community.
You can use the pre-move time to ask your community what actions they do daily and may need assistance with on the new platform.
Be patient
Some of us dislike change. We are creatures of habit. You may find some members are very resistant. That's OK, they'll come around in time as long as you continue to make them feel valued and understood. Take the time to explain how the new system works and what the benefits of Invision Community are.
In our experience, members love the following Invision Community features:
Notifications
Invision Community has a variety of granular notification options, from browser to email so you're sure to not miss a thing.
Mobile Friendly
We're mobile friendly right out of the box. Our theme has a responsive framework, which means that it resizes perfectly to any device you're using. No need for extra themes or styles, it's all baked in.
Gamification
We all love a little friendly competition don't we? Invision Community has features like the leaderboard and member titles to reward activity. Who doesn't want to win the day?

 
Reactions
Liking content is fun, but being able to express thanks, laughter and more is even better. It's all baked into the system ready to use.
Educate your team
Invision Community has a whole host of moderation tools that your team will love as it makes their daily routines much easier.
From the comprehensive warning system, to the crowd sourced moderation feature, which can automatically hide content and notify moderators once it has been reported multiple times, Invision Community makes your moderators lives easier.
The best approach is to pin topics in a team area that explains how to use these new features and where to find them.
Summary
Investing in a new community platform and migrating your community across is a big decision. With the right planning and forethought, it will be a smooth and positive migration with lots to look forward to once complete.
We offer free conversion tools for you to use, or we offer a VIP conversion service where we take care of it for you and you get one-to-one help and support throughout the process.
We'd love to hear from those who have successfully migrated across from other platforms and how they made it a positive experience for their members.

 

Do you have a community but are looking to move to a more modern and feature rich platform?
There's a lot of ways Invision Community can breathe new life into your community. With our engagement features, advanced promotion features and mobile ready responsive themes, your members are going to love the changes.
Invision Community can power your entire site, from the content management front end right through to your download areas and shopping carts.
Imagine not having to juggle a dozen plug-ins and make several different applications talk to each other.
We offer a range of migration tools for vBulletin, xenForo, phpBB, Vanilla, bbPress and more. These tools convert your data such as members, passwords, forums, topics, posts and more across to Invision Community.
But first, let's look at how to make your migration a success.
Take our demo for a spin
Hands down the best way to get a feel for Invision Community is to take out a free demo. Once you are comfortable with the suite and know what it can do, the more confident you will be in discussing it with your members.
There's a lot of functionality to discover. Keep in touch with our sales team to get the most from the demo.  We recommend that you consider three uses.
Your community. Look at how they will settle in with the new interface and how they will use the new features on offer.
Your moderators. Take a moment to look in the Moderator Control Panel. Run through all the tools that are available, such as the warning system and content review system.

Moderator Tools
Your administrators. Probably the largest change between platforms will be in the Admin Control Panel. It's worth spending a little time getting familiar with it and looking at what's new, and where common tools are such as forum and member management.

Tip: Invision Community's Admin Control Panel has a global search bar to look for settings, members, invoices and more. If you ever feel a little lost, enter in what you're looking for.
Make your plan
Using the demo and speaking to our sales team will help you draw up a migration plan. You'll know which apps you'll need, and what data can be migrated over.
You may want to browse the marketplace to look for apps, plugins and themes to extend the functionality even further.

Tip: We offer a VIP migration service where we work closely with you to draw up your plan and take care of the conversion for you.
Educate your community
Keep your community up to date with your migration plan. Show them the platform they'll be using. Take videos and screenshots showing them the exciting new features coming soon. Make it a positive and fun experience.
Post something new every few days to get your community used to the idea and get them involved by asking them if they have any questions. Our sales and support teams are here to help you if you have any further questions at this point.
Getting the majority of your community excited about the change is the best way to make the transition a smooth one.
Make sure you explain the benefits of the switch too. If there's a good reason for it, your community will get behind it quickly.
Some benefits may be:
It works better on your mobile device and tablets, so you don't need to struggle with pinch and zoom to get around.

Mobile ready out of the box
The built in embed system allows you to post images, YouTube videos more easily and you can preview it instantly as you type.
The crowd sourced moderation makes reporting bad content more beneficial. It'll help to keep the community clean from undesirable comments and moving a positive direction.
More features on the way. Invision Community is always adding new functionality based on our customers' wishes. These releases happen often so there's always something to be excited about.
Pick a day
The best migrations are planned down to the date and time when the data conversion will occur. Our team can give you a rough idea of how long the data conversion will take. It will vary but we can give you a ballpark. 
Your members will feel happy knowing what is going to happen and when. There will be some downtime while the data is converted, so it's always best to announce this well ahead of time.
Set up a test site
Once you are committed to switching, set up a test site. A single Invision Community license can be used for a development installation as well as a live installation.
This is the perfect time to work on your theme and look at any tweaks you'd like to make.
Invite in your team and a trusted few from your community to offer feedback and advice. It's worth taking the time here to make sure everything is perfect for when you do the final conversion.
Make it comfortable
Take some time to theme your new Invision Community so it has a similar look and feel to your existing community. Change resistant members will feel more comfortable if there are areas that are familiar to them.
Ensuring your branding is up, and the colours match what you had before is a good start.
The easy mode theme editor is a great place to start.
Mind your language!
There are always little differences in the interface language that may throw some of your older members off. For example, some systems use "threads" instead of topics and "messages" instead of posts.

The easy language editor
Invision Community has a built in translation system so you can change our interface language to match your existing site.
Help your members
Set up a temporary questions and answer forum where your members can ask how the new system works and give you feedback.
Pin a handful of topics explaining where common items are now, such as how to edit your profile, how to send personal messages, how to mark the site as read and so on. Think about the daily activities your members make and explain how to do them with Invision Community.
You can use the pre-move time to ask your community what actions they do daily and may need assistance with on the new platform.
Be patient
Some of us dislike change. We are creatures of habit. You may find some members are very resistant. That's OK, they'll come around in time as long as you continue to make them feel valued and understood. Take the time to explain how the new system works and what the benefits of Invision Community are.
In our experience, members love the following Invision Community features:
Notifications
Invision Community has a variety of granular notification options, from browser to email so you're sure to not miss a thing.
Mobile Friendly
We're mobile friendly right out of the box. Our theme has a responsive framework, which means that it resizes perfectly to any device you're using. No need for extra themes or styles, it's all baked in.
Gamification
We all love a little friendly competition don't we? Invision Community has features like the leaderboard and member titles to reward activity. Who doesn't want to win the day?

 
Reactions
Liking content is fun, but being able to express thanks, laughter and more is even better. It's all baked into the system ready to use.
Educate your team
Invision Community has a whole host of moderation tools that your team will love as it makes their daily routines much easier.
From the comprehensive warning system, to the crowd sourced moderation feature, which can automatically hide content and notify moderators once it has been reported multiple times, Invision Community makes your moderators lives easier.
The best approach is to pin topics in a team area that explains how to use these new features and where to find them.
Summary
Investing in a new community platform and migrating your community across is a big decision. With the right planning and forethought, it will be a smooth and positive migration with lots to look forward to once complete.
We offer free conversion tools for you to use, or we offer a VIP conversion service where we take care of it for you and you get one-to-one help and support throughout the process.
We'd love to hear from those who have successfully migrated across from other platforms and how they made it a positive experience for their members.

 

Do you have a community but are looking to move to a more modern and feature rich platform?
There's a lot of ways Invision Community can breathe new life into your community. With our engagement features, advanced promotion features and mobile ready responsive themes, your members are going to love the changes.
Invision Community can power your entire site, from the content management front end right through to your download areas and shopping carts.
Imagine not having to juggle a dozen plug-ins and make several different applications talk to each other.
We offer a range of migration tools for vBulletin, xenForo, phpBB, Vanilla, bbPress and more. These tools convert your data such as members, passwords, forums, topics, posts and more across to Invision Community.
But first, let's look at how to make your migration a success.
Take our demo for a spin
Hands down the best way to get a feel for Invision Community is to take out a free demo. Once you are comfortable with the suite and know what it can do, the more confident you will be in discussing it with your members.
There's a lot of functionality to discover. Keep in touch with our sales team to get the most from the demo.  We recommend that you consider three uses.
Your community. Look at how they will settle in with the new interface and how they will use the new features on offer.
Your moderators. Take a moment to look in the Moderator Control Panel. Run through all the tools that are available, such as the warning system and content review system.

Moderator Tools
Your administrators. Probably the largest change between platforms will be in the Admin Control Panel. It's worth spending a little time getting familiar with it and looking at what's new, and where common tools are such as forum and member management.

Tip: Invision Community's Admin Control Panel has a global search bar to look for settings, members, invoices and more. If you ever feel a little lost, enter in what you're looking for.
Make your plan
Using the demo and speaking to our sales team will help you draw up a migration plan. You'll know which apps you'll need, and what data can be migrated over.
You may want to browse the marketplace to look for apps, plugins and themes to extend the functionality even further.

Tip: We offer a VIP migration service where we work closely with you to draw up your plan and take care of the conversion for you.
Educate your community
Keep your community up to date with your migration plan. Show them the platform they'll be using. Take videos and screenshots showing them the exciting new features coming soon. Make it a positive and fun experience.
Post something new every few days to get your community used to the idea and get them involved by asking them if they have any questions. Our sales and support teams are here to help you if you have any further questions at this point.
Getting the majority of your community excited about the change is the best way to make the transition a smooth one.
Make sure you explain the benefits of the switch too. If there's a good reason for it, your community will get behind it quickly.
Some benefits may be:
It works better on your mobile device and tablets, so you don't need to struggle with pinch and zoom to get around.

Mobile ready out of the box
The built in embed system allows you to post images, YouTube videos more easily and you can preview it instantly as you type.
The crowd sourced moderation makes reporting bad content more beneficial. It'll help to keep the community clean from undesirable comments and moving a positive direction.
More features on the way. Invision Community is always adding new functionality based on our customers' wishes. These releases happen often so there's always something to be excited about.
Pick a day
The best migrations are planned down to the date and time when the data conversion will occur. Our team can give you a rough idea of how long the data conversion will take. It will vary but we can give you a ballpark. 
Your members will feel happy knowing what is going to happen and when. There will be some downtime while the data is converted, so it's always best to announce this well ahead of time.
Set up a test site
Once you are committed to switching, set up a test site. A single Invision Community license can be used for a development installation as well as a live installation.
This is the perfect time to work on your theme and look at any tweaks you'd like to make.
Invite in your team and a trusted few from your community to offer feedback and advice. It's worth taking the time here to make sure everything is perfect for when you do the final conversion.
Make it comfortable
Take some time to theme your new Invision Community so it has a similar look and feel to your existing community. Change resistant members will feel more comfortable if there are areas that are familiar to them.
Ensuring your branding is up, and the colours match what you had before is a good start.
The easy mode theme editor is a great place to start.
Mind your language!
There are always little differences in the interface language that may throw some of your older members off. For example, some systems use "threads" instead of topics and "messages" instead of posts.

The easy language editor
Invision Community has a built in translation system so you can change our interface language to match your existing site.
Help your members
Set up a temporary questions and answer forum where your members can ask how the new system works and give you feedback.
Pin a handful of topics explaining where common items are now, such as how to edit your profile, how to send personal messages, how to mark the site as read and so on. Think about the daily activities your members make and explain how to do them with Invision Community.
You can use the pre-move time to ask your community what actions they do daily and may need assistance with on the new platform.
Be patient
Some of us dislike change. We are creatures of habit. You may find some members are very resistant. That's OK, they'll come around in time as long as you continue to make them feel valued and understood. Take the time to explain how the new system works and what the benefits of Invision Community are.
In our experience, members love the following Invision Community features:
Notifications
Invision Community has a variety of granular notification options, from browser to email so you're sure to not miss a thing.
Mobile Friendly
We're mobile friendly right out of the box. Our theme has a responsive framework, which means that it resizes perfectly to any device you're using. No need for extra themes or styles, it's all baked in.
Gamification
We all love a little friendly competition don't we? Invision Community has features like the leaderboard and member titles to reward activity. Who doesn't want to win the day?

 
Reactions
Liking content is fun, but being able to express thanks, laughter and more is even better. It's all baked into the system ready to use.
Educate your team
Invision Community has a whole host of moderation tools that your team will love as it makes their daily routines much easier.
From the comprehensive warning system, to the crowd sourced moderation feature, which can automatically hide content and notify moderators once it has been reported multiple times, Invision Community makes your moderators lives easier.
The best approach is to pin topics in a team area that explains how to use these new features and where to find them.
Summary
Investing in a new community platform and migrating your community across is a big decision. With the right planning and forethought, it will be a smooth and positive migration with lots to look forward to once complete.
We offer free conversion tools for you to use, or we offer a VIP conversion service where we take care of it for you and you get one-to-one help and support throughout the process.
We'd love to hear from those who have successfully migrated across from other platforms and how they made it a positive experience for their members.

 

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

For most of us, at some point in our lives we've been told we look like someone famous. Maybe it's an actor from a favourite movie, or a member of a popular band.
This has certainly come up a few times among the team in chat. We often joke about our more famous doppelgängers. We've often wondered who'd play us in the movie version of Invision Community. I'm holding out for Ryan Reynolds [Keep dreaming - Editor].
More recently, friend to Invision Community @Joel R mentioned that it'd make a really fun blog entry. So please direct all constructive criticism to Joel if this is not as promised, a fun blog entry.
Ok, lets get started.
Andy is DJ Qualls
You may recognise DJ Qualls from comedies such as Road Trip and Road Trip: Beer Pong [Great list there - Editor]. This comparison was straight from Andy. He gets compared to him by his friends quite often apparently [He needs new friends- Editor].
Personally, I think it's just the fact that he also wears the exact same glasses.

Andy is DJ Qualls
Brandon is Adam Levine
Brandon was incredibly quick to mention that his dentist routinely says that he looks like Adam Levine, which seems like an odd thing to mention at most appointments. You may have heard of Adam from the band Maroon 5 and a few movies that I've not bothered watching [Awesome research for this piece - Editor].

 
Brandon is Adam Levine
Daniel is Daniel Brühl
Not only do they have the same first name, they also share a nose [Who has it today? - Editor]. You might have seen Daniel playing Nikki Lauder in the movie Rush, as well as that shady guy in Captain America: Civil War.

Nose twins
Jennifer is Charlize Theron
Jennifer had several looks for this blog entry, and chose the one featured below, which is very reminiscent of Charlize's role in Mad Max. You may know Charlize from her many movies. Including Max Max [Again, great research - Editor].

The eyes have it.
Lindy is Tony Soprano
This is a comparison I've been making for years. Lindy has a certain "aura" that reminds me a little of the the mafia boss with a conscience. There was a hotdog incident at his house which I don't want to go into right now [No, please do - Editor].
Tony Soprano was played by the late James Gandolfini.

Both know how to hide bodies
Marc is Casey Affleck
Honestly, this took a while to figure out because Marc looks like no other human being alive. We even tried those "Who is your celeb twin" apps and they threw errors and deleted themselves in a panic. This is the best we could do. Casey Affleck is of course Batman's younger brother [Have you ever read a comic? - Editor].

Yeah, it's not great is it.
Mark is Ansel Elgort
So one night I sat down to watch Baby Driver, featuring Ansel. It was uncanny how much he reminded me of our resident developer Mark. Even down to the facial expressions. It's uncanny.

I honestly have no idea which is which
Mark H is Ben Folds
Full disclosure, the photo Mark submitted could politely be described as "vintage" [Not sure that's polite - Editor]. However, as soon as I saw it, I was amazed at how much he looked like my favourite singer/songwriter Ben Folds. I'm not saying this photo of Mark his old, but lets say it cost us $10,000 to have an expert colour it from the black and white original.

Classic Mark
Matt is David Boreanez
Over the course of my 20s and 30s [Clearly not now you're old - Editor], I was often compared to "Angel from Buffy" played by David Boreanez. I thought it was because of my cool but brooding demeanour [lol - Editor] but maybe it's just one of those chance genetic occurrences.

Well, similar hair at least
Rhett is Bruce Willis
Rhett never lets our servers Die Hard [Jeez, you went there - Editor] but he does resemble Bruce Willis. It's not just that they visit the same hair dresser either.

Twins!
Ryan is Ethan Hawke
We've saved the best to last, because this comparison caused actual goosebumps. Someone even said "wow" when they saw it. These two could be related. Ethan Hawke is a huge movie star, so Ryan was quite happy with this comparison.

Uncle Ethan?
So, there you have it.

If there was a movie to be made featuring our lives, then this is the cast that would be our first choice.

Who do you look like? We've love to see your pictures too. Let us know below!
 

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

Unless you've been living under a rock, or forgot to opt-in to the memo, GDPR is just around the corner.
Last week we wrote a blog answering your questions on becoming GDPR compliant with Invision Community.
We took away a few good points from that discussion and have the following updates coming up for Invision Community 4.3.3 due early next week.
Downloading Personal Data
Invision Community already has a method of downloading member data via the member export feature that produces a CSV.
However, we wanted Invision Community to be more helpful, so we've added a feature that downloads personal data (such as name, email address, known IP addresses, known devices, opt in details and customer data from Nexus if you're using that) in a handy XML format which is very portable and machine readable.
 

You can access this feature via the ACP member view
The download itself is in a standard XML format.

A sample export
Pruning IP Addresses
While there is much debate about whether IP addresses are personal information or not, a good number of our customers requested a way to remove IP addresses from older content.
There are legitimate reasons to store IP addresses for purchase transactions (so fraud can be detected), for security logs (to prevent hackers gaining access) and to prevent spammers registering. However, under the bullet point of not storing information for longer than is required, we have added this feature to remove IP addresses from posted content (reviews, comments, posts, personal messages, etc) after a threshold.

The default is 'Never', so don't worry. Post upgrade you won't see IP addresses removed unless you enter a value.

This new setting is under Posting
Deleting Members
Invision Community has always had a way to delete a member and retain their content under a "Guest" name.
We've cleaned this up in 4.3.3. When you delete a member, but want to retain their content, you are offered an option to anonymise this. Choosing this option attributes all posted content to 'Guest' and removes any stored IP addresses.

Deleting a member
Privacy Policy
We've added a neat little feature to automatically list third parties you use on your privacy policy. If you enable Google Analytics, or Facebook Pixel, etc, these are added for you.

The new setting

 
Finding Settings Easily
To make life a little easier, we've added "GDPR" as a live search keyword for the ACP. Simply tap that into the large search bar and Invision Community will list the relevant settings you may want to change.

 
These changes show our ongoing commitment to helping you with your GDPR compliance. We'll be watching how GDPR in practise unfolds next month and will continue to adapt where required.

Invision Community 4.3.3 is due out early next week.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

You've no doubt heard about GDPR by now. It's a very hot topic in many circles. Lots of experts are weighing in on the best approach to take before the May 25th deadline.
Which reminds me of my favorite joke:
"Do you know a great GDPR expert?”
Yes, I do!
“Could you send me his email address”
No, I'm afraid not.
I wrote about how Invision Community can help with your GDPR compliance back in December. I've seen a lot of posts and topics on GDPR in our community since then.
First, let's get the disclaimer out of the way. I'm a humble programmer and not a GDPR expert or a lawyer. The information here is presented to assist you in making decisions. As always, we recommend you do your own research and if you're in any doubt, book an appointment with a lawyer.
It is also worth mentioning that GDPR is very much a living document with phrases like "legitimate interest" and "reasonable measures". None of these phrases have any real legal definition and are open to interpretation. Some have interpreted them severely, and others more liberally.
GDRP is about being a good steward of the data you store on a user. It's not designed to stop you from operating an engaging web site. There's no need to create stress about users linking to other sites, embedding images, anonymizing IP addresses, and such on your site. These don't impact any data you are storing and are part of the normal operation of how the web works. Be responsible and respectful of your users' data but keep enjoying your community.
Let's have a quick recap on the points we raised in our original blog entry.
Individual Rights
The right to be informed
Invision Community has a built in privacy policy system that is presented to a new user, and existing users when it has been updated.

 
What should your privacy policy contain? I personally like the look of SEQ Legal's framework which is available for free.
This policy covers the important points such as which cookies are collected, how personal information is used and so on.
There may be other services out there offering similar templates.
Right to erasure
I personally feel that everyone should listen to "A Little Respect" as it's not only a cracking tune, but also carries a wonderful message.
The GDPR document however relates to the individuals right to be forgotten.
Invision Community allows you to delete members. When deleting members, you can elect to remove their content too. There is an option to keep it as Guest content, thus removing the author as identifiable.
It's worth using the 'keep' option after researching the user's posts to make sure they haven't posted personal information such as where they live, etc.
Emailing and Consent
Invision Community has the correct opt-in for bulk emails on registration that is not pre-checked. If the user checks this option, this is recorded with the member's history. Likewise, if they retract this permission, that action is also recorded.

 
When you edit the terms and conditions or privacy policy, all users are required to read it again and opt-in again.
Cookies
A lot of GDPR anxiety seems to revolve around these tiny little text files your browser stores. If you read the GDPR document (and who doesn't love a little light reading) then you'll see that very little has actually changed with cookies. It extends current data protection guidance a little to ensure that you are transparent about which cookies you store.
Invision Community has tools to create a floating cookie opt-in bar, and also a page showing which cookies are stored and why.
This is the page that you'd edit to add any cookies your installation sets (if you have enabled Facebook's Pixel, or Google Analytics for example).
Your GDPR Questions
Now let's look at some questions that have been asked on our community and I'll do my best to provide some guidance that should help you make decisions on how to configure your Invision Community to suit your needs.

Alan!!
Is the soft opt-in cookie policy enough? What about the IP address stored in the session cookie?
Great question. There's conflicting advise out there about this. The GDPR document states:
The ICO states that session cookies stored for that session only (so they are deleted when the tab / window is closed) are OK as long as they are not used to profile users.
This is re-enforced by EUROPA:

My feeling is that GDPR isn't really out to stop you creating a functioning website, they are more interested in how you store and use this information.
Thus, I feel that storing a session cookie with an IP address is OK. The user is told what is being stored and instructions are given if they want to delete them.
Given the internet is very much driven by IP addresses, I fail to see how you can not collect an IP address in some form or another. They are collected in access logs deep in the server OS.
Finally, there is a strong legitimate interest in creating a session cookie. It's part and parcel of the website's function and the cookie is not used in any 'bad' way. It just allows guests and members to retain preferences and update "last seen" times to help deliver content.
Do I need to delete all the posts by a member if they ask me to?
We have many large clients in the EU with really impressive and expensive legal teams and they are all unanimous in telling us that there is no requirement to delete content when deleting a user's personal information. The analogy often given is with email: once someone sends you an email you are not obligated to delete that. The same is true with content posted by a user: once they post that content it's no longer "owned" by them and is now out in public.

Ultimately, the decision is yours but do not feel that you have to delete their content. This is not a GDPR requirement.
What about members who haven't validated? They're technically not members but we're still holding their data!
No problem. The system does delete un-validated users and incomplete users automatically for you. You can even set the time delay for deletion in the ACP.

 
What about RECAPTCHA? I use this, and it technically collects some data!
Just add that you use this service to your privacy policy, like so:
I see many companies emailing out asking for members to opt back in for bulk mail, do I need to do this?
Short answer: No.
Since Invision Community 4.0, you can only ever bulk email users that have opted in for bulk emails. There's no way around it, so there's nothing to ask them to opt-in for. They've already done it.
There is a tiny wrinkle in that pre 4.2.7, the opt-in was pre-checked as was the norm for most websites. Moving forward, GDPR asks for explicit consent, so this checkbox cannot be pre-ticked (and isn't in Invision Community 4.2.7 and later). However, the ICO is clear that if the email list has a legitimate interest, and was obtained with soft opt-in, then you don't need to ask again for permission.
What about notifications? They send emails!
Yes they do, but that's OK.
A notification is only ever sent after a user chooses to follow an item. This falls under legitimate interest.
There is also a clear way to stop receiving emails. The user can opt-in and opt-out of email as a notification device at their leisure.

 
Do I need to stop blocking embeds and external images?
No. The internet is based on cross-linking of things and sharing information. At a very fundamental level, it's going to be incredibly hard to prevent it from happening. Removing these engaging and enriching tools are only going to make your community suffer.

There's no harm in adding a few lines in your privacy policy explaining that the site may feature videos from Vimeo and Youtube as part of user contributions but you do not need to be worried. As stated earlier, GDPR isn't about sucking the fun out of the internet, it's about being responsible and transparent.
Phew.
Hopefully you've got a better understanding about how Invision Community can assist your GDPR compliance efforts.
The best bit of advice is to not panic. If you have any questions, we'd love to hear them. Drop us a line below.

For most of us, at some point in our lives we've been told we look like someone famous. Maybe it's an actor from a favourite movie, or a member of a popular band.
This has certainly come up a few times among the team in chat. We often joke about our more famous doppelgängers. We've often wondered who'd play us in the movie version of Invision Community. I'm holding out for Ryan Reynolds [Keep dreaming - Editor].
More recently, friend to Invision Community @Joel R mentioned that it'd make a really fun blog entry. So please direct all constructive criticism to Joel if this is not as promised, a fun blog entry.
Ok, lets get started.
Andy is DJ Qualls
You may recognise DJ Qualls from comedies such as Road Trip and Road Trip: Beer Pong [Great list there - Editor]. This comparison was straight from Andy. He gets compared to him by his friends quite often apparently [He needs new friends- Editor].
Personally, I think it's just the fact that he also wears the exact same glasses.

Andy is DJ Qualls
Brandon is Adam Levine
Brandon was incredibly quick to mention that his dentist routinely says that he looks like Adam Levine, which seems like an odd thing to mention at most appointments. You may have heard of Adam from the band Maroon 5 and a few movies that I've not bothered watching [Awesome research for this piece - Editor].

 
Brandon is Adam Levine
Daniel is Daniel Brühl
Not only do they have the same first name, they also share a nose [Who has it today? - Editor]. You might have seen Daniel playing Nikki Lauder in the movie Rush, as well as that shady guy in Captain America: Civil War.

Nose twins
Jennifer is Charlize Theron
Jennifer had several looks for this blog entry, and chose the one featured below, which is very reminiscent of Charlize's role in Mad Max. You may know Charlize from her many movies. Including Max Max [Again, great research - Editor].

The eyes have it.
Lindy is Tony Soprano
This is a comparison I've been making for years. Lindy has a certain "aura" that reminds me a little of the the mafia boss with a conscience. There was a hotdog incident at his house which I don't want to go into right now [No, please do - Editor].
Tony Soprano was played by the late James Gandolfini.

Both know how to hide bodies
Marc is Casey Affleck
Honestly, this took a while to figure out because Marc looks like no other human being alive. We even tried those "Who is your celeb twin" apps and they threw errors and deleted themselves in a panic. This is the best we could do. Casey Affleck is of course Batman's younger brother [Have you ever read a comic? - Editor].

Yeah, it's not great is it.
Mark is Ansel Elgort
So one night I sat down to watch Baby Driver, featuring Ansel. It was uncanny how much he reminded me of our resident developer Mark. Even down to the facial expressions. It's uncanny.

I honestly have no idea which is which
Mark H is Ben Folds
Full disclosure, the photo Mark submitted could politely be described as "vintage" [Not sure that's polite - Editor]. However, as soon as I saw it, I was amazed at how much he looked like my favourite singer/songwriter Ben Folds. I'm not saying this photo of Mark his old, but lets say it cost us $10,000 to have an expert colour it from the black and white original.

Classic Mark
Matt is David Boreanez
Over the course of my 20s and 30s [Clearly not now you're old - Editor], I was often compared to "Angel from Buffy" played by David Boreanez. I thought it was because of my cool but brooding demeanour [lol - Editor] but maybe it's just one of those chance genetic occurrences.

Well, similar hair at least
Rhett is Bruce Willis
Rhett never lets our servers Die Hard [Jeez, you went there - Editor] but he does resemble Bruce Willis. It's not just that they visit the same hair dresser either.

Twins!
Ryan is Ethan Hawke
We've saved the best to last, because this comparison caused actual goosebumps. Someone even said "wow" when they saw it. These two could be related. Ethan Hawke is a huge movie star, so Ryan was quite happy with this comparison.

Uncle Ethan?
So, there you have it.

If there was a movie to be made featuring our lives, then this is the cast that would be our first choice.

Who do you look like? We've love to see your pictures too. Let us know below!
 

For most of us, at some point in our lives we've been told we look like someone famous. Maybe it's an actor from a favourite movie, or a member of a popular band.
This has certainly come up a few times among the team in chat. We often joke about our more famous doppelgängers. We've often wondered who'd play us in the movie version of Invision Community. I'm holding out for Ryan Reynolds [Keep dreaming - Editor].
More recently, friend to Invision Community @Joel R mentioned that it'd make a really fun blog entry. So please direct all constructive criticism to Joel if this is not as promised, a fun blog entry.
Ok, lets get started.
Andy is DJ Qualls
You may recognise DJ Qualls from comedies such as Road Trip and Road Trip: Beer Pong [Great list there - Editor]. This comparison was straight from Andy. He gets compared to him by his friends quite often apparently [He needs new friends- Editor].
Personally, I think it's just the fact that he also wears the exact same glasses.

Andy is DJ Qualls
Brandon is Adam Levine
Brandon was incredibly quick to mention that his dentist routinely says that he looks like Adam Levine, which seems like an odd thing to mention at most appointments. You may have heard of Adam from the band Maroon 5 and a few movies that I've not bothered watching [Awesome research for this piece - Editor].

 
Brandon is Adam Levine
Daniel is Daniel Brühl
Not only do they have the same first name, they also share a nose [Who has it today? - Editor]. You might have seen Daniel playing Nikki Lauder in the movie Rush, as well as that shady guy in Captain America: Civil War.

Nose twins
Jennifer is Charlize Theron
Jennifer had several looks for this blog entry, and chose the one featured below, which is very reminiscent of Charlize's role in Mad Max. You may know Charlize from her many movies. Including Max Max [Again, great research - Editor].

The eyes have it.
Lindy is Tony Soprano
This is a comparison I've been making for years. Lindy has a certain "aura" that reminds me a little of the the mafia boss with a conscience. There was a hotdog incident at his house which I don't want to go into right now [No, please do - Editor].
Tony Soprano was played by the late James Gandolfini.

Both know how to hide bodies
Marc is Casey Affleck
Honestly, this took a while to figure out because Marc looks like no other human being alive. We even tried those "Who is your celeb twin" apps and they threw errors and deleted themselves in a panic. This is the best we could do. Casey Affleck is of course Batman's younger brother [Have you ever read a comic? - Editor].

Yeah, it's not great is it.
Mark is Ansel Elgort
So one night I sat down to watch Baby Driver, featuring Ansel. It was uncanny how much he reminded me of our resident developer Mark. Even down to the facial expressions. It's uncanny.

I honestly have no idea which is which
Mark H is Ben Folds
Full disclosure, the photo Mark submitted could politely be described as "vintage" [Not sure that's polite - Editor]. However, as soon as I saw it, I was amazed at how much he looked like my favourite singer/songwriter Ben Folds. I'm not saying this photo of Mark his old, but lets say it cost us $10,000 to have an expert colour it from the black and white original.

Classic Mark
Matt is David Boreanez
Over the course of my 20s and 30s [Clearly not now you're old - Editor], I was often compared to "Angel from Buffy" played by David Boreanez. I thought it was because of my cool but brooding demeanour [lol - Editor] but maybe it's just one of those chance genetic occurrences.

Well, similar hair at least
Rhett is Bruce Willis
Rhett never lets our servers Die Hard [Jeez, you went there - Editor] but he does resemble Bruce Willis. It's not just that they visit the same hair dresser either.

Twins!
Ryan is Ethan Hawke
We've saved the best to last, because this comparison caused actual goosebumps. Someone even said "wow" when they saw it. These two could be related. Ethan Hawke is a huge movie star, so Ryan was quite happy with this comparison.

Uncle Ethan?
So, there you have it.

If there was a movie to be made featuring our lives, then this is the cast that would be our first choice.

Who do you look like? We've love to see your pictures too. Let us know below!
 

For most of us, at some point in our lives we've been told we look like someone famous. Maybe it's an actor from a favourite movie, or a member of a popular band.
This has certainly come up a few times among the team in chat. We often joke about our more famous doppelgängers. We've often wondered who'd play us in the movie version of Invision Community. I'm holding out for Ryan Reynolds [Keep dreaming - Editor].
More recently, friend to Invision Community @Joel R mentioned that it'd make a really fun blog entry. So please direct all constructive criticism to Joel if this is not as promised, a fun blog entry.
Ok, lets get started.
Andy is DJ Qualls
You may recognise DJ Qualls from comedies such as Road Trip and Road Trip: Beer Pong [Great list there - Editor]. This comparison was straight from Andy. He gets compared to him by his friends quite often apparently [He needs new friends- Editor].
Personally, I think it's just the fact that he also wears the exact same glasses.

Andy is DJ Qualls
Brandon is Adam Levine
Brandon was incredibly quick to mention that his dentist routinely says that he looks like Adam Levine, which seems like an odd thing to mention at most appointments. You may have heard of Adam from the band Maroon 5 and a few movies that I've not bothered watching [Awesome research for this piece - Editor].

 
Brandon is Adam Levine
Daniel is Daniel Brühl
Not only do they have the same first name, they also share a nose [Who has it today? - Editor]. You might have seen Daniel playing Nikki Lauder in the movie Rush, as well as that shady guy in Captain America: Civil War.

Nose twins
Jennifer is Charlize Theron
Jennifer had several looks for this blog entry, and chose the one featured below, which is very reminiscent of Charlize's role in Mad Max. You may know Charlize from her many movies. Including Max Max [Again, great research - Editor].

The eyes have it.
Lindy is Tony Soprano
This is a comparison I've been making for years. Lindy has a certain "aura" that reminds me a little of the the mafia boss with a conscience. There was a hotdog incident at his house which I don't want to go into right now [No, please do - Editor].
Tony Soprano was played by the late James Gandolfini.

Both know how to hide bodies
Marc is Casey Affleck
Honestly, this took a while to figure out because Marc looks like no other human being alive. We even tried those "Who is your celeb twin" apps and they threw errors and deleted themselves in a panic. This is the best we could do. Casey Affleck is of course Batman's younger brother [Have you ever read a comic? - Editor].

Yeah, it's not great is it.
Mark is Ansel Elgort
So one night I sat down to watch Baby Driver, featuring Ansel. It was uncanny how much he reminded me of our resident developer Mark. Even down to the facial expressions. It's uncanny.

I honestly have no idea which is which
Mark H is Ben Folds
Full disclosure, the photo Mark submitted could politely be described as "vintage" [Not sure that's polite - Editor]. However, as soon as I saw it, I was amazed at how much he looked like my favourite singer/songwriter Ben Folds. I'm not saying this photo of Mark his old, but lets say it cost us $10,000 to have an expert colour it from the black and white original.

Classic Mark
Matt is David Boreanez
Over the course of my 20s and 30s [Clearly not now you're old - Editor], I was often compared to "Angel from Buffy" played by David Boreanez. I thought it was because of my cool but brooding demeanour [lol - Editor] but maybe it's just one of those chance genetic occurrences.

Well, similar hair at least
Rhett is Bruce Willis
Rhett never lets our servers Die Hard [Jeez, you went there - Editor] but he does resemble Bruce Willis. It's not just that they visit the same hair dresser either.

Twins!
Ryan is Ethan Hawke
We've saved the best to last, because this comparison caused actual goosebumps. Someone even said "wow" when they saw it. These two could be related. Ethan Hawke is a huge movie star, so Ryan was quite happy with this comparison.

Uncle Ethan?
So, there you have it.

If there was a movie to be made featuring our lives, then this is the cast that would be our first choice.

Who do you look like? We've love to see your pictures too. Let us know below!
 

For most of us, at some point in our lives we've been told we look like someone famous. Maybe it's an actor from a favourite movie, or a member of a popular band.
This has certainly come up a few times among the team in chat. We often joke about our more famous doppelgängers. We've often wondered who'd play us in the movie version of Invision Community. I'm holding out for Ryan Reynolds [Keep dreaming - Editor].
More recently, friend to Invision Community @Joel R mentioned that it'd make a really fun blog entry. So please direct all constructive criticism to Joel if this is not as promised, a fun blog entry.
Ok, lets get started.
Andy is DJ Qualls
You may recognise DJ Qualls from comedies such as Road Trip and Road Trip: Beer Pong [Great list there - Editor]. This comparison was straight from Andy. He gets compared to him by his friends quite often apparently [He needs new friends- Editor].
Personally, I think it's just the fact that he also wears the exact same glasses.

Andy is DJ Qualls
Brandon is Adam Levine
Brandon was incredibly quick to mention that his dentist routinely says that he looks like Adam Levine, which seems like an odd thing to mention at most appointments. You may have heard of Adam from the band Maroon 5 and a few movies that I've not bothered watching [Awesome research for this piece - Editor].

 
Brandon is Adam Levine
Daniel is Daniel Brühl
Not only do they have the same first name, they also share a nose [Who has it today? - Editor]. You might have seen Daniel playing Nikki Lauder in the movie Rush, as well as that shady guy in Captain America: Civil War.

Nose twins
Jennifer is Charlize Theron
Jennifer had several looks for this blog entry, and chose the one featured below, which is very reminiscent of Charlize's role in Mad Max. You may know Charlize from her many movies. Including Max Max [Again, great research - Editor].

The eyes have it.
Lindy is Tony Soprano
This is a comparison I've been making for years. Lindy has a certain "aura" that reminds me a little of the the mafia boss with a conscience. There was a hotdog incident at his house which I don't want to go into right now [No, please do - Editor].
Tony Soprano was played by the late James Gandolfini.

Both know how to hide bodies
Marc is Casey Affleck
Honestly, this took a while to figure out because Marc looks like no other human being alive. We even tried those "Who is your celeb twin" apps and they threw errors and deleted themselves in a panic. This is the best we could do. Casey Affleck is of course Batman's younger brother [Have you ever read a comic? - Editor].

Yeah, it's not great is it.
Mark is Ansel Elgort
So one night I sat down to watch Baby Driver, featuring Ansel. It was uncanny how much he reminded me of our resident developer Mark. Even down to the facial expressions. It's uncanny.

I honestly have no idea which is which
Mark H is Ben Folds
Full disclosure, the photo Mark submitted could politely be described as "vintage" [Not sure that's polite - Editor]. However, as soon as I saw it, I was amazed at how much he looked like my favourite singer/songwriter Ben Folds. I'm not saying this photo of Mark his old, but lets say it cost us $10,000 to have an expert colour it from the black and white original.

Classic Mark
Matt is David Boreanez
Over the course of my 20s and 30s [Clearly not now you're old - Editor], I was often compared to "Angel from Buffy" played by David Boreanez. I thought it was because of my cool but brooding demeanour [lol - Editor] but maybe it's just one of those chance genetic occurrences.

Well, similar hair at least
Rhett is Bruce Willis
Rhett never lets our servers Die Hard [Jeez, you went there - Editor] but he does resemble Bruce Willis. It's not just that they visit the same hair dresser either.

Twins!
Ryan is Ethan Hawke
We've saved the best to last, because this comparison caused actual goosebumps. Someone even said "wow" when they saw it. These two could be related. Ethan Hawke is a huge movie star, so Ryan was quite happy with this comparison.

Uncle Ethan?
So, there you have it.

If there was a movie to be made featuring our lives, then this is the cast that would be our first choice.

Who do you look like? We've love to see your pictures too. Let us know below!
 

For most of us, at some point in our lives we've been told we look like someone famous. Maybe it's an actor from a favourite movie, or a member of a popular band.
This has certainly come up a few times among the team in chat. We often joke about our more famous doppelgängers. We've often wondered who'd play us in the movie version of Invision Community. I'm holding out for Ryan Reynolds [Keep dreaming - Editor].
More recently, friend to Invision Community @Joel R mentioned that it'd make a really fun blog entry. So please direct all constructive criticism to Joel if this is not as promised, a fun blog entry.
Ok, lets get started.
Andy is DJ Qualls
You may recognise DJ Qualls from comedies such as Road Trip and Road Trip: Beer Pong [Great list there - Editor]. This comparison was straight from Andy. He gets compared to him by his friends quite often apparently [He needs new friends- Editor].
Personally, I think it's just the fact that he also wears the exact same glasses.

Andy is DJ Qualls
Brandon is Adam Levine
Brandon was incredibly quick to mention that his dentist routinely says that he looks like Adam Levine, which seems like an odd thing to mention at most appointments. You may have heard of Adam from the band Maroon 5 and a few movies that I've not bothered watching [Awesome research for this piece - Editor].

 
Brandon is Adam Levine
Daniel is Daniel Brühl
Not only do they have the same first name, they also share a nose [Who has it today? - Editor]. You might have seen Daniel playing Nikki Lauder in the movie Rush, as well as that shady guy in Captain America: Civil War.

Nose twins
Jennifer is Charlize Theron
Jennifer had several looks for this blog entry, and chose the one featured below, which is very reminiscent of Charlize's role in Mad Max. You may know Charlize from her many movies. Including Max Max [Again, great research - Editor].

The eyes have it.
Lindy is Tony Soprano
This is a comparison I've been making for years. Lindy has a certain "aura" that reminds me a little of the the mafia boss with a conscience. There was a hotdog incident at his house which I don't want to go into right now [No, please do - Editor].
Tony Soprano was played by the late James Gandolfini.

Both know how to hide bodies
Marc is Casey Affleck
Honestly, this took a while to figure out because Marc looks like no other human being alive. We even tried those "Who is your celeb twin" apps and they threw errors and deleted themselves in a panic. This is the best we could do. Casey Affleck is of course Batman's younger brother [Have you ever read a comic? - Editor].

Yeah, it's not great is it.
Mark is Ansel Elgort
So one night I sat down to watch Baby Driver, featuring Ansel. It was uncanny how much he reminded me of our resident developer Mark. Even down to the facial expressions. It's uncanny.

I honestly have no idea which is which
Mark H is Ben Folds
Full disclosure, the photo Mark submitted could politely be described as "vintage" [Not sure that's polite - Editor]. However, as soon as I saw it, I was amazed at how much he looked like my favourite singer/songwriter Ben Folds. I'm not saying this photo of Mark his old, but lets say it cost us $10,000 to have an expert colour it from the black and white original.

Classic Mark
Matt is David Boreanez
Over the course of my 20s and 30s [Clearly not now you're old - Editor], I was often compared to "Angel from Buffy" played by David Boreanez. I thought it was because of my cool but brooding demeanour [lol - Editor] but maybe it's just one of those chance genetic occurrences.

Well, similar hair at least
Rhett is Bruce Willis
Rhett never lets our servers Die Hard [Jeez, you went there - Editor] but he does resemble Bruce Willis. It's not just that they visit the same hair dresser either.

Twins!
Ryan is Ethan Hawke
We've saved the best to last, because this comparison caused actual goosebumps. Someone even said "wow" when they saw it. These two could be related. Ethan Hawke is a huge movie star, so Ryan was quite happy with this comparison.

Uncle Ethan?
So, there you have it.

If there was a movie to be made featuring our lives, then this is the cast that would be our first choice.

Who do you look like? We've love to see your pictures too. Let us know below!
 

For most of us, at some point in our lives we've been told we look like someone famous. Maybe it's an actor from a favourite movie, or a member of a popular band.
This has certainly come up a few times among the team in chat. We often joke about our more famous doppelgängers. We've often wondered who'd play us in the movie version of Invision Community. I'm holding out for Ryan Reynolds [Keep dreaming - Editor].
More recently, friend to Invision Community @Joel R mentioned that it'd make a really fun blog entry. So please direct all constructive criticism to Joel if this is not as promised, a fun blog entry.
Ok, lets get started.
Andy is DJ Qualls
You may recognise DJ Qualls from comedies such as Road Trip and Road Trip: Beer Pong [Great list there - Editor]. This comparison was straight from Andy. He gets compared to him by his friends quite often apparently [He needs new friends- Editor].
Personally, I think it's just the fact that he also wears the exact same glasses.

Andy is DJ Qualls
Brandon is Adam Levine
Brandon was incredibly quick to mention that his dentist routinely says that he looks like Adam Levine, which seems like an odd thing to mention at most appointments. You may have heard of Adam from the band Maroon 5 and a few movies that I've not bothered watching [Awesome research for this piece - Editor].

 
Brandon is Adam Levine
Daniel is Daniel Brühl
Not only do they have the same first name, they also share a nose [Who has it today? - Editor]. You might have seen Daniel playing Nikki Lauder in the movie Rush, as well as that shady guy in Captain America: Civil War.

Nose twins
Jennifer is Charlize Theron
Jennifer had several looks for this blog entry, and chose the one featured below, which is very reminiscent of Charlize's role in Mad Max. You may know Charlize from her many movies. Including Max Max [Again, great research - Editor].

The eyes have it.
Lindy is Tony Soprano
This is a comparison I've been making for years. Lindy has a certain "aura" that reminds me a little of the the mafia boss with a conscience. There was a hotdog incident at his house which I don't want to go into right now [No, please do - Editor].
Tony Soprano was played by the late James Gandolfini.

Both know how to hide bodies
Marc is Casey Affleck
Honestly, this took a while to figure out because Marc looks like no other human being alive. We even tried those "Who is your celeb twin" apps and they threw errors and deleted themselves in a panic. This is the best we could do. Casey Affleck is of course Batman's younger brother [Have you ever read a comic? - Editor].

Yeah, it's not great is it.
Mark is Ansel Elgort
So one night I sat down to watch Baby Driver, featuring Ansel. It was uncanny how much he reminded me of our resident developer Mark. Even down to the facial expressions. It's uncanny.

I honestly have no idea which is which
Mark H is Ben Folds
Full disclosure, the photo Mark submitted could politely be described as "vintage" [Not sure that's polite - Editor]. However, as soon as I saw it, I was amazed at how much he looked like my favourite singer/songwriter Ben Folds. I'm not saying this photo of Mark his old, but lets say it cost us $10,000 to have an expert colour it from the black and white original.

Classic Mark
Matt is David Boreanez
Over the course of my 20s and 30s [Clearly not now you're old - Editor], I was often compared to "Angel from Buffy" played by David Boreanez. I thought it was because of my cool but brooding demeanour [lol - Editor] but maybe it's just one of those chance genetic occurrences.

Well, similar hair at least
Rhett is Bruce Willis
Rhett never lets our servers Die Hard [Jeez, you went there - Editor] but he does resemble Bruce Willis. It's not just that they visit the same hair dresser either.

Twins!
Ryan is Ethan Hawke
We've saved the best to last, because this comparison caused actual goosebumps. Someone even said "wow" when they saw it. These two could be related. Ethan Hawke is a huge movie star, so Ryan was quite happy with this comparison.

Uncle Ethan?
So, there you have it.

If there was a movie to be made featuring our lives, then this is the cast that would be our first choice.

Who do you look like? We've love to see your pictures too. Let us know below!
 

For most of us, at some point in our lives we've been told we look like someone famous. Maybe it's an actor from a favourite movie, or a member of a popular band.
This has certainly come up a few times among the team in chat. We often joke about our more famous doppelgängers. We've often wondered who'd play us in the movie version of Invision Community. I'm holding out for Ryan Reynolds [Keep dreaming - Editor].
More recently, friend to Invision Community @Joel R mentioned that it'd make a really fun blog entry. So please direct all constructive criticism to Joel if this is not as promised, a fun blog entry.
Ok, lets get started.
Andy is DJ Qualls
You may recognise DJ Qualls from comedies such as Road Trip and Road Trip: Beer Pong [Great list there - Editor]. This comparison was straight from Andy. He gets compared to him by his friends quite often apparently [He needs new friends- Editor].
Personally, I think it's just the fact that he also wears the exact same glasses.

Andy is DJ Qualls
Brandon is Adam Levine
Brandon was incredibly quick to mention that his dentist routinely says that he looks like Adam Levine, which seems like an odd thing to mention at most appointments. You may have heard of Adam from the band Maroon 5 and a few movies that I've not bothered watching [Awesome research for this piece - Editor].

 
Brandon is Adam Levine
Daniel is Daniel Brühl
Not only do they have the same first name, they also share a nose [Who has it today? - Editor]. You might have seen Daniel playing Nikki Lauder in the movie Rush, as well as that shady guy in Captain America: Civil War.

Nose twins
Jennifer is Charlize Theron
Jennifer had several looks for this blog entry, and chose the one featured below, which is very reminiscent of Charlize's role in Mad Max. You may know Charlize from her many movies. Including Max Max [Again, great research - Editor].

The eyes have it.
Lindy is Tony Soprano
This is a comparison I've been making for years. Lindy has a certain "aura" that reminds me a little of the the mafia boss with a conscience. There was a hotdog incident at his house which I don't want to go into right now [No, please do - Editor].
Tony Soprano was played by the late James Gandolfini.

Both know how to hide bodies
Marc is Casey Affleck
Honestly, this took a while to figure out because Marc looks like no other human being alive. We even tried those "Who is your celeb twin" apps and they threw errors and deleted themselves in a panic. This is the best we could do. Casey Affleck is of course Batman's younger brother [Have you ever read a comic? - Editor].

Yeah, it's not great is it.
Mark is Ansel Elgort
So one night I sat down to watch Baby Driver, featuring Ansel. It was uncanny how much he reminded me of our resident developer Mark. Even down to the facial expressions. It's uncanny.

I honestly have no idea which is which
Mark H is Ben Folds
Full disclosure, the photo Mark submitted could politely be described as "vintage" [Not sure that's polite - Editor]. However, as soon as I saw it, I was amazed at how much he looked like my favourite singer/songwriter Ben Folds. I'm not saying this photo of Mark his old, but lets say it cost us $10,000 to have an expert colour it from the black and white original.

Classic Mark
Matt is David Boreanez
Over the course of my 20s and 30s [Clearly not now you're old - Editor], I was often compared to "Angel from Buffy" played by David Boreanez. I thought it was because of my cool but brooding demeanour [lol - Editor] but maybe it's just one of those chance genetic occurrences.

Well, similar hair at least
Rhett is Bruce Willis
Rhett never lets our servers Die Hard [Jeez, you went there - Editor] but he does resemble Bruce Willis. It's not just that they visit the same hair dresser either.

Twins!
Ryan is Ethan Hawke
We've saved the best to last, because this comparison caused actual goosebumps. Someone even said "wow" when they saw it. These two could be related. Ethan Hawke is a huge movie star, so Ryan was quite happy with this comparison.

Uncle Ethan?
So, there you have it.

If there was a movie to be made featuring our lives, then this is the cast that would be our first choice.

Who do you look like? We've love to see your pictures too. Let us know below!