Legal Back to lyr.jp →

Last updated:

Privacy Policy

In this document, LYR is referred to as the “Service” and its developer, Kento Nakai (an individual developer), as the “Developer”. Contact: hello@lyr.jp

This is a translation. The Japanese version of this Privacy Policy is the original. If there is any discrepancy between the two, the Japanese version prevails.


1. Introduction

This Privacy Policy explains how LYR (the “Service”) handles your information. In addition to the app (Android and iOS versions), this Policy also applies to the early-tester application form (see 2.6) and the iOS release notification sign-up form (see 2.7) on the website lyr.jp. By using the Service, you are deemed to have agreed to this Policy.

Where the Service is offered: The Service is offered to users in the countries and regions the Developer has selected for distribution on Google Play and the App Store. It is not offered in the European Economic Area (EEA), the United Kingdom, Switzerland, Türkiye, Russia, mainland China, Vietnam, or Indonesia. Use from those regions is not contemplated, and the Service is not offered or advertised to users there.


2. Information We Collect and Why

The Service is a translation app that runs on Android devices and on iOS devices (iPhone). The iOS version offers audio translation only (Audio mode, see 2.3) and has no features that read text on the screen (2.1, 2.2). It processes only the following information.

2.1 Screen captures (Android only)

2.2 Text extracted by OCR, and recent translation history (Android only)

⚠️ About the information visible on your screen (important)

The Service reads the text displayed on your screen without distinguishing between kinds of text. Accordingly, if names, contact details, addresses, account information, descriptions relating to health, or similar information happened to be on screen when you ran a translation, that information is also sent for translation as text to be translated. As part of the history described above, it may be sent again with the next translation.

Likewise, if you translate a screen such as a messaging app, it may contain information about people other than yourself (for example, the person you are talking with).

The Developer does not use such information for any purpose other than translation and does not store it on any server. Even so, please do not run a translation on screens showing sensitive information or the personal information of others. If you do translate information about other people, you are responsible for confirming that doing so is appropriate.

2.3 Audio being played (Audio mode; Android and iOS)

Collected only when you use Audio mode.

⚠️ About the audio you play (important)

Audio mode treats all audio played on your device as input for recognition. If you play a call, or a recording that contains other people’s speech, that audio itself is sent to the server for recognition, and text generated from it is translated.

Please do not use Audio mode with sensitive content, or with audio containing other people’s speech. If you translate someone else’s voice, you are responsible for confirming that doing so is permitted (including any consent required for recording and translation).

2.4 Local settings and on-device activity log

Android: The following are stored only in DataStore / SharedPreferences on your device and are not transmitted externally.

Token usage and plan type (free / paid) are stored on your device, but are also transmitted in aggregate form as part of the usage data (see section 3.2).

iOS: The following are stored on your device (within the Service’s storage). The source and target languages are also included in translation requests (see 2.3), and some settings and operational information are also sent as aggregated usage data (see 3.2); nothing else here is transmitted externally.

2.5 Title of the content being played (Android only; optional; only if you enable notification access)

Used in Audio mode and real-time translation (Live) to translate proper nouns such as people’s names correctly. Collected only if you grant the Service “Notification access” in Android’s settings. The Service works without it, and nothing is collected if you do not grant it.

2.6 Early tester recruitment (application form on the website lyr.jp)

To recruit early testers for the Service, the application form on the website (lyr.jp) accepts the following information. It is not required to use the app.

2.7 iOS release notification sign-up (sign-up form on the website lyr.jp)

To let you know when the iOS version is released on the App Store, the sign-up form on the website (lyr.jp) accepts the following information. It is not required to use the app.


3. Disclosure to Third Parties / Transfers Outside Japan

3.1 Transfers outside Japan for translation processing (disclosure)

Text extracted by OCR is sent for translation by way of a relay server operated by the Developer (Cloudflare Workers). There are two processing routes, and which one is used is determined automatically based on the type of processing (manga, live subtitles, audio, full page, and so on), the language pair, and server availability. You cannot choose between them.

Currently, full-page translation (Page) uses (a). Manga, real-time translation (Live) and audio translation (Audio) use (b) first, and are translated via (a) when (b) is down or overloaded, or when (b) does not support the language pair. This allocation may change without notice based on quality, speed, and cost. The iOS version uses only (b) and never uses (a) (see 2.3).

On Android, on either route, what is sent is the text to be translated and the recent history described in 2.2 (except for the direct Live sending described below, which does not include the history). In Audio mode only, the audio itself and the pass (see 2.3) are additionally sent to the inference server in (b). In Live, when the title glossary (see 2.5) is available, the subtitle text and the pass are sent directly to (b) without going through the relay server (see 2.2). Otherwise, the device identifier is consumed at the relay server and is sent to neither route.

On iOS, what is sent to (b) is the stretches of device playback audio identified as speech, up to 2 recent subtitles (source text and translation), the source and target languages with the translation instructions, and the pass (see 2.3). Recognized text is produced on the inference server, so it is not sent from the device.

Item (a) External LLM API service (processing entrusted to a service provider) (b) Inference servers operated by the Developer (processing entrusted to a service provider)
Recipient An LLM API provider located in the United States. The provider’s name will be disclosed on request to the contact address at the end of this Policy. It may change without notice based on quality, speed, cost, and similar considerations The Developer runs translation and speech recognition models on servers rented from the cloud GPU provider RunPod (Runpod, Inc., United States). Processing takes place in the server’s memory. The rented servers are either in data centers contracted by RunPod (Secure Cloud) or on machines owned by third-party businesses or individuals vetted by RunPod (Community Cloud); in the latter case, the machine’s owner has physical access to it. We therefore treat (b) as a provision to third parties in a foreign country (the provider and the machine owners) as well (the provider may change based on quality, speed, cost, and similar considerations, in which case we will update this Policy)
Country of the recipient United States One of Taiwan, the United States, Canada, Japan, or a member state of the European Union (EU). We switch among these depending on speed, cost, and availability (servers outside this set are automatically refused at startup). If we add a country beyond this set, we will update this Policy in advance
Data transferred (Android only) The text to be translated extracted from the screen by OCR, and the recent history (2.2). In Audio mode when (b) is unavailable, the recognized text and the recent history Android: same as at left. In Audio mode, additionally the stretches of device playback audio identified as speech, and the pass (see “2.3”). In the Live case described above, the subtitle text and the pass. iOS: the stretches of audio identified as speech, up to 2 recent subtitles, the source and target languages with the translation instructions, and the pass
Data not transferred Device identifier, screen images, audio, account information, usage data Screen images, account information, usage data (the device identifier only as contained in the pass in Audio mode and in the Live case described above)
Purpose of transfer Solely to obtain the translation result Solely to obtain the translation result (in Audio mode, speech recognition and translation)
Timing of transfer Each time you run a translation Same as at left. In Audio mode, once per stretch of speech
Method of transfer API communication encrypted with HTTPS (TLS) Same as at left (by way of Cloudflare’s network)
Retention and use period Until translation processing completes. Discarded afterwards and not stored Same as at left. Audio likewise is discarded from memory as soon as recognition finishes and is not stored as a file
Data protection regime of the recipient country The country above is not recognized as having a level of protection equivalent to Japan’s (as the EU and the UK are). For an overview of each country’s regime, please refer to the survey of foreign personal information protection systems published by Japan’s Personal Information Protection Commission Taiwan, the United States, and Canada are not recognized as having a level of protection equivalent to Japan’s. EU member states are recognized as having an equivalent level. For an overview of each country’s regime, see the survey at left
Measures taken at the recipient Communications are encrypted with HTTPS (TLS) and what is sent is limited to the text to be translated and the recent history. In addition, our contract with the provider (data processing terms) confirms the following — that the text we send will not be used to train or tune AI models; that it will not be used or retained beyond what is necessary to provide the service; that security measures including encryption at rest and in transit and multi-factor authentication are in place, along with third-party audit (SOC 2 Type II); that a list of sub-processors is published and prior notice is given before additions; that we will be notified within 72 hours in the event of a breach; and that we may request deletion of data on termination. Furthermore, the Developer has enabled Zero Data Retention, so inputs and outputs are not stored by the provider In addition to the encryption above, the servers are configured with authentication so that only the Developer can access them. RunPod’s terms of service prohibit machine owners from inspecting or analyzing data inside customers’ servers (this is a contractual rule, not a technical guarantee). Audio and text are handled only in the server’s memory and are not stored as files. The servers’ operational logs are also configured not to retain the text to be translated, translation results, audio, or speech recognition results — only operational information such as language, number of lines, audio duration and processing time (see 4)

Legal basis (your consent): Provision to (a) and (b) is made based on your consent, after presenting the information above (the recipient country, its system for protecting personal information, and the measures taken at the recipient). For audio translation (Audio), before you start using it, a confirmation screen (on iOS, the last page of the first-launch guide) tells you that audio is processed on servers that may be outside your country, and asks for your consent.

About the relay server (Cloudflare): The relay server runs on the infrastructure of Cloudflare, Inc. (United States). Cloudflare only provides the infrastructure that relays and processes the communication and is not contracted to handle the content itself, so we do not treat this as a provision to Cloudflare. To keep communication with the inference servers fast, the relay server is configured to run at Cloudflare locations near Japan (Tokyo). Usage counters (see 4) are stored at Cloudflare locations in the Asia-Pacific region or the United States (each counter stays where it was first created, and processing used to take place in the United States). Your device’s connection, however, is received at the Cloudflare location nearest to you and reaches the relay server over Cloudflare’s network.

If you do not want these transfers: Sending text for translation is the core function of the Service, so the Service cannot be used without it. If you do not want these transfers, please refrain from using the Service. Note that “3.2 Usage Data” and “3.3 Crash Reports” (Android) are separate from translation and can each be turned off individually from the settings screen. “2.5 Title of the content being played” is not sent if you do not grant (or you revoke) notification access.

If there is a material change, we will update the “Last updated” date of this Policy to notify you.

3.2 Usage data (analytics)

This section applies to both the Android and iOS versions. Because the iOS version offers audio translation (Audio) only, it sends the items below that relate to audio translation, purchases, and common features.

To improve the quality of the Service, we collect and transmit the usage data listed below. It does not include information that directly identifies you personally, such as your name, email address, phone number, contacts, or precise location.

However, this is not “anonymized data” — it is pseudonymized data linked to a random identifier assigned per app installation. Activity within the same installation can be correlated.

Data transmitted:

What is not transmitted: Text read by OCR, audio, speech recognition results, translation results, screen content or images, the title of content being played, and the name of the foreground app are never included in telemetry (everything above consists of counts, durations, success/failure, and similar aggregates).

Recipients:

Opt-out: You can stop the transmissions described in this section at any time by turning off the switch at Settings → “Info & Privacy” → “Usage Data” in the Service (on iOS: Settings → “Privacy” → “Usage Data”). When it is off, nothing in this section is transmitted, including the automatic collection described above.

3.3 Crash reports (Android only)

The iOS version does not send these reports. Crash information reaches the Developer through Apple only if you have allowed “Share With App Developers” in iOS settings (subject to Apple’s privacy policy).

When the app terminates abnormally or an unexpected error occurs, the following information is sent to Firebase Crashlytics (United States), provided by Google LLC, in order to identify the cause.

Text read by OCR, audio, translation results, and screen content are not included.

Opt-out: You can stop the transmissions described in this section at any time by turning off the switch at Settings → “Info & Privacy” → “Crash Reports” in the Service. This is a separate switch from “3.2 Usage Data”; each can be toggled independently.

3.4 Where early-tester application data and iOS sign-up data are held

The application information in 2.6 and the sign-up information in 2.7 are stored and processed on the services of the following providers. All are managed under the Developer’s own accounts and are not used for any other purpose.

3.5 Other

Paid-plan purchases: On Android the paid plan is purchased on Google Play (Google LLC (United States)); on iOS, on the App Store (Apple Inc. (United States)). Payments are handled by each store. On iOS, verifying purchases and managing the state of the paid plan (reflecting renewals, cancellations and refunds) are entrusted to RevenueCat (RevenueCat, Inc. (United States), a processor). We send RevenueCat the purchase record issued by Apple and a random identifier that RevenueCat creates for each installation of the app (it is not tied to any login, name or email address). Only if you allow usage data (3.2) to be sent, we also pass the Firebase app instance ID to RevenueCat so that RevenueCat sends the number and amount of purchases and renewals to Google Analytics for revenue reporting. The device identifier is not passed to RevenueCat and is not attached to the purchase record (for Android, see the end of 2.2). Purchase records are kept by RevenueCat for as long as needed to manage the state of the paid plan.

Feedback and inquiries:

We do not provide information to any third parties other than those listed in 2.5 and 3.1 through 3.5. We do not use advertising networks and do not collect the advertising ID.

The relay server (Cloudflare Workers) and the network that carries audio run on the infrastructure of Cloudflare, Inc. (United States), and communications pass through its network.


4. Retention Periods


5. Permissions

The Service uses the following permissions and features.

Android

Permission Purpose
SYSTEM_ALERT_WINDOW Displaying translation results, subtitles and control buttons as an overlay
FOREGROUND_SERVICE / FOREGROUND_SERVICE_MEDIA_PROJECTION Capturing the screen and playback audio as a resident service while translation is running
POST_NOTIFICATIONS Displaying the notification that shows the service is running
VIBRATE Haptic feedback for interactions
INTERNET / ACCESS_NETWORK_STATE Sending translation and speech recognition requests and checking connectivity
RECORD_AUDIO Capturing device playback audio in Audio mode. Android requires this permission for AudioPlaybackCapture. It is not used for microphone recording (see “2.3”)
com.android.vending.BILLING Purchasing the paid plan on Google Play
Quick Settings tile (optional) To start translation from the Quick Settings panel (only if you add the tile)
Accessibility Service Detecting scroll stop, identifying the foreground app, and locating the main content area in browsers and similar apps (see section 6; text on the screen is not read)
Notification access (Notification Listener) Optional. Obtaining the title and channel name of the content being played (see 2.5; the content of notifications is not read). The app introduces this feature on first use and on the settings screen, but you grant the permission yourself in Android’s settings, and you can revoke it at any time. The Service works without it

In addition, the libraries we use (Firebase and Google Play services) declare permissions such as WAKE_LOCK for scheduling data transmission and similar purposes.

iOS

Feature Purpose
Screen recording (Broadcast Upload Extension) Receiving sound played by other apps (see 2.3). You start and stop it from iOS. Screen video and microphone audio are discarded as soon as they are received
Picture in Picture Showing subtitles on top of other apps. Subtitles are drawn on the device
Background audio Keeping the Service running while subtitles are shown in Picture in Picture. It neither plays nor records sound
In-App Purchase (StoreKit) Purchasing the paid plan on the App Store (see 3.5)

The app does not ask for access to the microphone, camera, photos, location, contacts, or notifications.


6. About Our Use of Accessibility Service (Android only)

The Service uses Accessibility Service for only the following three purposes.

Technically, we enable the permission that allows retrieving screen information (canRetrieveWindowContent). This is because, under Android’s design, this permission is required even just to learn the name of the foreground app (window information does not carry the app name directly; it can only be obtained by way of screen elements).

However, what we actually reference is only the foreground app’s package name, and the type, on-screen position and size of the component that displays web pages (WebView) — we do not read the text content on your screen or your input. The package name and positions are used only on your device and are neither stored nor transmitted (the foreground app’s package name is also used on your device to match the content title described in 2.5). We also do not grant the permission to perform touch gestures (canPerformGestures).


7. Age Requirement

The Service is not intended for use by anyone under the age of 13 (under the age of 14 if you are in South Korea). If this applies to you, please use the Service with the consent of a parent or guardian, or refrain from using it.


8. Deleting and Exporting Data

All on-device data (translation cache and settings, and the iOS activity log and device identifier) is deleted when you uninstall the app. Because the device identifier and activity log are excluded from backups, restoring from a backup does not bring them back. Text to be translated, translation results, and audio are not stored on the relay server, the inference servers, or the translation service. Titles of content being played are deleted automatically once the period in section 4 has passed.

By contrast, the data transmitted under “3.2 Usage Data” and “3.3 Crash Reports” (Android) remains in Firebase and in Google BigQuery managed by the Developer for a limited period (see “4. Retention Periods”). This is statistical data linked to a random per-installation identifier, and the Developer has no means of connecting it to you personally. For that reason, we may be unable to act on requests to delete specific data. If you want to stop future transmissions, please turn them off from the settings screen.


8-2. Your Rights (Requests for Disclosure and Similar)

You may request notification of the purpose of use, disclosure, correction, addition, deletion, suspension of use, erasure, and disclosure of records of third-party provision with respect to information about you held by the Developer. There is no charge.

Note that the data transmitted under “3.2 Usage Data” and “3.3 Crash Reports” is statistical data linked to a random per-installation identifier, and the Developer has no means of connecting it to you personally. Accordingly, for that data we may be unable to identify you and may be unable to act on individual requests. If you want to stop future transmissions, you can turn them off from the settings screen at any time.

Where to file complaints

In addition to the contact address above, complaints about how the Service handles personal information may be filed with the Personal Information Protection Commission of Japan (https://www.ppc.go.jp/).

Information about the Developer

The Developer’s name is stated at the top of this Policy. The address will be provided without delay on request to the contact address above.


8-3. Security Measures

The Developer takes the following security measures for the information it handles.


9. Changes to This Policy

This Policy may be revised as needed. If there is a material change, we will notify you through an in-app notice or by updating the “Last updated” date at the top of this Policy.


10. Contact

For questions about this Policy, please contact us at:


11. Governing Law

This Policy is governed by the laws of Japan.


Revision history