Japanese Kanji Reading AssistantJAPANESE KANJI READING ASSISTANT
English
Back to homepage

PRIVACY POLICY

Privacy Policy

This policy explains what data Japanese Kanji Reading Assistant (the “Extension”) processes, why it processes that data, and how you can control or delete it.

Effective and last updated: August 22, 2026

1. Single purpose

The Extension displays readings above kanji on Japanese webpages, shows original foreign words above high-confidence katakana loanwords, and translates text that you actively select through an OpenAI-compatible API you configure. It does not use these capabilities for advertising, profiling, selling data, or any purpose unrelated to reading assistance.

2. Data processed locally

  • Webpage text undergoes Japanese morphological analysis in the browser to generate readings. This processing does not send the page text to a developer server.
  • Katakana loanwords are matched locally against a fixed etymology subset and manually curated common corrections bundled with the Extension. This feature does not query a remote dictionary or call a translation API.
  • Your API Key, BaseURL, model, target language, and interface language are stored locally in Chrome extension storage.
  • Translation history may include the selected source text, translation, page URL, page title, time, model, target language, and token usage. Token details include the page URL, page title, time, and usage. These records are stored locally.

3. Data sent to the user's chosen provider

Only when you actively request a translation are the selected text, target language, and necessary request instructions sent to the API BaseURL you configured. Your API Key is sent to that provider as authentication information with API requests. Clicking “Test connection” sends the fixed test text “こんにちは”. The Extension does not attach the page URL, page title, or local history to translation requests.

The remote provider processes received data under its own terms and privacy policy. Configure only a service you trust, and review its retention, training, and cross-border transfer practices. Remote endpoints must use HTTPS; only the localhost and 127.0.0.1 loopback addresses may use HTTP.

4. The developer does not collect or sell data

The Extension has no developer-operated data receiver, analytics SDK, or advertising SDK. The developer does not receive or sell your API Key, webpage text, selected text, browsing history, translation history, or token records, or disclose any of them to data brokers.

5. Retention and deletion

  • Settings and records have no fixed cloud retention period because they are stored only in your local browser.
  • Translation history retains at most 500 entries and is limited to approximately 4 MiB in total. Token records retain at most 1,000 entries and are limited to approximately 512 KiB in total. Older records are removed first when a limit is exceeded.
  • In the dashboard, you can delete individual history entries, clear all history, clear token records, or remove your API Key.
  • Uninstalling the Extension will normally remove the local data Chrome stored for it. To ensure deletion, clear your records and key in the dashboard before uninstalling.

6. How permissions are used

  • activeTab: accesses the current tab only when the user operates the Extension.
  • scripting: injects local readings, loanword-origin annotations, and the selection translation interface into the current page.
  • storage: stores settings, history, and token records locally.
  • Optional host permissions: requests network access only to the user-specified API origin when saving or testing API settings. The Extension does not obtain permanent, predefined permission to access every website.

7. Security boundaries

The API Key is never displayed in full in the dashboard or background responses, and extension storage is restricted to trusted extension contexts. These measures reduce accidental exposure, but local extension storage is not a hardware vault. Protect your browser profile and device account, and immediately revoke or rotate the key with your provider if you suspect it has been exposed.

8. Children, changes, and contact

The Extension is not a service designed specifically for children and does not actively create user accounts. If its features or data-processing practices materially change, this policy will be updated, including its date and explanation. Privacy questions may be submitted through the public project's GitHub Issues.

Open GitHub Issues