Privacy Policy

Eye Got It (the "App") is an application that lets you use one device as a camera and, from a browser on another device, view video and audio and perform supported operations.

The App does not require account registration and is designed on the basis of direct communication between devices.

This Privacy Policy (the "Policy") explains how user information is handled in the App.

1. Operator Information

• App name: Eye Got It
• Operator: [To be confirmed before publication: operator's name]
• Location: Japan
• Contact: [To be confirmed before publication: support email address]

The Operator's address and other matters required to be disclosed by law will be provided in accordance with applicable laws by appropriate means, including responding to requests made through the contact above.

2. Information We Handle

Account Information

The App has no account registration feature and does not ask you to register your name, email address, phone number or the like in order to use it.

If you contact us, we handle the information described in Section 7.

Camera Video and Audio

The App uses the device's camera and microphone and streams video and audio in real time to connected devices.

The Operator does not collect or store the streamed video and audio on its own servers, and does not use them for advertising, usage analytics, training AI models or the like.

Video and audio may be temporarily held and processed on devices to the extent necessary for communication and playback.

The App does not provide a feature for recording or saving video and audio. However, the Operator does not control screen recording or data storage performed independently by the viewing device, its OS, browser or the like.

Connection Information

To connect and operate devices, we handle the following information:

• Local IP addresses and port numbers
• Connection destination information contained in QR codes
• Connection tokens and session identifiers
• Connection status and communication control information
• Information needed to operate the camera

This information is used to connect devices, communicate between them and provide features.

The Operator does not provide any mechanism for continuously monitoring users' connection destinations or communication content.

Device Permissions

Depending on the features provided, the App uses permissions related to the camera, microphone, local network and the like.

These permissions are used to provide the corresponding features, and changes to permissions follow the OS's specifications and settings.

The App is not intended to obtain precise GPS location information.

3. Communication Between Devices

In principle, the App connects devices on the same local network via Wi-Fi, supported tethering or the like.

The App uses WebRTC for real-time streaming of video and audio. The viewing device can connect from a supported web browser.

The camera device may serve the viewing page and other resources needed for connection over local HTTP. WebRTC video and audio communication and HTTP communication use different protection methods, and HTTP communication is not protected by encryption equivalent to HTTPS.

The security of communication between devices also depends on the environment, such as the network, devices and OS used. The Operator does not guarantee that it can prevent all unauthorized access, interception, tampering or the like in communication.

The history, cache and the like of the viewing browser are subject to the specifications and settings of that browser and OS.

4. Information Stored on the Device

Camera Device

To provide its features, the App may store the following information on the camera device:

• Usage time of the free allowance and information needed for its renewal
• Feature unlock status from in-app purchases
• App settings
• Consent status for the Terms of Use and the like
• Your choice about sending usage and crash information
• Connection keys (authentication information contained in QR codes and connection URLs)
• Temporary information needed to manage connections

This information is retained for as long as needed to provide each feature.

Connection keys are stored in the OS's secure storage, only on that device, and are not synced to other devices. A connection key is retained until the user performs "Refresh URL" in the App, and does not become invalid with the passage of time or when a connection ends. Performing "Refresh URL" replaces it with a new key, after which the previous key, and the reconnection information saved in browsers that connected with the previous key, can no longer be used. If the App is deleted and then reinstalled, the previous connection key is deleted the first time the App is launched after reinstallation.

Receiving Browser

When a connection URL is opened on a receiving device, the following information may be saved in that browser's storage:

• Information for returning to the current session (session identifier and reconnection key): saved only for that browser tab, and deleted when, for example, the connection is ended on the camera side. It is also deleted, according to the browser's specifications, when the tab is closed.
• Information for reconnecting from the same URL (not the connection key itself, but information converted for that browser only): can be used to reconnect until "Refresh URL" is performed on the camera side. After "Refresh URL" it can no longer be used, but the App does not delete this information from the browser. It may remain in that browser until the browser's data is deleted or it is deleted according to the browser's specifications or settings.

Information saved in the receiving browser can be deleted from that browser's settings. Neither the camera device nor the Operator can delete information saved in the receiving browser.

Deleting Stored Information

Some information is erased when the App is deleted, but information stored in the OS's secure storage, device backups or the like may remain or be restored after deletion.

The Operator does not centrally manage this on-device information on its own servers and does not provide a feature to remotely view or delete information stored on users' devices.

5. In-App Purchases and External Services

In-App Purchases

The App offers a one-time in-app purchase.

Payments are processed through the app store from which you obtained the App (currently the Apple App Store).

The Operator does not directly obtain payment information such as credit card numbers or bank account numbers through the App.

To verify and restore purchase status, the app store may handle product identifiers, transaction identifiers, purchase date and time, purchase status and other information needed to manage purchases. The App directly uses the purchase system provided by the app store and does not use any purchase management service other than the app store.

The App stores the result of checking whether a purchase has been made on the device, as described in Section 4.

Purchase-related information is stored and managed in accordance with the rules of each app store.

• Apple: https://www.apple.com/legal/privacy/

Advertising and Tracking

The App does not display third-party advertising and does not perform tracking for the purpose of ad delivery.

The Operator does not sell users' personal information or share it with third parties for cross-context behavioral advertising.

Sending Usage and Crash Information (Optional)

To understand how the App is used and to investigate problems, the App uses Firebase (Google Analytics for Firebase and Firebase Crashlytics), provided by Google LLC.

By default, this information is not sent. It is sent only if the user chooses "Help improve" in the App's prompt, or turns on "Send usage and crashes" in "About this app". Every feature of the App can be used without turning on sending. This choice is stored on the camera device (Section 4).

[To be confirmed before publication: results of on-device confirmation of whether communication accompanying Firebase initialization (such as registering identifiers) occurs before sending is turned on, and a description if it does]

When sending is turned on, the following information is sent:

• Usage of the App: launches, QR code displays, connection successes and failures and their reasons, connection time and number of connected devices, the free allowance running out and renewing, views of the paid upgrade screen, and purchase and restore results
• Usage that Firebase records automatically: first launch, start of use, in-app purchases (product identifier, price and currency) and the like
• Crash information: records of how the App behaved when a crash or problem occurred, and codes defined by the App indicating the type of problem
• Device model, OS version, language and App version
• Identifiers that Firebase creates for the App
• Approximate region estimated from the IP address of the connection

The following information is not sent:

• Camera video and audio
• The contents of QR codes and connection URLs, and connection keys
• Device names
• Information that directly identifies the user, such as name or email address
• Advertising identifiers

The information sent is used to improve usability and connection quality, to investigate problems and to improve stability, and is not used for ad delivery.

If "Send usage and crashes" in "About this app" is turned off, sending of usage information stops immediately, and sending of crash information stops from the next launch.

Even while sending is not turned on, crash information may be recorded on the device. The App deletes unsent crash information on the device when it is launched with sending turned off, and immediately before sending is turned on. Therefore, crash information recorded while sending was turned off is not sent even if sending is turned on later.

[To be confirmed before publication: results of confirming that usage information held on the device while offline is not sent after sending is turned off]

The retention periods for the information sent are as follows:

• Usage information (Google Analytics for Firebase): [To be confirmed before publication: the Google Analytics data retention setting (applies to user-level and event-level data, not to aggregated reports)]
• Crash information (Firebase Crashlytics): [To be confirmed before publication: the Firebase Crashlytics retention period at the time of publication (according to Google's published information, crash records and associated identifiers are kept for 90 days before the removal process begins)]

For how Google handles information, please see Google's Privacy Policy.

• Google: https://policies.google.com/privacy

Provision to Third Parties

Information handled by the Operator may, in the following cases, be provided to or processed by external businesses and others to the extent necessary:

• Payment for in-app purchases, and verification and restoration of purchase status
• Use of email services and the like in responding to inquiries
• Use of external services described in this Policy
• Where based on laws, or as otherwise permitted by applicable laws

Streaming of video and audio between devices through users' operations does not constitute the Operator itself collecting that information or providing it to third parties.

6. International Transfers and Your Rights

International Transfers

Information related to in-app purchases, responding to inquiries and the like, and usage and crash information when the user has turned on sending, may be processed and stored outside Japan or your country or region of residence, depending on the external services used.

When the Operator transfers personal data abroad, it uses the necessary safeguards and transfer mechanisms in accordance with applicable laws.

[To be confirmed before publication: the countries and regions where Firebase (Google LLC) processes and stores information, the legal basis and safeguards for transfer that must be disclosed under applicable laws, and information on foreign systems that must be provided to users in Japan]

Legal Bases for Processing Personal Data

In the EU/EEA, the United Kingdom and other regions that require a legal basis for processing personal data, we handle information on the following bases in accordance with applicable laws:

• Providing app features and managing purchases: performance of a contract
• Responding to inquiries: legitimate interests, or performance of a contract depending on the circumstances
• Sending usage and crash information: the user's consent (consent can be withdrawn at any time, without affecting the lawfulness of processing before withdrawal)
• Responding to misuse and protecting legitimate rights: legitimate interests
• Actions required by law: compliance with legal obligations

When processing on the basis of legitimate interests, we take into account the necessity of the processing and users' rights and interests.

Your Rights

In accordance with applicable laws, you may have rights regarding your personal data handled by the Operator, such as access, rectification, erasure, suspension of use, restriction of processing, objection and data portability. You may also lodge a complaint with the competent supervisory authority or the like in accordance with applicable laws.

The content of these rights, the conditions for exercising them and the Operator's obligations to respond differ depending on applicable laws.

Because the App does not require account registration, the Operator may not hold information that identifies a specific user.

If we do not hold the relevant information, or cannot identify the relevant data even after the necessary checks, we may be unable to respond to individual requests for access, rectification, erasure or the like.

For requests based on law, we will verify identity and the relevant information as necessary and respond in accordance with applicable laws. Where permitted by law, we may limit our response to a request.

7. Contact and Changes to This Policy

Contact

Inquiries about the App and the handling of personal information are accepted at the following contact:

[To be confirmed before publication: support email address]

When you contact us, we handle the sender's email address, message content, attachments and the like in order to review the content, provide any necessary reply, investigate issues, keep records of our handling and respond to legal claims.

This information is retained for as long as necessary for handling inquiries, record keeping, dispute handling or legal obligations. The retention period is determined based on the content of the inquiry, the status of handling, applicable laws and the like.

We do not guarantee individual replies or action for every general question, comment, request or the like. However, this does not affect any obligation to respond under applicable laws or app store rules.

Changes to This Policy

The Operator may revise this Policy in response to changes in features or external services, amendments to laws and the like.

The revised content will be made available, together with the date of update, in the App, on a public page or the like. For changes that require notice or consent under applicable laws, we will follow those laws.