A circular reading room with books and rows of desks

Journal service privacy · ISSN 0275-1607

Privacy for authors and readers

This policy describes the information used by the static Raritan frontend and the journal API that supports submissions and author services.

Information and its use

The journal service processes information needed to evaluate manuscripts, operate author accounts and respond to inquiries.

Manuscript records

Submission sends the title, author names, email, keywords, abstract, coauthor information and PDF to the journal service. Editors and reviewers use this material to assess and prepare the work.

Account credentials

The service returns a username and password after submission and uses them for tracking and author sign-in. The frontend displays the returned password but does not store it. Recovery uses the submission email address.

Author sessions

Sign-in stores a bearer token in sessionStorage. It remains within the browser tab’s session and is removed by sign-out, an authenticated unauthorized response or tab closure.

Final versions and payment

The proof workflow sends the final PDF and the payment details requested by the acceptance process. The service uses them to generate a proof and record confirmation.

Tracker and full text

A paper ID and password authorize status checks. Published full-text links are signed and expire after one hour. Galley-proof links expire after 15 minutes.

Contact tickets

An inquiry sends names, email, message and an optional paper ID so the office can answer. The service sends a receipt and notifies the office after accepting it.

Browser storage and privacy choices

The frontend has no analytics, advertising trackers or account cookies.

Captcha providers

Where the deployed service requires Turnstile or reCAPTCHA, the relevant provider script loads on submission, recovery or contact forms. That provider processes technical information under its own privacy terms.

Fonts and local assets

Source Serif 4 and Libre Franklin load from Google Fonts, which receives the connection data needed to deliver the fonts. Photographs and application code are served from this site.

Server records

The backend may record network, security and editorial logs needed to prevent abuse and maintain the manuscript record. The journal service states a limit of 20 tracker attempts per 15 minutes per IP address.

Retention and correction

Editorial records may need to remain for research integrity and publication history. To request access, correction or deletion of other information, contact the office and identify the relevant email or paper ID.

Security and external links

Signed PDF links should not be forwarded publicly. Directions and source credits open external sites with referrer protection and no new-window access to this page.

Privacy questions

Write to [email protected] or use the contact form. Do not place an account password in an inquiry.