SophaxisPreprints in Philosophy and Mathematics

日本語

Submission Policy

Last updated: 2026-11-12.

Japanese: 投稿の規程(日本語訳). It is a translation; where the two differ, the English text applies.

The Submission Policy says who can submit what to Sophaxis, and what the submitter confirms.

The laws, licences and terms that this page cites are quoted at the end of each section that cites them. Japanese statutes are quoted in full, as the e-Gov law API gives them. The other texts are quoted word for word from their official sources, as fetched on 2026-11-12, and are not translated. A citation whose source could not be fetched is named there as not quoted, with the reason.

Who can submit

If you are worried about your personal data because Vercel, which serves the site, or GitHub, which keeps the submissions, may use what they hold to train AI models, do not submit. The Privacy Policy explains these uses.

Only an author of a work can submit it. Sophaxis confirms this through ORCID, before a moderator reads the work.

A submission that does not pass both is not listed. The first check confirms that the person who controls the ORCID record opened the issue. It is not an official identity check. Authors without an ORCID iD cannot submit. From 2026-11-21, a person under 13 cannot submit. A submitter under 18 needs the consent of a parent or guardian. From 2026-11-22, Sophaxis does not list work by an author under 18 who lives or stays in India. From 2027-05-13, Rule 10 of India's Digital Personal Data Protection Rules, 2025 lets the data of a person under 18 be processed only with the verifiable consent of a parent, and Sophaxis does not verify that consent. From 2026-11-22, Sophaxis does not list work by an author who lives in any of the 43 places in the table below, or who stays in one between the submission and the listing, and the submitter confirms this in the form. For the 15 places for which the table gives 2026-11-26, this applies from 2026-11-26. A stay counts even if it is short, such as for travel, work or study. Stays count because the laws of several of these places reach people who are there, not only people who live there; Article 3(2) of the GDPR, for example, speaks of data subjects who are in the Union. Sophaxis does not offer its service there, because it meets none of the duties that the law there places, or is reported to place, on a service offered to people there; the Privacy Policy says more. This rule depends only on where an author lives or stays, not on nationality, race, ethnic origin or any other personal characteristic. An author of any nationality who lives elsewhere and does not stay there can submit, and an author who lives or stays there cannot, whatever their nationality. The reasons are laws that require a local representative, the storage of personal data in the country, or registration there (among them Article 27 of the GDPR and of the UK GDPR; Article 13 of the EU Digital Services Act; Article 53 of China's Personal Information Protection Law; section 37(5) of Thailand's Personal Data Protection Act), which Sophaxis, run unpaid by one person within free services, does not have; the operator has decided not to appoint a representative, as the Privacy Policy explains. The rule is that Sophaxis is not offered where a law requires, or is reported to require, a service offered to people there to have a representative there, to keep personal data there, to register there, or to meet conditions before personal data leaves the place that Sophaxis cannot meet. From 2026-11-26, the rule also covers two more kinds of duty that Sophaxis cannot meet. One is a duty to give people there, before their personal data is collected, a postal address or a telephone number of the operator, which Sophaxis does not publish. The other is a duty to process the personal data of a minor there only with a parent's consent that the service confirms, or not at all. From the same day, a place is also not offered when its data protection law, found by a survey of the laws of 195 countries made on 2026-11-12, could not be read at its source, through its official address and one other route; the table gives such a place as "No, not fetched". A place is added to the list as soon as such a duty is reported, before its law has been read at its source, and it is taken off only after that law has been read at its source and found not to reach Sophaxis. Each change to the list is announced on the top page before it takes effect, as the Terms of Use set out. Sophaxis relies on the submitter's confirmation and does not check where authors live or stay. If it turns out that an author lives there, or stayed there between the submission and the listing, the record is removed under the Takedown Policy, and the operator reviews the decision on a representative.

PlaceWhat the law requiresLawRead at its sourceFrom
The European UnionA representativeGDPR Article 27; Digital Services Act Article 13Yes2026-11-22
The European Economic AreaA representativeGDPR Article 27, as applied in the EEAYes2026-11-22
The United KingdomA representativeUK GDPR Article 27Yes2026-11-22
ChinaA representativePersonal Information Protection Law, Article 53Yes2026-11-22
ThailandA representativePersonal Data Protection Act, section 37(5)Yes2026-11-22
RussiaStorage of personal data thereFederal Law No. 152-FZ, Article 1(1.1) and Article 18(5)Yes2026-11-22
TürkiyeRegistration through a representative thereRegulation on the Data Controllers' RegistryNo, as reported2026-11-22
EgyptA representative and a licenceLaw No. 151 of 2020 and its Executive Regulation, Article 3No, as reported2026-11-22
PeruA representativeRegulation of Law No. 29733 (Supreme Decree No. 016-2024-JUS)No, as reported2026-11-22
AlbaniaA representativeLaw No. 124/2024 on Personal Data ProtectionNo, as reported2026-11-22
MonacoA representativeLaw No. 1.565, Article 25Yes2026-11-22
GuernseyA representativeData Protection (Bailiwick of Guernsey) Law, 2017No, as reported2026-11-22
BotswanaA representativeData Protection Act 2024, section 54No, as reported2026-11-22
EcuadorA representativeRegulation of the Organic Law on Personal Data Protection, Article 3No, as reported2026-11-22
IraqNotice to the regulator before the service startsFramework Regulations for Digital Platforms and Services (2025), Articles 4 and 5Yes2026-11-22
IndonesiaRegistrationRegulation of the Minister of Communication and Informatics No. 5 of 2020, as amendedNo, as reported2026-11-22
RwandaRegistration and storage of personal data thereLaw No. 058/2021, Articles 2, 29 and 50Yes2026-11-22
ZambiaRegistration and storage of personal data thereData Protection Act 2021, sections 19 and 70No, as reported2026-11-22
EthiopiaStorage of personal data therePersonal Data Protection Proclamation No. 1321/2024No, as reported2026-11-22
The Democratic Republic of the CongoStorage of personal data there and an authorisationOrdonnance-loi No. 23/010 (Digital Code), Articles 184, 186, 188 and 201 (read in a copy that is not the official journal)In part2026-11-22
KazakhstanStorage of personal data thereLaw No. 94-V on Personal Data, Articles 3 and 12(2)Yes2026-11-22
TunisiaA declaration by a controller who resides thereOrganic Law No. 2004-63No, as reported2026-11-22
UgandaRegistrationData Protection and Privacy Act 2019, section 29No, as reported2026-11-22
GuineaStorage of personal data thereLaw No. L/2016/037/AN on Cybersecurity and Personal Data ProtectionNo, as reported2026-11-22
MadagascarStorage of personal data thereLaw No. 2014-038 on Personal Data ProtectionNo, as reported2026-11-22
BoliviaStorage of personal data thereLaw No. 164, General Law on TelecommunicationsNo, as reported2026-11-22
Costa RicaRegistrationLaw No. 8968, Article 21No, as reported2026-11-22
QuebecAn assessment and a written agreement before personal data leaves itAct respecting the protection of personal information in the private sector, section 17No, as reported2026-11-22
ArgentinaRegistration of its databases, the operator's postal address before personal data is collected, and an adequate level of protection before personal data leaves itLaw No. 25.326, Articles 6, 12 and 21Yes2026-11-26
ColombiaThe operator's telephone number before personal data is collected, and no processing of the personal data of minorsLaw 1581 of 2012, Articles 7 and 12Yes2026-11-26
GhanaRegistrationData Protection Act, 2012 (Act 843), sections 45, 46 and 53Yes2026-11-26
KoreaA parent's consent, confirmed, for a child under 14, and, for consent to a transfer abroad, each recipient's period of retentionPersonal Information Protection Act, Articles 22-2 and 28-8Yes2026-11-26
MexicoThe operator's postal address in the privacy noticeFederal Law on the Protection of Personal Data Held by Private Parties, Articles 1 and 15Yes2026-11-26
The PhilippinesA comparable level of protection by every recipientData Privacy Act of 2012, sections 6 and 21Yes2026-11-26
Saudi ArabiaConditions before personal data leaves itPersonal Data Protection Law, Article 29Yes2026-11-26
UruguayRegistration of its databases, and the operator's postal address before personal data is collectedLaw No. 18.331, Articles 3, 13 and 29Yes2026-11-26
ZimbabweAn adequate level of protection before personal data leaves itCyber and Data Protection Act [Chapter 12:07], sections 4 and 28 (read in a copy that is not the official journal)In part2026-11-26
KenyaRegistrationData Protection Act 2019No, as reported2026-11-26
TanzaniaRegistrationPersonal Data Protection Act, 2022No, as reported2026-11-26
South AfricaNot known: its data protection law could not be readProtection of Personal Information Act 4 of 2013No, not fetched2026-11-26
SingaporeNot known: its data protection law could not be readPersonal Data Protection Act 2012No, not fetched2026-11-26
The United Arab EmiratesNot known: its data protection law could not be readFederal Decree-Law No. 45 of 2021No, not fetched2026-11-26
QatarNot known: its data protection law could not be readLaw No. 13 of 2016No, not fetched2026-11-26
Text of General Data Protection Regulation (EU) 2016/679, Article 3(2)

2. This Regulation applies to the processing of personal data of data subjects who are in the Union by a controller or processor not established in the Union, where the processing activities are related to: (a) the offering of goods or services, irrespective of whether a payment of the data subject is required, to such data subjects in the Union; or (b) the monitoring of their behaviour as far as their behaviour takes place within the Union.

Quoted word for word from General Data Protection Regulation (EU) 2016/679, Article 3(2), as fetched on 2026-11-12.

Text of General Data Protection Regulation (EU) 2016/679, Article 27(1) and (2)

1. Where Article 3(2) applies, the controller or the processor shall designate in writing a representative in the Union. 2. The obligation laid down in paragraph 1 of this Article shall not apply to: (a) processing which is occasional, does not include, on a large scale, processing of special categories of data as referred to in Article 9(1) or processing of personal data relating to criminal convictions and offences referred to in Article 10, and is unlikely to result in a risk to the rights and freedoms of natural persons, taking into account the nature, context, scope and purposes of the processing; or (b) a public authority or body.

Quoted word for word from General Data Protection Regulation (EU) 2016/679, Article 27(1) and (2), as fetched on 2026-11-12.

Text of UK GDPR, Article 27(1) and (2) (legislation.gov.uk, with its marks of amendment)

1. Where Article 3(2) applies, the controller or the processor shall designate in writing a representative in [ F2 the United Kingdom ]. 2. The obligation laid down in paragraph 1 of this Article shall not apply to: (a) processing which is occasional, does not include, on a large scale, processing of special categories of data as referred to in Article 9(1) or processing of personal data relating to criminal convictions and offences referred to in Article 10, and is unlikely to result in a risk to the rights and freedoms of natural persons, taking into account the nature, context, scope and purposes of the processing; or (b) a public authority or body.

Quoted word for word from UK GDPR, Article 27(1) and (2) (legislation.gov.uk, with its marks of amendment), as fetched on 2026-11-12.

Text of Digital Services Act (EU) 2022/2065, Article 13(1)

1. Providers of intermediary services which do not have an establishment in the Union but which offer services in the Union shall designate, in writing, a legal or natural person to act as their legal representative in one of the Member States where the provider offers its services.

Quoted word for word from Digital Services Act (EU) 2022/2065, Article 13(1), as fetched on 2026-11-12.

Text of Personal Information Protection Law of the People’s Republic of China, Article 53 (the English text of the National People’s Congress)

Article 53 Personal information processors outside the territory of the People’s Republic of China as specified in the second paragraph of Article 3 of this Law shall set up specialized agencies or designate representatives within the territory of the People’s Republic of China to be responsible for handling personal information protection related matters, and shall submit the names, contact information, and other information of the agencies and representatives to the departments with personal information protection duties.

Quoted word for word from Personal Information Protection Law of the People’s Republic of China, Article 53 (the English text of the National People’s Congress), as fetched on 2026-11-12.

Text of Thailand, Personal Data Protection Act B.E. 2562, section 37(5) (ETDA’s English translation, marked unofficial)

(5) in the event of being the Data Controller pursuant to section 5 paragraph two, the Data Controller shall designate in writing a representative of the Data Controller who must be in the Kingdom of Thailand and be authorized to act on behalf of the Data Controller without any limitation of liability with respect to the collection, use or disclosure of the Personal Data according to the purposes of the Data Controller.

Quoted word for word from Thailand, Personal Data Protection Act B.E. 2562, section 37(5) (ETDA’s English translation, marked unofficial), as fetched on 2026-11-12.

Text of Federal Law No. 152-FZ on Personal Data, Article 1, part 1.1

Положения настоящего Федерального закона применяются к обработке персональных данных граждан Российской Федерации, осуществляемой иностранными юридическими лицами или иностранными физическими лицами, на основании договора, стороной которого являются граждане Российской Федерации, иных соглашений между иностранными юридическими лицами, иностранными физическими лицами и гражданами Российской Федерации либо на основании согласия гражданина Российской Федерации на обработку его персональных данных.

Quoted word for word from Federal Law No. 152-FZ on Personal Data, Article 1, part 1.1, as fetched on 2026-11-12.

Text of Federal Law No. 152-FZ on Personal Data, Article 18, part 5

При сборе персональных данных, в том числе посредством информационно-телекоммуникационной сети "Интернет", запись, систематизация, накопление, хранение, уточнение (обновление, изменение), извлечение персональных данных граждан Российской Федерации с использованием баз данных, находящихся за пределами территории Российской Федерации, не допускаются, за исключением случаев, указанных в пунктах 2, 3, 4, 8 части 1 статьи 6 настоящего Федерального закона.

Quoted word for word from Federal Law No. 152-FZ on Personal Data, Article 18, part 5, as fetched on 2026-11-12.

Text of Law No. 1.565 of 3 December 2024 on the protection of personal data (Monaco), Article 25

Lorsque le traitement concerne le second tiret du chiffre 1 de l'article 3, le responsable du traitement ou le sous-traitant désigne par tous moyens écrits un représentant dans la Principauté de Monaco ou, à défaut, au sein d'un État membre de l'Union européenne. Ce dernier est mandaté pour être le contact des personnes concernées par le traitement et de l'autorité de protection à qui elles peuvent s'adresser pour toutes questions. Cette obligation ne s'applique pas : à un traitement occasionnel, qui n'implique pas un traitement à grande échelle de données sensibles

Quoted word for word from Law No. 1.565 of 3 December 2024 on the protection of personal data (Monaco), Article 25, as fetched on 2026-11-12.

Text of Law No. 25.326 on the Protection of Personal Data (Argentina), Article 6(b)

Cuando se recaben datos personales se deberá informar previamente a sus titulares en forma expresa y clara: a) La finalidad para la que serán tratados y quiénes pueden ser sus destinatarios o clase de destinatarios; b) La existencia del archivo, registro, banco de datos, electrónico o de cualquier otro tipo, de que se trate y la identidad y domicilio de su responsable;

Quoted word for word from Law No. 25.326 on the Protection of Personal Data (Argentina), Article 6(b), as fetched on 2026-11-12.

Text of Law No. 25.326 on the Protection of Personal Data (Argentina), Article 12(1)

1. Es prohibida la transferencia de datos personales de cualquier tipo con países u organismos internacionales o supranacionales, que no propocionen niveles de protección adecuados.

Quoted word for word from Law No. 25.326 on the Protection of Personal Data (Argentina), Article 12(1), as fetched on 2026-11-12.

Text of Law No. 25.326 on the Protection of Personal Data (Argentina), Article 21(1)

1. Todo archivo, registro, base o banco de datos público, y privado destinado a proporcionar informes debe inscribirse en el Registro que al efecto habilite el organismo de control.

Quoted word for word from Law No. 25.326 on the Protection of Personal Data (Argentina), Article 21(1), as fetched on 2026-11-12.

Text of Law 1581 of 2012 (Colombia), Article 7

Queda proscrito el Tratamiento de datos personales de niños, niñas y adolescentes, salvo aquellos datos que sean de naturaleza pública.

Quoted word for word from Law 1581 of 2012 (Colombia), Article 7, as fetched on 2026-11-12.

Text of Law 1581 of 2012 (Colombia), Article 12(d)

El Responsable del Tratamiento, al momento de solicitar al Titular la autorización, deberá informarle de manera clara y expresa lo siguiente: a) El Tratamiento al cual serán sometidos sus datos personales y la finalidad del mismo; b) El carácter facultativo de la respuesta a las preguntas que le sean hechas, cuando estas versen sobre datos sensibles o sobre los datos de las niñas, niños y adolescentes; c) Los derechos que le asisten como Titular; d) La identificación, dirección física o electrónica y teléfono del Responsable del Tratamiento.

Quoted word for word from Law 1581 of 2012 (Colombia), Article 12(d), as fetched on 2026-11-12.

Text of Data Protection Act, 2012 (Act 843) (Ghana), section 45(1)

(1) Except as otherwise provided, this Act applies to a data control- ler in respect of data where (a) the data controller is established in this country and the data is processed in this country, (b) the data controller is not established in this country but uses equipment or a data processor carrying on business in this country to process the data, or (c) processing is in respect of information which originates partly or wholly from this country.

Quoted word for word from Data Protection Act, 2012 (Act 843) (Ghana), section 45(1), as fetched on 2026-11-12.

Text of Data Protection Act, 2012 (Act 843) (Ghana), section 46(3)

(3) A data controller shall register with the Commission.

Quoted word for word from Data Protection Act, 2012 (Act 843) (Ghana), section 46(3), as fetched on 2026-11-12.

Text of Data Protection Act, 2012 (Act 843) (Ghana), section 53

A data controller who has not been registered under this Act shall not process personal data.

Quoted word for word from Data Protection Act, 2012 (Act 843) (Ghana), section 53, as fetched on 2026-11-12.

Text of Personal Information Protection Act (Korea; KLRI's English translation), Article 22-2(1)

(1) When the consent of a child under 14 years of age is required to process the personal information of such child, a personal information controller shall obtain the consent of his or her legal representative and confirm whether the legal representative has granted consent.

Quoted word for word from Personal Information Protection Act (Korea; KLRI's English translation), Article 22-2(1), as fetched on 2026-11-12.

Text of Personal Information Protection Act (Korea; KLRI's English translation), Article 28-8(2)

(2) A personal information controller shall inform data subjects of the following matters in advance when obtaining consent under paragraph (1) 1: 1. Particulars of the personal information to be transferred; 2. The country to which the personal information is transferred, transfer date, and method; 3. Name of the recipient of personal information (referring to the name of a corporation and the contact information of the corporation, if the recipient is a corporation); 4. The purpose of using personal information by the recipient of personal information and the period of retention and use of personal information; 5. The method and procedure for refusing the transfer of personal information and the effect of such refusal.

Quoted word for word from Personal Information Protection Act (Korea; KLRI's English translation), Article 28-8(2), as fetched on 2026-11-12.

Text of Federal Law on the Protection of Personal Data Held by Private Parties (Mexico), Article 1

La presente Ley es de orden público y de observancia general en todo el territorio nacional y tiene por objeto la protección de los datos personales en posesión de los particulares

Quoted word for word from Federal Law on the Protection of Personal Data Held by Private Parties (Mexico), Article 1, as fetched on 2026-11-12.

Text of Federal Law on the Protection of Personal Data Held by Private Parties (Mexico), Article 15(I)

El aviso de privacidad deberá contener, al menos, la siguiente información: I. La identidad y domicilio del responsable;

Quoted word for word from Federal Law on the Protection of Personal Data Held by Private Parties (Mexico), Article 15(I), as fetched on 2026-11-12.

Text of Data Privacy Act of 2012 (the Philippines), section 6

This Act applies to an act done or practice engaged in and outside of the Philippines by an entity if: (a) The act, practice or processing relates to personal information about a Philippine citizen or a resident;

Quoted word for word from Data Privacy Act of 2012 (the Philippines), section 6, as fetched on 2026-11-12.

Text of Data Privacy Act of 2012 (the Philippines), section 21(a)

(a) The personal information controller is accountable for complying with the requirements of this Act and shall use contractual or other reasonable means to provide a comparable level of protection while the information are being processed by a third party.

Quoted word for word from Data Privacy Act of 2012 (the Philippines), section 21(a), as fetched on 2026-11-12.

Text of Personal Data Protection Law (Saudi Arabia; SDAIA's English translation), Article 29

2-The conditions that must be met when there is a Transfer or Disclosure of Personal Data, according to what is stated in Paragraph (1) of this Article, are as follows: A. The Transfer or Disclosure shall not cause any prejudice to national security or the vital interests of the Kingdom. B. There is an adequate level of protection for Personal Data outside the Kingdom. Such level of protection shall be at least equivalent to the level of protection guaranteed by the Law and Regulations, according to the results of an assessment conducted by the Competent Authority in coordination with whomever it deems appropriate from the other relevant authorities.

Quoted word for word from Personal Data Protection Law (Saudi Arabia; SDAIA's English translation), Article 29, as fetched on 2026-11-12.

Text of Law No. 18.331 on the Protection of Personal Data (Uruguay), Article 3

El régimen de la presente ley será de aplicación a los datos personales registrados en cualquier soporte que los haga susceptibles de tratamiento, y a toda modalidad de uso posterior de estos datos por los ámbitos público o privado.

Quoted word for word from Law No. 18.331 on the Protection of Personal Data (Uruguay), Article 3, as fetched on 2026-11-12.

Text of Law No. 18.331 on the Protection of Personal Data (Uruguay), Article 13(B)

Cuando se recaben datos personales se deberá informar previamente a sus titulares en forma expresa, precisa e inequívoca: A) La finalidad para la que serán tratados y quiénes pueden ser sus destinatarios o clase de destinatarios. B) La existencia de la base de datos, electrónico o de cualquier otro tipo, de que se trate, la identidad y domicilio de su responsable.

Quoted word for word from Law No. 18.331 on the Protection of Personal Data (Uruguay), Article 13(B), as fetched on 2026-11-12.

Text of Law No. 18.331 on the Protection of Personal Data (Uruguay), Article 29

Toda base de datos pública o privada debe inscribirse en el Registro que al efecto habilite el Organo de Control, de acuerdo a los criterios reglamentarios que se establezcan.

Quoted word for word from Law No. 18.331 on the Protection of Personal Data (Uruguay), Article 29, as fetched on 2026-11-12.

Text of Cyber and Data Protection Act [Chapter 12:07] (Zimbabwe), section 4(2)(a), as ZimLII gives it

(2) Subject to subsection (1) this Act shall be applicable— (a) to the processing of data carried out in the context of the effective and actual activities of any data controller;

Quoted word for word from Cyber and Data Protection Act [Chapter 12:07] (Zimbabwe), section 4(2)(a), as ZimLII gives it, as fetched on 2026-11-12.

Text of Cyber and Data Protection Act [Chapter 12:07] (Zimbabwe), section 28(1), as ZimLII gives it

(1) Subject to the provisions of this Act, a data controller may not transfer personal information about a data subject to a third party who is in a foreign country unless an adequate level of protection is ensured in the country of the recipient or within the recipient international organisation and the data is transferred solely to allow tasks covered by the competence of the controller to be carried out.

Quoted word for word from Cyber and Data Protection Act [Chapter 12:07] (Zimbabwe), section 28(1), as ZimLII gives it, as fetched on 2026-11-12.

Not quoted: the texts that could not be fetched

What can be submitted

Sophaxis accepts work in philosophy, mathematics, logic, the philosophy of mathematics and the philosophy of science. Work that belongs mainly to another field is out of scope, even if it uses mathematics.

The work must already be deposited in Zenodo, Figshare, OSF Preprints, SocArXiv, MetaArXiv, arXiv, Preprints.org, SSRN, Research Square, SciELO Preprints, Qeios, ScienceOpen Preprints, Advance, KC Works or Jxiv, with a DOI. It must carry CC BY 4.0, CC BY-SA 4.0 or CC0 1.0 in its DOI metadata, as set out in the Licence Policy. It must have a title, an abstract and references, in the ordinary form of a scholarly paper.

From 2026-11-23, a new work is listed only if at least six months have passed since its first DOI was registered. The six months are counted to the day the submission issue is opened, in Japan time. They end on the same day of the month, or on the last day of a shorter month. The first DOI is the DOI registered earliest among the DOI given and the DOIs that its metadata names as earlier versions of the work, or as the DOI of all its versions. In Zenodo this is the DOI of all versions, and in Figshare the DOI of the first version. The day of registration is the one that DataCite or Crossref records. Where the metadata gives no such day, as for Jxiv, the operator checks it by hand. The automatic check in the issue reads these days and counts the six months. A submission opened too early is not listed; a new issue can be opened once the six months have passed. This does not apply to a new version of a work that Sophaxis already lists, or to a submission opened before 2026-11-23.

From 2026-11-23, a work for which Crossref records a retraction, a partial retraction, a withdrawal or a removal is not listed. A work for which it records an expression of concern goes to the operator, who decides under the Moderation Policy. Crossref includes the data of the Retraction Watch database. The automatic check in the issue reads these notices for the DOI given. A notice that a repository shows only on its own page, and not to Crossref, is not seen by the check.

Work that a journal has already published may be submitted only in a version that the authors may share under such a licence. Publishers set different terms for this. The submitter gives the DOI of the published version in the form, as set out under "When the work is published" below.

When a work has more than one author

From 2026-11-21, a work with more than one author is listed only after every other author confirms their own agreement. Each confirms in one of two ways. One is a comment in the submission issue, from a GitHub account that their ORCID record links. The comment says "I agree to the listing of this work on Sophaxis." and gives their ORCID iD. The automatic check in the issue counts each confirmation. The other is an email to the operator, after which the operator confirms them through their ORCID record. This consent covers the listing, and the provision of their personal data that the Privacy Policy sets out. An email confirmation says the same, and the operator's reply links the Privacy Policy. Saving the record to the Internet Archive needs a separate consent from every author, which the form asks and which may be left empty; without it the record is not saved there. Any author can withdraw a consent at any time, by a removal issue or by email.

A researcher who vouches for a first submission

From 2026-11-23, a submitter who is not yet an author of a work that Sophaxis lists needs one researcher to vouch for it. That researcher's public ORCID record lists a journal article, a book chapter or a book with a DOI, and links the GitHub account from which they comment. The researcher comments in the submission issue with these words and their own ORCID iD: "I vouch for this submission to Sophaxis. I am not an author of this work, and I do not live in, or stay in, a place where Sophaxis is not offered." The authors of the work and the operator cannot vouch. Like an author, the researcher must not live in, or stay in, a place where Sophaxis is not offered. Vouching says that the work is in scope and in the ordinary form of a scholarly paper. It is not a review, and the moderator still decides. The automatic check in the issue reads the researcher's public ORCID record as it reads a co-author's, and counts the vouching. The researcher can take it back by deleting the comment before the listing. A submitter who is already an author of a listed work needs no one to vouch, and neither does a new version of a listed work.

What the submitter confirms

Every author of the work agrees to its listing on Sophaxis. The authors have the right to share this version under its licence; if a journal has published the work, the publisher allows it. The submitter confirms both, and each point below, by ticking its box in the submission form, which has the same 29 boxes, in the same words and order. The automatic check in the issue refuses a submission unless every box of a group is ticked: the confirmations always, the consent and agreement from 2026-11-21, and where the authors live from 2026-11-22.

Confirmations

Where the authors live

One more box, on saving the record page and the PDF copies to the Internet Archive, may be left empty; the work is listed either way.

How to submit

  1. Deposit the preprint in Zenodo, Figshare, OSF Preprints, SocArXiv, MetaArXiv, arXiv, Preprints.org, SSRN, Research Square, SciELO Preprints, Qeios, ScienceOpen Preprints, Advance, KC Works or Jxiv, under an accepted licence, and obtain its DOI.
  2. Link your ORCID record to your GitHub account: add https://github.com/<your username> under "Websites & social links".
  3. Open a submission issue in the Sophaxis repository and give the DOI, your ORCID iD, the category and the statement on generative models.
  4. An automatic check reads the DOI metadata and your ORCID record, and posts the result in the issue.
  5. A moderator checks the submission under the Moderation Policy. If it passes, a record page is published.

The title, the authors, the abstract, the licence and the versions are taken from the DOI metadata, not typed in by hand.

The submission issue is public. Your GitHub username and everything you write in the form will be visible to anyone.

Language models and other generative models

Work written or developed with language models is accepted, on one condition: the use is disclosed. The same condition applies to every other generative model, including models that produce images, figures, audio or code.

The disclosure must name the tools used and say what they were used for, for example drafting, translation, proofs, code, literature search, editing, figures or images. If no generative model was used, the statement says so.

From 2026-11-21, the form also asks for the extent of use, at one of four levels. The authors choose the highest level that applies:

The record page shows the level the authors chose, above their statement. The level does not replace the statement; the statement still names the tools and what each did. A level of "None" cannot stand beside a statement that names a model.

A language model cannot be listed as an author. No other generative model can be listed as an author either. The authors bear full responsibility for the work, as the Terms of Use set out.

If substantial undisclosed use comes to light after listing, the record receives a notice, and the authors are asked to add a disclosure.

Funding, competing interests, research ethics, and data

From 2026-11-24, the form asks three statements, and a work is listed only if each is given. The automatic check in the issue confirms that each field is filled in; it does not judge what it says.

Work that involves human participants must name the ethics committee that approved it, or say why no approval was needed under the rules that applied where the research was done. Every participant who can be identified must have consented, and the statement says so. Work that contains personal data of third parties is not accepted, as set out above.

The form also asks, as an option, where the data, code and other materials on which the work rests can be found, such as a repository with a DOI, or that there are none. Sophaxis encourages authors to make them available, but does not require it and does not check them.

The record page shows each statement as the authors give it. Sophaxis does not check the statements beyond reading them. A statement found to be untrue is handled under "Research integrity" in the Moderation Policy. This does not apply to a submission opened before 2026-11-24.

Versions and updates

A work is listed once, under one Sophaxis id. That id is never given to another work, even after a record is withdrawn or removed.

A new version is a new version in the repository. Most repositories give each version its own DOI. arXiv keeps one DOI for all versions, and that DOI leads to the latest one; the record then lists the same DOI with the date of each version. Submit it as an update to the existing record; earlier versions stay listed.

When the work is published

A listed preprint stays listed when a later version is published in a journal, in proceedings or in a book. The record page then shows the published version at the top: what it is, where and when it appeared, and its DOI. It asks readers to cite the published version, and it names the listed version as the preprint.

Any one author reports the published version with the published-version form, from the GitHub account that the author's ORCID record links. An automatic check confirms that the report comes from an author, and reads the metadata of the published DOI. The published version must be a journal article, a conference paper, a book chapter or a book. It must not be in one of the accepted repositories, and it must share an author with the record. A moderator then records it, and the decision is public in the issue. A published version can also be given at submission, and the same checks run on it.

Sophaxis does not judge the peer review of a journal. The record repeats what the authors state: that the published version was peer-reviewed, that it was not, or nothing. It also says whether the publisher's metadata links the published version to the preprint, or whether only an author reported it.

Each week Sophaxis looks in the metadata of Crossref and DataCite for a published version that is linked to a listed preprint and shares an author with it. It records nothing by itself: it asks the authors to report it. The same weekly check confirms that a recorded published version still resolves. When the publisher adds a retraction, a correction or another notice to the published version, the record page shows it.

Some publishers ask authors to remove or change a preprint on publication. The authors check the publisher's terms. If the listing must go, any one author can withdraw it under the Withdrawal Policy, and the record page keeps the link to the published version.

Examples of what is not accepted

These examples show how the rules above apply. They are not a complete list; the rules decide. Each group matches a reason that a moderator names when declining, under the Moderation Policy.

Authorship: the submitter must be an author, and every author must agree.

Repository and DOI: the work must have its own DOI from an accepted repository.

Licence: the DOI metadata must carry CC BY 4.0, CC BY-SA 4.0 or CC0 1.0.

Scope: the work must belong mainly to philosophy, mathematics, logic, the philosophy of mathematics or the philosophy of science.

Form: the work must have a title, an abstract and references, in the ordinary form of a scholarly paper.

Disclosure: the statement on generative models must name the tools and say what they were used for.

Rights or personal data: the authors must be free to share everything in the work, and it must not expose others.

Spam or abuse.

Versions.

Withdrawal

Any one author can withdraw a listed work under the Withdrawal Policy. Records are not deleted: a withdrawn work keeps its record page with a withdrawal notice, so that citations to it do not break. An author can instead have the record removed, so that only its Sophaxis id stays. Removal for legal reasons follows the Takedown Policy.

All policies