Moringa SP takes the protection of private data very seriously. We want you to know what kind of data we are keeping and how we use them. As commercial publisher we are governed by the German Data Protection Law (BDSG) and the Telemedia Law (TMG). We have technical and organisatorial measures in place that your data is kept save and the requirements by law are fulfilled by us and external parties.
Personal data is information related to your identity, like your name, adress, phone number. Other information that can not be directly related to you is not personal data.
You can use our services as reader anonymously and without any registration. If you decide to submit data or articles or use our services as reviewer or editor, you will need to register in our journal system. In the spirit of Open Science we ask you to provide your real data when you register, though it remains your free decision how much of your personal data your are entering into the system. Please speak to our editors if you require anonymity so we can take the necessary steps. We may reject you submission (articles, data or reviews) otherwise.
By law we are required to remove unlawful comments or submissions on request and we can be forced to hand over user details from our system if asked by law officials.
Please note that all the data you enter on your public profile in the journal system will be visible to other users of the system.
Your personal data is saved on specially protected servers in the EU. Technical measures are in place that only authorized personell will have access to that data for technical or publication, service and payment related reasons.
Storage of IP addresses
Access to the webserver and the journal system is logged internally for security, development and technical issues. This data (like IP addresses, date, time and accessed resources) in itself is not personal, as long as no connection to your identity is made. We deploy state of the art HTTPS connections to protect you against this.
IP Addresses will be saved for a maximum of 7 days and then will be anonymised or deleted.
For our journals we use the Open Journal Systems (OJS). The OJS platform sets a cookie called OJSSID, that contains a machine-generated session-id for the OJS-platform that will keep track of your browsing session and log-in to the OJS-webpage. This cookie is normally deleted at the end of the browsing session.
If you check “remember me” when you log in, you may quit your browser and open it at a later time, and you will still be logged in. In that case this cookie will expire after 30 days since your last visit or until you log out and close your browser. This cookie is necessary in order to log in to the OJS platform. You will still be able to access all articles on the OJS platform with cookies disabled, but you will not be able to perform any tasks that requires the user to be logged in.
We are using the privacy aware Matomo tool to get an impression of the traffic to our side and be able to quickly detect problems on our pages. This way we know what people are looking at on our web-site and (to a certain extent) from what country they are, but we will have no idea who they were. That means that we will not be able to tell that it was you who visited our website. If that still bothers you, you can switch tracking on and off here:
Right To Correction and Deletion Of Personal Data.
If you entered personal data in the journal system, you can change or delete that data anytime by logging into the system and making the changes in your profile. Other personal data related to billing and service orders will be stored the time we are required to do so by German law. In case we got something wrong just drop us a message and we will correct it.
We use a distributed global file system to persistent publish articles and related datasets. It is in the censorship resistant nature of that technology that anything that has been published in the network will stay available as long as one copy of the original data is retained in the network. In case that we are ordered to retract an article or data set (either by the authors or by law), we will publish a notice and then remove the relevant data from our servers in the network and mark it as blacklisted. This will mean that any access to that data via our system will be blocked. However, given the distributed nature of the system, other participants cannot be forced by us to do the same and might continue to share the data.