Privacy

Introduction
Personal Data Protection
Export
Erasure
Pollicy
GDPR
Support

Introduction

This document reviews how GeoDirectory handles privacy of personal user data. The document is intended for site managers who are ultimately responsible for personal data protection.

As a site manager you have no doubt heard that 2018 might be called ‘the year of personal data privacy’. It has been a year filled with news articles and government policies about how personal data should be stored, shared, an handled in order to respect privacy.

As a site manager, you have probably also heard that in the end, you are ultimately responsible for the care and safekeeping of your site user’s data. As the developers of GeoDirectory, we want to help you as best we can, but we are not lawyers. We can tell you what personal data has been stored by the plugin, and we make sure that this data can be exported to users as well as exported and erased upon request.

Export

Site managers may export GeoDirectory related personal data for users. That will include things like:

Favorites
Ratings
Reviews
Listings

Erasure

Site managers may erase GeoDirectory personal data for users. GeoDirectory Data erasure includes:

Favorites

Things not deleted but made anonymous will include:

Listngs
Reviews
Ratings

Privacy Policy

Every WordPress install now comes with tools to create a Privacy Policy for the site. This can be found at

WordPress – Settings – Privacy

GeoDirectory will contribute some text that you can choose to include in your site policy. The code may change, so, you can look at it inside you site, or view the file on Github.

GDPR

GeoDirectory core and addons are GDPR compliant. Several features were removed (send to friend and social share).

Further, it has been decided that an additional marketing opt-in on the add-listing page (in addition to the optional “Terms and Conditions” option) is not needed because in all cases for the use of GeoDirectory the intended legal basis is “legitimate interests” as opposed to requiring consent.

This is the case for two reasons:
A. If the user did not give consent then nothing would happen and no data would be processed, so there is no “genuine choice”, and therefore consent is not appropriate.
B. All the data entered is used “as reasonably expected” by the forms.

Support

For additional questions about privacy, please create a support topic.

GeoDirectory Core