geolocation column of members table holds many unneeded properties including IP address and coordinates (derived from the IP address) of the members. We only use country, country_code and region properties of that object stored in geolocation column. These "unintended" extra data poses a privacy and security risk for all Ghost sites. Also these "personally identifiable" informations that we collect without consent is against many privacy rules like GDPR.
We should only keep data we need on that column. Also it's needed to have a one-time job that cleans-up those geolocation data previously stored.
geolocationcolumn ofmemberstable holds many unneeded properties including IP address and coordinates (derived from the IP address) of the members. We only usecountry,country_codeandregionproperties of that object stored ingeolocationcolumn. These "unintended" extra data poses a privacy and security risk for all Ghost sites. Also these "personally identifiable" informations that we collect without consent is against many privacy rules like GDPR.We should only keep data we need on that column. Also it's needed to have a one-time job that cleans-up those geolocation data previously stored.