Privacy Policy

Last Updated: November 7, 2026

This is a translation for convenience. The Japanese version is the official version and legally binding.

1. Introduction

Professional Reader (hereinafter "the Service") is a web application and a Chrome browser extension operated by the Professional Reader Development Team (hereinafter "we," "us" or "our"), located in Naha-shi, Okinawa, Japan. We are committed to protecting your privacy and ensuring the security of your personal information.

This Privacy Policy explains how we collect, use, disclose, and protect your information when you use the Service. By using Professional Reader, you agree to the collection and use of information in accordance with this policy.

Key Privacy Principle

Your document contents are never stored on our servers. In the web application, PDF files are stored locally in your browser's IndexedDB storage, and only metadata such as filename, file size, and page count is stored on our servers. In the Chrome Extension, PDFs are rendered directly from their source URL, and no metadata is stored on our servers.

2. Information We Collect

2.1 Information You Provide Directly

  • Account Information: Email address, password (hashed and encrypted)
  • Subscription Information: Subscription status (Free or Standard plan), payment history
  • Billing Information: Credit card information (processed and stored by Stripe; not by us). We currently do not collect billing addresses, but may collect them in the future for tax compliance purposes (such as EU VAT compliance).
  • Security Verification Codes (OTP): Hashed one-time passwords used for email verification, two-factor authentication, and password reset (automatically expire after 10 minutes)

2.2 PDF Metadata (NOT File Contents)

When you upload a PDF in the web application, we collect and store the following metadata only:

  • Filename
  • SHA-256 file hash (for duplicate detection)
  • File size (bytes)
  • Page count
  • Upload date and time
  • Last opened date and time

IMPORTANT: The actual PDF file content is stored locally in your browser's IndexedDB. We never store, retain, or access your PDF file contents on our servers.

2.3 Translation, Explanation, and Detail Q&A Data

When you select text in a PDF or on a web page (via the Chrome Extension) for translation or explanation, or when you use the Detail Q&A follow-up chat:

  • Selected text (up to about 1,000 tokens)
  • Context: The sentence(s) containing the selected text. If the selected sentence is short (below a configurable token threshold, default: 30 tokens), surrounding sentences are automatically included to provide better context. You can adjust the context threshold in the reader settings.
  • Your language preference
  • Detail Q&A Conversations: When you use the Detail Q&A feature, your typed messages, the selected text, the prior meaning explanation, and the surrounding context are sent to OpenAI as a multi-turn conversation. Detail Q&A requires a signed-in account.
  • Web Search: When web search is enabled, OpenAI may run web searches based on the selected text, its context or the question entered in Detail Q&A. Answers may include links to the web pages found. Web search requires a signed-in account.

This data is sent to OpenAI API for processing and is not permanently stored by us.

2.4 Automatically Collected Information

  • Usage Data: Pages visited, features used, session duration, token usage
  • Device Information: Browser type and version, operating system, screen resolution
  • Log Data: IP address, access times, referring URLs
  • Cookies: Authentication cookies (Supabase Auth), analytics cookies (Google Analytics, Vercel Analytics)
  • Anonymous Usage Data: If you use the Service without an account, we track your API request count and token usage on our servers using a device identifier. In the web application, the identifier is stored in a cookie, and when you create an account, this data may be linked to your account. In the Chrome Extension, the identifier is generated on your device and sent with each API request. Use without an account (in the web application and the Chrome Extension) is limited to 5 requests per 24 hours per network address: our servers count these requests under a keyed one-way hash of your IP address, never the address itself.
  • Keep-alive Requests: Periodic requests sent to our servers during use to maintain service responsiveness

2.5 Chrome Extension Specific Data Collection

When you use the Professional Reader Chrome Extension:

  • Local Storage: Device identifier, language preference, extension on/off toggle, and reader preferences (text highlighting, context threshold, default tooltip tab). Authentication tokens are not stored.
  • Cookie Access: Cookies from professional-reader.app for single sign-on authentication. The extension reads your sign-in session from these cookies and asks professional-reader.app to renew it shortly before it expires. All other requests to our servers are sent without cookies.
  • Browser Permissions: activeTab (current tab access), storage (preferences), cookies (authentication), webNavigation (PDF detection), alarms (periodic tasks), downloads (PDF download from the custom viewer)
  • Host Permissions: Limited to professional-reader.app (used only for SSO authentication). The content script is loaded via a separate matches declaration and the extension does not have network access to host pages.
  • Content Script: Injected into all websites visited (except professional-reader.app) to enable text selection detection; only activates on text selection and does not read or transmit page content otherwise
  • Local PDF Access (Optional): If you manually enable "Allow access to file URLs" on chrome://extensions, the extension can render local PDFs (file://) in its built-in viewer. The file contents remain on your device and are never uploaded.

3. How We Use Your Information

We use the collected information for the following purposes:

Service Provision

  • Account creation and management
  • Providing translation and word explanation features
  • Subscription management
  • Storing your language preferences

Payment Processing

  • Billing for subscription fees
  • Issuing receipts
  • Fraud prevention

Service Improvement

  • Analyzing usage patterns
  • Optimizing features
  • Identifying and fixing bugs
  • Developing new features

Communication

  • Important service announcements
  • Security alerts
  • Subscription renewal notifications
  • Customer support

Legal Compliance

  • Retaining information as required by the Act on Specified Commercial Transactions
  • Tax reporting
  • Responding to legal requests

4. Data Security

We implement the following security measures to protect your personal information from unauthorized access, alteration, disclosure, or destruction:

Technical Measures

  • HTTPS/TLS encryption (all communications)
  • Password hashing (managed by Supabase Auth)
  • Database encryption (at rest)
  • Regular security updates

Access Control

  • Principle of least privilege (minimum necessary access rights)
  • Multi-factor authentication (user and administrator accounts)
  • Access log monitoring

Privacy by Design

  • Local processing of PDF file contents (no server transmission)
  • Server storage of metadata only
  • Periodic security reviews

However, no method of transmission over the Internet or electronic storage is 100% secure. While we strive to protect your personal information using commercially reasonable means, we cannot guarantee absolute security.

5. Cookies and Tracking Technologies

We use cookies and similar tracking technologies for the following purposes:

Essential Cookies

Purpose: Authentication, session management

Provider: Supabase Auth

Can Disable: No

Required for basic Service functionality

Functional Cookies

Purpose: Storing language preferences and UI preferences

Provider: Local Storage / Chrome Storage

Can Disable: No

Remembers your settings

Device Identification Cookie

Purpose: Anonymous usage tracking, linking anonymous activity to account upon registration

Provider: Professional Reader

Can Disable: No

A randomly generated UUID stored as an HttpOnly cookie (pr_device_id) with 30-day expiration. Used to track usage for anonymous users and to link anonymous activity to your account when you register.

Analytics (First-Party)

Purpose: Application performance monitoring, page view tracking

Provider: Vercel Analytics

Can Disable: No

First-party, privacy-friendly analytics that do not use cookies for tracking. Collects page views and performance metrics.

Analytics Cookies (Optional)

Purpose: Usage analysis, service improvement

Provider: Google Analytics

Can Disable: Yes

You can disable these cookies in your browser settings

Cookie Management

Most browsers are set to accept cookies by default, but you can change your browser settings to refuse cookies or notify you when cookies are sent.

However, disabling cookies may prevent some features of the Service from functioning properly (such as maintaining login status).

6. Information Sharing and Disclosure

We do not share your personal information with third parties except in the following cases:

6.1 Service Providers

To support the operation of the Service, we use the following third-party services:

Supabase (USA)

Purpose: Authentication, database, file metadata storage

Data Shared: Email address, password hash, PDF metadata, token usage, subscription information, language preference, two-factor authentication settings

Stripe (USA)

Purpose: Payment processing, subscription management

Data Shared: Billing information, credit card information (processed directly by Stripe)

OpenAI (USA)

Purpose: AI translation and explanation generation, web search (when enabled)

Data Shared: Selected text, context, Detail Q&A messages

OpenAI's data usage policy: Data sent via API is not used for model training

Vercel (USA)

Purpose: Hosting, CDN, application analytics

Data Shared: Access logs (IP address, request information), page views, performance metrics

Resend (USA)

Purpose: Transactional email delivery (verification, password reset, security alerts)

Data Shared: Email address, email content (OTP codes, verification links)

Used solely for sending transactional emails. Resend does not use your data for marketing purposes.

Google Analytics (USA - Optional)

Purpose: Usage analysis

Data Shared: Anonymized usage data

These providers are contractually obligated to protect personal information and are not permitted to use your data for purposes other than providing the Service.

6.2 Legal Requests

We may disclose your information in the following cases:

  • To comply with laws, regulations, legal proceedings, or governmental requests
  • To enforce our Terms of Service
  • To protect our rights, property, or safety, or those of you or third parties

6.3 Business Transfer

In the event of a business transfer such as a merger, acquisition, or asset sale, your personal information may become part of the transferred assets. In such cases, we will notify you in advance and provide you with choices before a new privacy policy takes effect.

7. Data Storage and International Transfers

Data Storage Location

Your personal information is primarily stored on servers in the United States (Supabase, Stripe, Vercel).

In the web application, PDF file contents are stored only on your device (browser's IndexedDB) and are never transferred to our servers or third-party servers.

International Data Transfers

By storing data on servers outside Japan (primarily in the United States), your personal information is transferred internationally. These countries may not have data protection laws equivalent to Japan's, but all service providers we use implement industry-standard security measures.

8. Third-Party Service Privacy Policies

The Service uses the following third-party services. These services have their own privacy policies that detail how they handle your data:

We are not responsible for the privacy practices of these third-party services. We recommend reviewing their privacy policies.

9. Data Retention Period

We retain your personal information for as long as necessary to fulfill the purposes stated in this Privacy Policy or as required to comply with legal obligations.

Data TypeRetention Period
Account InformationDeleted immediately after account deletion (login sessions are invalidated), except for email address hash and subscription history boolean (see Section 10).
PDF MetadataDeleted immediately after account deletion.
PDF File ContentsStored in your browser. We do not retain this information.
Billing InformationRetained for 7 years from the last transaction for tax reporting (based on Japanese tax law).
Usage LogsRetention period is reviewed periodically.
Anonymous Usage DataRetained indefinitely on our servers. In the web application, it is linked to your account upon registration, and the device identifier expires after 30 days (a new identifier is generated on subsequent visits). In the Chrome Extension, the device identifier is kept until the extension is removed. The hashed network address used for the request limit is removed by a periodic cleanup after its 24-hour counting window ends.
OTP CodesExpire after 10 minutes. Marked as used after verification.
API Performance LogsRetained indefinitely for monitoring purposes.
Device Identification Cookie30-day expiration. Refreshed on each visit.

Account Deletion

You can delete your account at any time from your account settings. Upon deletion, your personal information (except billing information, email address hash, and subscription history boolean) will be permanently removed from our systems. See Section 10 for details.

10. Fraud Prevention Measures

To prevent abuse, we implement the following measures:

Data Retained

When you delete your account, the following information is retained:

  • SHA-256 hash of your email address
  • Salt for hash generation (32 bytes)
  • Whether you had a subscription (boolean value)
  • Deletion timestamp
  • Internal record of which user initiated the deletion (user ID)

The information above, retained to prevent abuse, does not include billing information, payment history, contract details, etc. (the retention period for billing information is set out in Section 9).

10.1 Email Address Hash

Technical Implementation

  • Algorithm: Uses SHA-256 with a unique random salt (32 bytes) per email
  • Storage: Stored in an isolated database table separate from user profiles
  • Data Stored: Only stores hash, salt, and deletion timestamp - contains no identifiable information

Privacy Protection

  • The original email address cannot be restored from the hash (irreversible one-way function)
  • The hash is not linked to any other personal information
  • The hash is stored in a separate database table with no connection to user profiles
  • Each hash uses a unique random salt to prevent rainbow table attacks
  • This measure complies with GDPR and CCPA requirements

Legal Basis

  • GDPR: Legitimate interest in fraud prevention (GDPR Article 6(1)(f))
  • CCPA: Business purpose - Prevention of fraud and abuse
  • Proportionality: This measure is necessary and appropriate to prevent service abuse. The hash cannot identify individuals, so the privacy impact is minimal.

Not Personal Data

Since the hash cannot be used to identify you and cannot identify you even when combined with other information, it does not constitute 'personal data' under GDPR Article 4(1) after account deletion. Therefore, GDPR rights (such as the right to erasure) do not apply to this hash.

10.2 Subscription History

Technical Implementation

  • Data Stored: Only subscription status (boolean) - does not store amounts, periods, payment information, or other details
  • Storage: Stored in the same isolated database table as email address hashes, with no connection to user profiles

Privacy Protection

  • Subscription history information is protected by standard database security measures along with email address hashes
  • The retained information is only a boolean value indicating 'whether you had a subscription,' and contains no detailed information that could identify individuals
  • Billing information and payment history are retained only for specified periods (see Section 9)

If you have concerns about these measures, please contact us at contact@professional-reader.app.

11. Your Rights

You have the following rights regarding your personal information:

Right of Access

The right to access and obtain a copy of your personal information held by us

Right to Rectification

The right to request correction of inaccurate or incomplete personal information

Right to Erasure

The right to request deletion of your personal information (under certain conditions)

When you delete your account, your personal information is permanently removed from our systems. However, billing information is retained for 7 years from the last transaction for tax reporting. To prevent abuse, we also retain the email address hash and the salt used to generate it, whether you had a subscription, the deletion timestamp, and an internal record of which user initiated the deletion (user ID). See Sections 9 and 10 for details.

Right to Restriction of Processing

The right to request restriction of processing of your personal information

Right to Data Portability

The right to receive your personal information in a structured, commonly used, and machine-readable format

Right to Object

The right to object to our processing of your personal information

Right to Withdraw Consent

The right to withdraw consent at any time for processing based on your consent (without affecting the lawfulness of processing before withdrawal)

How to Exercise Your Rights

To exercise these rights, please contact us at contact@professional-reader.app. We may request additional information to verify your identity.

We will typically respond within 30 days of your request.

12. Children's Privacy

The Service is not intended for individuals under 16 years of age. We do not intentionally collect personal information from anyone under 16. However, individuals under 16 may use the Service with parental consent. Parental consent is required for subscription registration. If we become aware that personal information has been provided by someone under 16 without parental consent, we will take steps to promptly delete that information. If you believe that someone under 16 has provided personal information to us, please contact us at contact@professional-reader.app.

13. Changes to This Policy

We may update this Privacy Policy from time to time. When changes are made, we will post the new Privacy Policy on this page and update the "Last Updated" date.

For significant changes, we will provide advance notice through the Service or via email to your registered email address before the changes take effect.

Your continued use of the Service after changes constitute your acceptance of the revised Privacy Policy. We recommend checking this page periodically.

14. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or the handling of your personal information, please contact us:

Professional Reader Development Team

Representative: Sekito Shinjo / 新城世紀斗

Address: Naha-shi, Okinawa

Detailed address will be disclosed promptly upon request.

Email: contact@professional-reader.app

Will be disclosed promptly upon request.

Business Hours: Weekdays 9:00-18:00 (excluding weekends and holidays)

We will typically respond to inquiries within 5 business days.