FAIR PRESS JOURNALS

FAIR Press Journals · About the publisher

Privacy

last updated 2026-09-05

We hold what a journal needs in order to run: your account, the paper you send us, and the record of the decision we made on it. This site sets no cookies, makes no requests to any third party, and shows no consent banner. You can verify that in your browser's developer tools in a few seconds. We sell nothing, we share nothing for advertising, and we run no analytics that identify you.

Who is responsible. FAIR Press Journals GmbH, Olten, Switzerland, commercial register CHE-237.825.846, operates this site and the journals published on it. The postal address and the people behind it are on the legal notice. For anything in this notice, write to privacy@fairpressjournals.com.

If you only read the site

Our web server keeps the usual request log: IP address, time, the page requested, the browser's user-agent string. Every web server keeps this. We use it for security and for aggregate counts, we do not analyse it for behaviour, and we do not merge it with anything else.

We host our fonts ourselves. Nothing on the page loads from another company's server, so no third party learns that you visited us.

If you use the scope check

The scope check on a journal's home page sends the abstract you paste to our own server, which asks a language model whether the topic fits the journal. We do not store the abstract. What we keep is a counter row: the journal, the verdict, the length of the text, and a one-way hash of your IP address that lets us hold a rate limit. The hash is erased within the hour. The counter row is deleted after 90 days. You need no account, and we do not learn who you are.

If you submit a paper

What you give us. An account, which is an email address and nothing else, because you sign in with a six-digit code instead of a password. For the submission: title, abstract, keywords, subject areas, the names, affiliations, countries, email addresses and ORCID iDs of the authors, the manuscript and its source files, your statements on data and code availability, ethics and AI use, and whatever you write in the cover note.

Why we may process it. To handle the submission you asked us to handle, and to run the journal, which needs an editorial record that documents each decision.

Who sees it. The editors of the journal you submitted to. The database enforces the access rules itself. The editorial area also requires a second authentication factor.

What happens to the manuscript. How the review works is set out on the peer-review policy of the journal you submitted to (linked from our policies). Your manuscript and the documents you submit with it are processed by the language-model provider named at the end of this page, under a contract that forbids training on your work and requires deletion within 30 days. A named human editor reads the result and signs every decision.

Your unpublished paper is not sent to outside referees. In conventional peer review a manuscript is emailed to two or three strangers who are under no contract with anyone. Here it stays with the editors and the engine.

Where it is stored. In our database and file storage operated by Supabase in the European Union (Ireland). A nightly copy of the database and the stored files is held on storage in Switzerland under the publisher's own control and rotated after 30 days.

Email we send you

We send transactional mail through Resend. Per message we record the recipient, the time, and whether it was delivered, bounced or opened, because an editor has to be able to see that a decision reached its author. If you subscribe to an announcement list, we keep the address and the record of your confirmation. Every message carries an unsubscribe link.

What becomes public

If your paper is accepted and published, the article and its metadata become public and permanent: author names, affiliations, ORCID iDs where you supplied them, and the article itself under CC-BY. Metadata will be deposited to Crossref and an archive copy to Zenodo upon publication. A published DOI is meant to resolve forever. We cannot withdraw it. Corrections and retractions follow each journal's corrections policy.

How long we keep things

  • Manuscript, source files and bundles of a rejected or withdrawn submission: deleted twelve months after the decision.
  • The editorial record of a decision (submission metadata, review runs, verdicts, the signature): kept for ten years, then anonymised. It documents a decision and protects both sides.
  • Accounts with no submission: deleted after three years without a sign-in.
  • Delivery records for email: 24 months.
  • Rate-limit ledgers for the upload scan and the scope check: 90 days.
  • Backups: rotated after 30 days.

Your rights

You may ask what we hold about you, have it corrected, ask for deletion, object to a processing, or receive a copy in a portable format. Write to privacy@fairpressjournals.com and we answer within 30 days.

Two limits, in plain sight. A signed editorial decision is immutable by design, because a decision record that can be edited afterwards is worth nothing to anyone. A published article cannot be unpublished, and its DOI stays resolvable.

You may also complain to a supervisory authority: in Switzerland the Federal Data Protection and Information Commissioner, in the European Union the authority of the country you live in.

Who processes data for us

  • Supabase, database, accounts, file storage and server functions, in the European Union (Ireland).
  • Hostinger, hosting of the websites and their server logs.
  • Resend, sending our email and recording delivery, in the European Union.
  • Anthropic (United States), the language-model provider. Its models process submitted manuscripts and the documents that travel with them, and the text pasted into the scope check. Data-processing agreement with EU standard contractual clauses, no training, deletion within 30 days.
  • Crossref and Zenodo, registration and archiving of published articles. This applies from the first publication, and that metadata is public by design.

Changes

We date this notice and say what changed. This version is of 5 September 2026.