Review Article WorkbenchReview Article Workbench

Privacy Policy

The Review Article Workbench operations team (the “Operator”) publishes this policy to protect users’ personal information and respond promptly to privacy concerns under applicable Korean privacy law.

Effective date: September 7, 2026
Document version: privacy-notice/3
Service model: Independently operated, free public registration
Privacy contact: [email protected]

1. Data processed, purposes, and retention

Data	Purpose	Retention
Google unique identifier (`sub`), display name, and verified email	Registration, sign-in, account linking and email verification	Until account deletion
Username, display name and Argon2id password hash	Administrator issuance, sign-in, password resets, suspension and recovery	Until account deletion; issued passwords are shown once and never stored or logged as plaintext
Display name, affiliation, role, and project permissions	Account and collaboration access management	Until account deletion or removal from the project
Manuscripts, uploads, literature queries, evidence-use notes, comments, AI requests and results, and change/audit records	Review-article authoring, review, collaboration, recovery, and security auditing	Until project deletion or completion of a deletion request; limited collaboration history may be separated or anonymized to protect other participants
Access time, IP address, user agent, and session/security events	Session continuity, misuse prevention, reliability, and security response	Session data until cookie expiry; security records until account or project deletion

Minimum required data is processed to perform the service contract and maintain security. AI processing occurs when a user runs the feature and only to provide the requested result. Turning off full-text AI use in settings stops new full-text processing while abstract-based features remain available.

2. Google user data

Requested scopes are limited to openid, profile, and email.
The unique identifier verifies repeat sign-in; the display name is shown in the service.
The verified email confirms a new account and supports account security. It is not used for marketing or automatic account merging.
OAuth access, refresh, and ID tokens are not retained after the sign-in callback.
Google user data is not used for advertising, sale, credit evaluation, or email-based automatic account merging.

The Review Article Workbench’s use of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements.

review_paper_session: Secure, HttpOnly, SameSite=Lax sign-in cookie retained for up to eight hours.
rpw_oauth_browser: Secure, HttpOnly, SameSite=Lax anti-forgery cookie retained for up to ten minutes.
rpw_locale: remembers the language selection for up to one year.
Temporary in-progress interface state may use tab session storage and is removed when the tab closes.

Blocking required cookies disables sign-in and the private workbench. No advertising or behavioral-tracking cookies are used.

The Operator does not sell personal information. The following services may process limited data when needed:

Where the overseas processing below is necessary to enter into or perform the service contract, it relies on Article 28-8(1)(3) of Korea's Personal Information Protection Act. A user can stop new full-text transfers by not running the feature or by turning off the full-text AI preference.

Recipient/processor	Purpose and data	Timing and retention
Google LLC (United States and Google global infrastructure)	Google sign-in and security verification: OAuth request and account authentication data	Processed over encrypted connections at sign-in and retained under Google account/security policies
Cloudflare, Inc. (global network)	DNS, TLS transport, and service security: IP address, request headers, and access time	Processed over encrypted connections and retained as required by security settings and law
OpenAI, OpCo, LLC and API subprocessors (Cloudflare, Microsoft, CoreWeave, Oracle Cloud, Google Cloud, AWS, Cerebras, Snowflake, TaskUs, Intercom, Salesforce, Pylon Labs, Accenture, Confluent, Cinder Technologies, and Okta; the United States, South Korea, Japan, Singapore, Australia, Brazil, Canada, France, Germany, India, Indonesia, Ireland, Italy, Malaysia, Mexico, the Netherlands, Norway, the Philippines, Poland, South Africa, Spain, Sweden, Switzerland, the United Arab Emirates, the United Kingdom, and other locations in the official list)	User-requested AI analysis and explanations: the question, selected full-text excerpts, and necessary bibliographic information. The full library and institutional credentials are not sent.	Encrypted transfer when the user runs an AI feature; Responses API requests use `store: false`. API data is not used for model training unless the user explicitly opts in. Default abuse-monitoring logs may be retained for up to 30 days.

Full-text use by AI can be turned off at any time in account settings. No new full-text excerpt is transferred after it is turned off, although abuse-monitoring records from earlier requests may remain for the retention period above. See OpenAI's API data guide and official subprocessor list. The current disclosure version is openai-subprocessors/2026-07-09 (official list updated 2026-07-09). The Operator updates this policy and the version when that list changes.

Cross-account invitations and sharing are disabled. Everyone using a shared account can access all its projects, PDFs and AI results. History identifies the account and browser session, not the individual person. Administrators receive identifiers, status and error codes; other accounts’ manuscripts, full text and AI conversations are excluded from operational views.

No paid checkout is currently offered, so payment information is not collected or sent to a payment processor.

5. Separation of the administrator quality corpus

User-uploaded or Zotero-imported manuscripts and articles are not used for the review-quality corpus, model training, benchmarks, or evaluation rubrics. The administrator corpus is maintained in a separate private store with separate access.

Authorized platform administrators register corpus documents separately after responsibility checks. Runtime use is limited to structured authoring/evaluation profiles designed not to reveal source titles, DOI values, journals, summaries, or unique results.

6. Your rights

You may request access, correction, deletion, suspension of processing, or consent withdrawal. Send the request and a Google account or administrator-issued username that can verify your identity to the privacy contact. A legal representative may apply with evidence of authority.

Turn off “Use my full text in AI features” to withdraw future full-text processing immediately. Requests to delete a source file, project, or account may be made in the service or through the privacy contact.

Account deletion removes account identifiers and private work. Collaboration history needed to preserve a shared manuscript or protect other participants may be separated or anonymized. Legally required records are isolated and deleted after the required period.

7. Deletion

Personal information is destroyed without undue delay when its purpose or retention period ends. Electronic files use secure deletion; any paper record is shredded or incinerated. Legally retained information is kept separately.

8. Security

Reasonable safeguards include least-privilege access, encrypted transport, separate secret management, HttpOnly session cookies, one-time OAuth state with PKCE, security audit records, and vulnerability/dependency reviews.

9. Children under 14

The service is not directed to children under 14. If a user is identified as under that age, new use is restricted and collected information is deleted without undue delay.

10. Privacy contact and remedies

Send privacy questions, rights requests, or complaints to [email protected]. The Review Article Workbench Operator is the privacy contact and will respond as promptly as practical.

For additional assistance, you may contact Korea’s privacy portal, Personal Information Dispute Mediation Committee, or another competent authority.

11. Changes to this policy

Changes and their effective date will be posted here in advance. Material changes affecting user rights will also be announced in the service with reasonable notice.

Published and effective: September 7, 2026