About Journal
Data Privacy Policy
Compliance with GDPR (General Data Protection Regulation)
Cookie policy



About Journal

ISSN: 2544-0780
e-ISSN: 2544-1671
DOI Journal prefix: 10.30464


The Journal of Mechanical and Energy Engineering as a continuation of Scientific Journal of Faculty of Mechanical Engineering of Koszalin University of Technology (PL: Zeszyty Naukowe Wydziału Mechanicznego Politechniki Koszalińskiej) published in Polish between 1975 and 2007.

Resumed in 2017 in a new form, the Journal of Mechanical and Energy Engineering publishes manuscripts on research, development and design related to science and technology in a field of Mechanical Engineering and Energy Engineering. A peer-reviewed interdisciplinary JMEE is published minimum 2 times per year in an open access formulaThere is no publication fee for the Authors of articles. The journal accepts manuscripts of two different types: original research papers and review papers.

  • Journal full name: Journal of Mechanical and Energy Engineering
  • Journal Journal Abbreviation: J Mech Energy Eng
  • Journal initials: JMEE


Annual schedule

The Journal of Mechanical and Energy Engineering is published two times per year and is issued free to all coumunity. Each year a new volume is published, divided into 2 issues. The issues are published on a schedule:
- issue 1 - end of June,
- issue 2 - end of December.


Ethics & disclosures

The Journal is committed to maintaining the highest level of integrity in the content published.

This journal has a Conflict of Interest policy in place.

The journal will be soon a member of the Committee on Publication Ethics (COPE) but will apply its principles on how to deal with acts of misconduct thereby committing to investigate allegations of misconduct in order to ensure the integrity of research.

The journal may use plagiarism detection software to screen the submissions. If plagiarism is identified, the COPE guidelines on plagiarism will be followed.

Content published in this journal is peer reviewed (Single Blind).


Data Privacy Policy

The data collected from registered and non-registered users of JMEE 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.

JMEE 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 (PKP) in an anonymized and aggregated form, with appropriate exceptions such as article metrics.

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.

The data will not be sold by JMEE 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 JMEE 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.



Compliance with GDPR

Data Administrator

  • The administrator of your personal data is:

Editorial team of
Journal of Mechanical and Energy Engineering (JMEE)

ISSN: 2544-0780
e-ISSN: 2544-1671
DOI: Journal prefix: 10.30464

Publishing House of Koszalin University of Technology
(Wydawnictwo Uczelniane Politechniki Koszalińskiej)
Racławicka 15-17 St.
75-620 Koszalin, Poland

  • Information Security Administrator - Data Protection Officer:

Mariusz Lenartowicz
Śniadeckich 2 St., building A, room 622
Phone: +48 (94) 34 78 622
Alternative e-mail:


What data do we process?  

Our Journal is provided by System OJS (Open Journal System) by PKP (Public Knowledge Project).

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.

When a visitor creates a user account in a PKP application, the following personal information is processed and stored: 

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


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. 


All PKP applications track 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.


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 (depends on Server provider Policy):

  • IP address information (including date, browser, etc.) in web server logs (separate from application log files as part of the Usage Statistics plugin).  



Personal informations (data) are stored in the application database, with the exception of any uploaded submission files, which are stored in the application’s submission files directory on the web server.  

Only the user password is encrypted.


  • Cookies: A cookie (usually titled “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, 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, 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

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

Contributor Metadata Information — 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.  

Editors can download this data via author and submission reports. 

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.

Workflow Data — 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 the data they have supplied, or that editorial staff have explicitly made available to them.  

General Visitor Information:

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



Register information — This data can be erased by the journal manager using the Merge Users tool, without affecting any editorial records.

Contributor Metadata Information — This data can be erased by any editor by editing a submission’s metadata. This can be done at any point of the submission process, including after publication.

Workflow Data — This data can only be erased by the editor, by rejecting and deleting the submission outright; or by a systems administrator via direct intervention into the underlying database or submission files directory.

General Visitor Information:

  • 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 requires system administrator access.



Cookie policy



Our JMEE OJS system uses cookies to manage user sessions (for which they are required). Cookies aren’t required to simply visit the site and read content. 

JMEE website use cookies to analyze the usage of website. This information includes the IP address, your browser type, the date and the time of your visit to our website as well as the cookie number.

Our cookies help us:

  • Improve the speed of the site
  • Continuously improve our website for you
  • Allow you to share pages with social networks like Facebook

We do not use cookies to:

  • Collect any personally identifiable information (without your express permission)
  • Collect any sensitive information (without your express permission)
  • Pass personally identifiable data to third parties
  • Pay sales commissions


Turning Cookies Off

You can usually switch cookies off by adjusting your browser settings to stop it from accepting cookies. Your browser help function will tell you how. Doing so however will limit the functionality of most of the world's websites as cookies are a standard part of websites.