Humanitext ID

This is a translation for reference. The Japanese version is authoritative.

Humanitext Common Privacy Policy

This Policy sets out how user information is handled in "Humanitext ID," the common account provided by the Humanitext Project, and in each of the following services (collectively, the "Services").

ServiceURL
Humanitext ID (common account)https://id.humanitext.ai
Humanitext Antiquahttps://antiqua.humanitext.ai
Humanitext Aozorahttps://aozora.humanitext.ai
Humanitext OCRhttps://ocr.humanitext.ai
Humanitext Readerhttps://reader.humanitext.ai
Humanitext GEOhttps://geo.humanitext.ai

Handling specific to each Service (the information that Service handles, its contractors, retention periods, etc.) is set out in the "Service Rules" for that Service. Where this Policy and the Service Rules differ, the Service Rules prevail with respect to that Service.

Article 1. Operator and Contact Point

  1. Operator: the Humanitext Project
  2. Responsible person for operations (person responsible for the handling of personal information): Naoya Iwata (affiliated with the Center for Digital Humanities and Social Sciences, Nagoya University)
  3. Address (for correspondence): Nagoya University, Furo-cho, Chikusa-ku, Nagoya, Aichi 464-8601, Japan
  4. Contact point: the inquiry form (https://forms.gle/1NTz78iubG9bwrgQA) or email (contact@humanitext.ai). Requests under Article 8 may also be made through either channel.
  5. The Humanitext Project does not have legal personality. The business operator handling personal information under the Act on the Protection of Personal Information, and the counterparty to the contract for use of each Service, is the responsible person for operations. If paid plans are offered, fees will be received by Nagoya University. Paid plans are currently in preparation. The counterparty to contracts for paid plans and the handling of payment-related information will be determined before such plans become available, and we will notify you by revising this Policy.
  6. The project members (Ikko Tanaka [J. F. Oberlin University] and Jun Ogawa [The University of Tokyo]) have administrative privileges for the Services and handle user information under the direction of the responsible person for operations, to the extent necessary for operations.

Article 2. Information Handled for the Common Account

The common account "Humanitext ID" is used to log in to the Services. You can log in with a Google account, or with an email address and password. Humanitext ID handles the following information.

  1. Account identifier (UID). If you have been using the Services since before September 2026, you retain the identifier issued under the previous login method (Google Firebase Authentication).
  2. Email address and its verification status
  3. Display name: not stored. The name received from Google when you log in with a Google account is discarded without being stored. Names that had been received and stored up to October 7, 2026 were erased on that date.
  4. Login method: the Google account identifier, or a hash value (scrypt) computed from your password. The password itself is not stored.
  5. Records of login status (sessions): a hash value of the value stored in your browser's cookie, the dates and times of creation and last use, and the method used to log in (Google account or password). Sessions expire 30 days after login.
  6. Temporary values for email address verification and password reset (hash values; expiring after 24 hours or 30 minutes, respectively), and temporary values used to hand over a login to Reader (hash values; expiring after 60 seconds)
  7. For rate limiting, a value computed from the IP address from which you connect (which cannot be converted back into the original IP address; deleted within 1 day at most), and a value computed from your email address (to count login attempts and emails sent; deleted within 2 days at most)
  8. The results of bot protection checks (Cloudflare Turnstile). For these checks, Turnstile processes the IP address from which you connect, your browser type, and similar information. Cloudflare's Turnstile Privacy Addendum also applies to this processing.
  9. Which Services you use (the correspondence with your user ID in each Service, recorded when you first log in to that Service)
  10. If a suspension of use has been imposed, the identifier of the login method (such as the Google account identifier) to prevent re-registration
  11. When an account is deleted, records used to deliver the deletion to each Service (whether it has been delivered)

As a rule, only the account identifier, whether the email address has been verified, and the method used to log in (Google account or password; administrative privileges are granted only when logged in with a Google account) are passed to the servers of each Service. Services that require a verified email address, such as for inviting proofreaders (as stated in the relevant Service Rules), also receive the verified email address. In addition, to show on each Service's screens that you are logged in, your email address is passed to your browser (it is not sent to the servers of each Service).

Article 3. Information Handled by Each Service

Each Service handles the information necessary to provide that Service (questions and answers, uploaded materials, posts, etc.). Because the items and the manner of handling differ substantially from Service to Service, they are set out in the Service Rules.

Article 4. Purposes of Use

The purposes of use common to all Services are as follows. Purposes specific to a Service are set out in its Service Rules.

  1. Providing the Services (including login, account management, and management of usage allowances)
  2. Preventing misuse, ensuring secure operation, and responding to failures
  3. Understanding usage and improving the Services. This is done in the form of aggregate data that cannot identify individuals, and such aggregate data is also used in reports on usage (research use with consent is governed by item 5).
  4. Communicating important notices (changes to terms, failures, procedures concerning your account, etc.)
  5. Research use with the consent of users (limited to the scope set out in the Service Rules of the relevant Service)

Article 5. Provision to Third Parties

We will not provide personal information to third parties without the consent of the person concerned, except where required by laws and regulations, where necessary for the protection of the life, body, or property of a person and it is difficult to obtain the consent of the person concerned, or where otherwise permitted by laws and regulations. Entrustment under Article 6, and cases where users themselves instruct sharing (such as inviting proofreaders), do not constitute provision to third parties.

Article 6. Contractors and Handling in Foreign Countries

  1. To provide the Services, we entrust handling to the following businesses. All entrustment is based on the operator's instructions, and none of these companies is permitted to use users' information for its own purposes (except as separately stated in the Service Rules of each Service).
BusinessRoleInformation handledMain processing regions
CloudflareDelivery and relaying of the Services (Antiqua, Aozora, OCR, Reader, GEO); operation of and data storage for Humanitext ID; sending verification and reset emails; bot protection (Turnstile); access analytics (Web Analytics, including the estimation of country used to determine whether consent is required for Google Analytics [Article 10, paragraph 2])Each request (including the IP address from which you connect); the information in Article 2United States and elsewhere (locations close to the user). The Humanitext ID database is in the Asia-Pacific region
GoogleData storage (Cloud Firestore, Cloud Storage); infrastructure for running OCR (Cloud Run); AI-based generation, translation, and OCR (Vertex AI); access analytics (Google Analytics; Article 10, paragraph 2); the previous login method (Firebase Authentication; records of accounts prior to migration, to be deleted for all users once migration is complete); the inquiry formThe information set out in the Service Rules of each Service; browsing information (Article 10, paragraph 2)United States, Japan
  1. Contractors specific to a Service (OpenAI, Pinecone, etc.) are set out in the Service Rules.
  2. Content sent to Google's Vertex AI is not used to train AI. However, only where suspected misuse is detected, Google may log such content for up to 90 days, and may temporarily hold it in memory for up to 24 hours to speed up responses.
  3. The United States does not have a personal information protection system recognized as being at a level equivalent to that of Japan. We entrust handling to each business after confirming that measures equivalent to those required under Japan's Act on the Protection of Personal Information are in place through terms of use and data processing terms (including standard data protection clauses), and we periodically check the status of those measures. For information on the systems of the destination countries and on these measures, please make a request to the contact point in Article 1.

Article 7. Retention Periods

InformationRetention period
Account information (Article 2, items 1–4 and 9)Until the account is deleted. After deletion, only the account identifier, the date and time of deletion, and the Services used are retained (to prevent the deleted account from being restored and to keep aggregate user counts unchanged)
Usage records of deleted accounts (as set out in the Service Rules of each Service)Until the end of the retention period in the Service Rules of each Service (indefinitely where none is set). Retained in a form no longer linked to the account (Article 8, paragraph 3)
Monthly usage aggregates (number of users, number of uses, etc.; containing no personal information)Indefinitely
Records of suspension of use (Article 2, item 10)Until the suspension is lifted
Records of login statusUp to 30 days (deleted immediately upon logout)
Temporary values for verification, reset, and login handover24 hours, 30 minutes, and 60 seconds
Values computed from IP addressesUp to 1 day
Values computed from email addresses (rate limiting)Up to 2 days
Records used to deliver deletions (Article 2, item 11)30 days after delivery
Copies for restoration (backups)Through the databases' restore functions, the state prior to changes or deletions is retained for a certain period (up to 30 days for the Humanitext ID and Reader databases, and up to 14 days for Firestore). These are used solely to recover from failures or operational errors, and once the period has passed, deleted information can no longer be restored
Operational logs on the businesses' sideAccording to each business's standards

Retention periods specific to a Service are set out in its Service Rules.

Article 8. Users' Rights

  1. You may request notification of the purposes of use of retained personal data, disclosure (including disclosure by electromagnetic record), correction, addition, or deletion, cessation of use or erasure, and cessation of provision to third parties (Articles 32 to 35 of the Act on the Protection of Personal Information).
  2. Requests are accepted at the contact point in Article 1. After verifying your identity, we will, as a rule, respond within one month. No fee is charged. Requests through an agent are also accepted (documents demonstrating the authority of representation are required).
  3. You may delete your Humanitext ID account yourself at any time from the account screen (https://id.humanitext.ai). Deletion upon request to the contact point in Article 1 is also accepted. On the deletion screen, you will be asked to enter a confirmation word and your current password (for accounts without a password, a recent login [within the past 15 minutes]). Once deleted, you will no longer be able to log in to any of the Services, and each Service will handle your data as follows. Deletion normally reaches each Service within a few minutes; if it does not, it is retried automatically. Deletion cannot be undone.
    • Erased: personal information such as your email address and display name, and content you entered or uploaded yourself (questions, materials, file names, etc.; see the Service Rules of each Service for details)
    • Retained in a form not linked to any individual: usage records (dates of use, number of uses, number of pages, etc.). The account identifier is replaced with a separate, meaningless value for each user, and no link to Humanitext ID is retained. This is so that aggregate figures such as the number of users do not change as a result of deletion.
    • Posts on Reader are anonymized in accordance with the Reader Service Rules, with their text retained.
    • Records that must be retained by law (such as records of paid plan transactions) are retained for the period prescribed by law.
    • Information remaining in the copies for restoration (Article 7) also disappears once that period has passed.

    If you register again with the same Google account or email address, it will be treated as a new account, and your previous data will not be carried over.

  4. Where handling is based on consent, you may withdraw your consent at any time. Withdrawal does not affect the lawfulness of handling before the withdrawal.
  5. Please direct complaints about handling to the contact point in Article 1. You may also lodge a complaint with the Personal Information Protection Commission or, if you are outside Japan, with the supervisory authority of the country or region where you reside.

Article 9. Security Control Measures

  1. All communications are encrypted using TLS.
  2. Stored data is encrypted using each business's standard functions.
  3. Passwords are stored only in a non-recoverable form (hash values computed with scrypt). For values indicating login status, too, only hash values are stored.
  4. Access to data is limited to the user concerned and to operators and members to the extent necessary. Server permissions are kept to the minimum for each purpose.
  5. Information whose retention period has passed is deleted automatically.
  6. With respect to handling in foreign countries, as stated in Article 6, we take measures after understanding the systems of the destination countries.
  7. In the event of a leak or similar incident, we will report it to the Personal Information Protection Commission and notify the persons concerned in accordance with laws and regulations.

Article 10. Cookies and Storage in the Browser

  1. Cookies are used to keep you logged in. The Humanitext ID login cookie is sent only to id.humanitext.ai and is not sent to other sites on humanitext.ai (each Service checks your login status by querying id.humanitext.ai). Each Service also uses cookies and storage areas in the browser (local storage) for its own login status and for settings such as the display language.
  2. For access analytics, we use Cloudflare Web Analytics and Google Analytics.
    • Cloudflare Web Analytics does not use cookies and performs only aggregation that does not identify individuals.
    • Google Analytics uses cookies. Google processes the pages viewed (the part of the URL after "?" is not sent), the referring page, the page title, the type of device and browser, the approximate region (estimated by Google from the IP address; the IP address itself is not stored), and a per-browser identifier. Account identifiers, email addresses, and content you enter (questions, materials, search terms, etc.) are not sent. It is not used on administrator screens. On pages containing values that differ for each user (such as OCR job screens), that part of the URL is masked before sending. The data retention period is 14 months.
    • For users accessing from the European Economic Area, the United Kingdom, or Switzerland, we ask for consent before use, and Google Analytics is not loaded unless consent is given. Where you are accessing from is determined from the country information estimated by Cloudflare from the IP address (which is not stored), or, where this cannot be determined, from the time zone setting of your device.
    • If you wish to stop this, please enable Global Privacy Control (GPC) in your browser or use the Google Analytics Opt-out Browser Add-on (https://tools.google.com/dlpage/gaoptout). Handling by Google is governed by Google's privacy policy.
  3. We do not use trackers or cookies for advertising (Google Analytics advertising features are disabled).

Article 11. Minors

If you are under 16 years of age, please use the Services with the consent of a parent or legal guardian. We do not collect dates of birth.

Article 12. Revisions to This Policy

  1. When this Policy or the Service Rules are revised, we will announce the revised content and its effective date on each Service.
  2. For changes that significantly affect users (adding new contractors, expanding the scope of information handled, extending retention periods, etc.), we will ask for your consent again.

Article 13. Language

The Japanese version of this Policy is the authoritative text. Versions in other languages are translations provided for reference.

Established: October 6, 2026 (version 2026-10-06)

Revised: October 7, 2026 (Article 2, item 3: display names are no longer stored; Article 2, item 5 and the paragraph after the list: the method used to log in is recorded and passed to each Service)

日本語 English 简体中文 한국어
Terms of UsePrivacy Policy