In accordance with the article 13 of the EU General Data Protection Regulation (GDPR) 2016/679, the Data Controller, Applied Medical Informatics (ami.info.umfcluj.ro) journal (in the person of the legal representative pro-tempore, with headquarters presented in the contact page - hereafter named Applied Medical Informatics) guarantees the observance of the rules on personal data protection.
This journal may change this policy from time to time by updating this page. You should check this page from time to time to ensure that you are happy with any changes. This policy is effective from 25 may 2018.
The data collected from registered and non-registered users of this journal falls within the scope of the standard functioning of peer-reviewed journals. It includes information that makes communication possible for the editorial process; it is used to inform readers about the authorship and editing of content; it enables collecting aggregated data on readership behaviors, as well as tracking geopolitical and social elements of scholarly communication. The personal data gathered and will not be given to third parties.
This journal’s editorial team uses this data to guide its work in publishing and improving this journal. Data that will assist in developing this publishing platform may be shared with its developer Public Knowledge Project in an anonymized and aggregated form, with appropriate exceptions such as article metrics. The data will not be sold by this journal or PKP nor will it be used for purposes other than those stated here. The authors published in this journal are responsible for the human subject data that figures in the research reported here.
Those involved in editing this journal seek to be compliant with industry standards for data privacy, including the European Union’s General Data Protection Regulation (GDPR) provision for “data subject rights” that include (a) breach notification; (b) right of access; (c) the right to be forgotten; (d) data portability; and (e) privacy by design. The GDPR also allows for the recognition of “the public interest in the availability of the data,” which has a particular saliency for those involved in maintaining, with the greatest integrity possible, the public record of scholarly publishing.
The present privacy sets the legal basis upon which the personal data collected will be used:
* - Their principal use is solely related to the services offered by the journal, i.e., submission of scientific manuscripts to be evaluated for publication; request to evaluate scientific contributions (referee); correspondence with the corresponding Author during the editing workflow of the article; newsletter informing about the publication of the most recent issue, or informing about changes in the policies of the website.
* - The user’s consent is requested before entering personal data.
* - By no means the collected data will be sold or disclosed to third parties.
What we collect
We may collect the following information:
* - When a user creates an account on the website: first name, last name, username, email address, and password (encrypted) - that are required.
* - When a manuscript is submitted to a PKP application, contributor information is
included. Contributors can be authors, translators, volume editors, and so on.
This information is stored as submission metadata and is provided as part of
any published manuscript record. Only the first name, last name, email address and country fields are required.
* - Other information that is not mandatory, only if it is provided by the user (Salutation, Middle name, Suffix, Gender, ORCiD ID, Website, Mailing Address, Country, Phone, Fax, Affiliation, Biography, Registration date, Last login date, Locales, Reviewing interests, Role registrations (author, reader, and/or reviewer)), while creating an account, or while submitting a manuscript.
* - The website tracks workflow information, mostly as submission-specific
editorial history. The system tracks:All actions taken on a submission, and by whom; All notifications sent regarding a submission (including who sent and
received the notification); All reviewer recommendations; All editorial decisions; All files uploaded as part of the submission process, including files that may have personally identifying information in the form of file metadata or in the files themselves.
* - General visitor information: Cookie information, to manage session history. Optionally, detailed usage log data, including: IP address; pages visited; date visited; and browser information, in application log files. Optionally, country, region and city information, in the metrics database. Other data may be tracked, either on the server or via third parties: Script loads from CDN servers; IP address information (including date, browser, etc.) in web server logs (separate from application log files as part of the Usage Statistics plugin).
What we do with the information we gather
We require this information to understand your needs and provide you with a better service, and in particular for the following reasons:
* - Internal record keeping.
* - We may use the information to improve our products and services.
* - Information from the user registration. This information is available to the user via their User Profile (and, with the exception of the username and dates, can be edited). System administrators, journal managers, and editors can also access and edit this data (except the username and dates) via the application back end. The data is not otherwise publicly available.
* - Information about submissions of manuscripts. This information is available to almost any submission participant, with some restrictions to preserve the blind peer-review process. In short: contributing authors, editors and editorial assistants can all see this data; in most cases, only editorial staff can edit this data after submission. Most importantly: once a submission has been published, this data is made publicly available online in a variety of ways. It is available on the submission home page to readers, is available to indexing services in underlying metadata tags, is available via an OAI-PMH endpoint for harvesting, and may be made available in any number of ways via other system plugins.
* - Information about workflow. Submission participants have access to different amounts of workflow data depending on their role. Journal managers and editors can access all submission data; section editors and editorial assistants can access all submission data only for those submissions to which they have been assigned;
authors have limited access to their own submissions and are only able to see 10the data they have supplied, or that editorial staff have explicitly made available to them.
* - We may from time to time send emails regarding new issues being published, information about the submission or editorial process, or other information regarding website activity, as well as promotional emails about new products, special offers or other information which we think you may find interesting using the email address which you have provided, in accordance with the current regulations, being understood that the person concerned has the right to object to this use at any time.
* - Additional information (such as domain names, IP addresses and browser types), detected through our website, is used to track traffic statistics.
* - The data will be processed only by those with the authority to do so, nominated by the owner to deal with relationships with clients. In no way shall they be circulated or disclosed to third parties, either national or international.
* - The data will be stored in a form that allows the identification of the person concerned for a period not exceeding that necessary to fulfil the purposes for which they were collected.
We are committed to ensuring that your information is secure. In order to prevent unauthorised access or disclosure,we have put in place suitable physical, electronic and managerial procedures to safeguard and secure the information we collect online
Links to other websites
Our website may contain links to other websites of interest. However, once you have used these links to leave our site, you should note that we do not have any control over that other website. Therefore, we cannot be responsible for the protection and privacy of any information which you provide whilst visiting such sites and such sites are not governed by this privacy statement. You should exercise caution and look at the privacy statement applicable to the website in question.
Controlling your personal information
You may choose to restrict the collection or use of your personal information in the following ways:
* - whenever you are asked to fill in a form on the website, please make sure you enter only the information you want to be accessible.
* - you can edit at any time what you completed in the filled forms, to erase or to modify what you entered before.
* - at any time users can decide to retract or request the cancellation, modification or update of any personal information in our possession, either doing it personally by accessing their personal area, using their credentials (username and password), or by sending an e-mail to contact address.
* - you may request details of personal information which we hold about you under the GDRP. If you would like a copy of the information held on you please write to the website contact address.
* - any author or contributor not registered in the system that wishes to anonymize their data can contact the journal editorial team who will do it for them.
* - To receive confirmation of the existence of their personal data in the database of the Controller, and right to access them by means of log in data (username and password), or by contacting the Controller.
* - To know the objectives and scopes, the legal basis and methods of treatment of the data
* - To know who the appointed person responsible for the treatment of data is
* - To modify, integrate, and/or update their data, in accordance with the service requested and offered by the journal;
* - To cancel their data if treated in violation of the law. There are certain specific cases, however, in which the journal must maintain the collected data, and cannot cancel them. For instance, if the data inserted are of users who have acted as Authors, Reviewers and/or Subscribers to the journal, these data are necessary to the regular and legitimate functioning of the website.
* - To withdraw their consent to the treatment of data, in accordance with the previous point.
* - To lodge a complaint with the competent supervisory authority identified under art. 77 of EU Regulation 2016/679 in the case of alleged violation of the regulations governing the processing of personal data.
To make this site work properly, we sometimes place small data files called cookies on your device. Most big websites do this too.
What are cookies
A cookie is a small text file that a website saves on your computer or mobile device when you visit the site. It enables the website to remember your actions and preferences (such as login, font size and other display preferences) over a period of time, so you don’t have to keep re-entering them whenever you come back to the site or browse from one page to another.
A cookie (containing in its name “OJSSID”) is created when first visiting a PKP application and is stored on the visitor’s computer. It is only used to store a session ID, and to facilitate logins. (If the visitor blocks cookies, the website will still work properly, though they will not be able to log in.)
* - to allow the login, submission of manuscripts, and the editorial process
* - your display preferences, such as font size
Also, some youtube.com videos embedded in our pages, that are supplementary files of the published manuscripts, use a cookie to gather statistics on how you got there and what videos you visited.
Overall, cookies help us provide you with a better website, by enabling us to monitor which pages you find useful and which you do not. A cookie in no way gives us access to your computer or any information about you, other than the data you choose to share with us.
You can choose to accept or decline cookies. Most web browsers automatically accept cookies, but you can usually modify your browser setting to decline cookies if you prefer. This may prevent you from taking full advantage of the website - log in, submission, and editorial process, but this will not impede you accessing published manuscripts.
Different types of cookies exist. We report below some kinds of cookies that can be used in this website, and a brief description of the purpose of their use
Cookies of this type are necessary for the proper functioning of some areas of the site. Cookies in this category include both persistent cookies and session cookies. Without these, the site or portions of it may not work properly, therefore, they are always used, regardless of user preferences. Cookies in this category are always sent from our domain.
Cookies of this type are used to collect information on the use of the site. The Data Controller uses this information for statistical analysis to improve the site and simplify its use, as well as to monitor correct operational activity. This type of cookie collects information anonymously about user activity on the site and the way in which users arrived at the site and the pages visited. Cookies in this category are sent from the site itself
Cookies for the integration of third-party functionality
Cookies of this type are used to integrate third-party functionality in the site (e.g. youtube videos for supplementary materials). Cookies in this category can be sent from the domains of the partner sites or from those that offer the features present on the site. The Data Controller is not required to obtain user consent for Functionality cookies.
How to control cookies
You can control and/or delete cookies as you wish – for details, see aboutcookies.org. You can delete all cookies that are already on your computer and you can set most browsers to prevent them from being placed. If you do this, however, you may have to manually adjust some preferences every time you visit a site and some services and functionalities may not work.