Privacy notice

Last updated 2 November 2026

Effective 2 November 2026.

Who is responsible

JAIGR is operated by Dr. Ding Han as an individual, who is the controller of the personal data processed through jaigr.org. Contact: [email protected].

What we collect

Account data from Google sign-in: your Google account identifier, name and email address. We never receive your password.
Submissions: the text, references, AI declarations and workflow, competing-interests statement, and the author name, affiliation and ORCID iD you enter, with the time you accepted these terms.
Technical data: web server logs with IP addresses, the pages requested, time and browser details.

Why we process it

We process account and submission data because it is necessary to provide the submission, assessment and publication service you request and to perform our agreement with you. We keep security logs, prevent abuse, keep editorial records and preserve the published scholarly record for our legitimate interests in running a secure and trustworthy journal. We may also process data where needed to comply with a legal obligation or to establish, exercise or defend legal claims. You may object to processing based on legitimate interests (see your rights below).

What is public

For published articles: the author name, affiliation and ORCID iD you entered, the text, the declarations, the competing-interests statement and the assessment. Your email address and Google identifier are never published. Unpublished submissions are visible only to you and the editor.

Who else receives data

IONOS hosts the website, database and server logs on a server in Kansas City, Missouri, United States.
Google provides sign-in and supplies your Google account identifier, name and email address.
Cloudflare provides domain registration and DNS. If its proxy or security features are enabled, Cloudflare may also process IP addresses and request details.
vast.ai and the rented GPU host (never one located in China) run the weekly assessment. Each request contains one citation-bearing claim from a submission and selected passages from the cited papers; a claim can contain personal data if the manuscript does. Account identifiers and email addresses are not sent. Inputs are not used to train any model. The rented machine is destroyed after the run, but the provider or host may keep their own security logs.
Crossref, DataCite, OpenAlex and Unpaywall receive the DOIs of cited works for registry and open-access lookups, and arXiv and other open-access hosts receive requests for the cited papers. These requests come from our server and may carry the journal's contact address; they do not include your account details.
Professional advisers, courts, regulators or law enforcement, where disclosure is legally required or needed to protect legal rights.

Your data is therefore processed in the United States, and assessment inputs may be processed in another country where the rented GPU host is located. These countries may not offer the same legal protection as your own.

How long we keep it

Accounts are kept while they are in use. When you ask us to delete your account, we erase your name, email address and Google link, and the content of your unpublished submissions, within 30 days.
Unpublished submissions (withdrawn, returned, or left needing fixes) are erased automatically 12 months after their last change. A minimal record of editorial decisions (what was decided and when) is kept without the content.
Assessment working files from the weekly run are deleted within 30 days.
Web server logs are kept for up to 60 days.
Backups of the database are kept for 30 days, so erased data can remain in a backup for up to 30 more days; backups are restored only for disaster recovery.
Published articles, including every version, the assessment, notices and the minimal editorial record, are kept permanently as the scholarly record (see corrections and retractions). Your email address and Google identifier are never part of it.

Cookies

We use no advertising or analytics cookies. We set a sessionid cookie to keep you signed in (up to two weeks) and a csrftoken cookie to protect forms (up to one year). Both are strictly necessary and are not used for tracking. Google sets its own cookies when you use its sign-in page, and Cloudflare may set security cookies if its proxy is enabled. We will update this notice, and ask for consent where required, before adding any non-essential cookie.

Your rights

Depending on the law that applies to you, you may ask for access to, correction of, deletion of, restriction of, or a portable copy of your personal data, and you may object to processing based on legitimate interests. These rights are not absolute: for example, deletion does not usually extend to a published version of record. We make no decisions with legal or similarly significant effects solely by automated means: automated checks produce evidence, and the editor makes every publication decision.

Send requests to [email protected]. We may ask for information to confirm your identity, and we normally reply within one month. You may also complain to the data protection authority where you live or work, or where you believe an infringement happened (in the UK, the Information Commissioner's Office at ico.org.uk).

California residents

We collect identifiers, internet activity (server logs), professional information that authors provide, and submitted content, from the sources and for the purposes described above. We do not sell personal information or share it for cross-context behavioural advertising, and we have not done so in the past 12 months. You may ask to know, correct or delete your personal information using the contact address above, and you will not be treated differently for doing so.

Children

The service is not intended for anyone under 18, and submitting requires confirming that you are at least 18.

Changes

We will post any change to this notice here with a new effective date, and announce material changes on the home page before they take effect.