General Admission

Privacy Statement

Privacy and User Data Policy

GDPR Update:

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 informs 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.

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.

Requests per item (a) through (e) above should be sent to the journal's mailbox, jom(at)pnpco.com

The names and email addresses entered in this journal site will be used exclusively for the stated purposes of this journal and will not be made available for any other purpose or to any other party.

What Data does this Website Process?

The system, based the PKP Open Journal System applications, process personal data as a fundamental part of their operations. Most data is only provided by consent, ie. through manual user registration, though some visitation data (eg. cookies, usage logs) may also be recorded.

User Registration Data

When a visitor creates a user account in a PKP application, the following personal information is processed and stored (with some minor variation between OMP and OJS, and from version to version):

●   Salutation

●   First name*

●   Middle name

●   Last name*

●   Suffix

●   Username

●   Gender

●   Password (encrypted)

●   Email address*

●   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)

Only the username, first name, last name, email and password fields are required.

Storage

This information is stored in the application database. Only the user password

is encrypted.

Availability and Access

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 can be downloaded by journal managers in XML format. The data is not otherwise publicly available.

Erasure

This data can be erased by the journal manager using the Merge Users tool, without affecting any editorial records. The erasure is subject to the considerations raised in the section “Scholarly Publishing, Data Privacy, and the Public Interest”, above.

Contributor Metadata Information

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. The following contributor information is collected:

●   Salutation

●   First name*

●   Middle name

●   Last name*

●   Email address*

●   Suffix

●   ORCiD ID

●   Website

●   Country*

●   Affiliation

●   Biography

Only the first name, last name, email address and country fields are required.

Storage

This information is stored in the application database.

Data Transfer

We do not sell or transfer to third parties user information from this system.

General Visitor Information

PKP applications also collect general visitor usage data, including:

● Cookie information, to manage session history. Cookies are required to maintain a login session in PKP applications.

● Optionally, detailed usage log data, including: IP address; pages visited; date visited; and browser information, in application log files, as part of the Usage Statistics plugin. An anonymization option is available to privatize this information.

● Optionally, country, region and city information, in the metrics database. This data collection requires additional setup and is not enabled by default.

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).

Detailed instructions in limiting the amount of data you collect, and providing consent for the data you collect, can be found below.

Storage

● Cookies: A cookie (usually titled “OJSSID” or “OMPSID”) 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, OJS will still work properly, though they will not be able to log in.)

● Usage Statistics log files: As part of the usage statistics framework and plugin, OJS may store detailed application log files in the submission files directory (configured as the files_dir parameter in the OJS config.inc.php file), in a “usageStats” directory.

● Geographical data: Filtered usage data, including possibly geographic data, is also stored in the OJS database, in a “metrics” table.

Availability and Access

● Cookies: These are available via the visitor’s browser settings.

● Usage Statistics log files: Only individuals with server file access can access application log files.

● Geographical data: Journal Managers can access filtered usage data by using the OJS usage report plugins.

Erasure

● Cookies: These can be deleted via the visitor browser.

● Usage Statistics log files: These can be erased by system administrators with file access.

● Geographical data: This can only be erased by deleting records from the database directly, which also typically requires system administrator access.

Portions of this privacy statement are copyright by Simon Fraiser University Licensed wth CC4.0-BY.