Betaphonia
Last updated · 2025-05-03

Magic Screen · Privacy Policy

Jeon Seok-ho (hereinafter referred to as the "Developer") places great importance on the privacy of users who use the mobile application (hereinafter referred to as the "App") and related services (collectively, the "Services") provided by the Developer. This Privacy Policy explains how the Developer collects, uses, and discloses personal information.

By providing your personal information to the Developer, you are deemed to have fully understood and agreed to this Privacy Policy.

If you do not agree to this policy, please refrain from providing personal information.

In the event of any amendments to this Privacy Policy, the Developer will notify users via the website with the reason and details of such changes.

This Privacy Policy is effective as of May 3, 2025.

Article 1 (Purpose of Personal Information Processing)

The Developer processes personal information for the following purposes. The collected information will not be used for any purposes other than those specified below. If the purpose of use is changed, the Developer will take necessary steps such as obtaining additional consent in accordance with Article 18 of the Personal Information Protection Act.

  • The app does not store any personal information locally.
  • The app includes AdMob (advertising program). You can view AdMob's privacy policy here.
  • For service improvement, the app uses Google Analytics, Firebase Crashlytics, Facebook, and Flurry Analytics to collect the following:
    • App install, uninstall, update events
    • Device model and OS version
    • App event location, gender, age group, and traffic source
  • The app uses Firebase Authentication to collect users' email address, display name, and Firebase UID for login, user identification, and ranking features.

Article 2 (Retention and Use Period of Personal Information)

The Developer retains and uses personal information within the period agreed upon by the user or required by law.

Article 3 (Provision of Personal Information to Third Parties)

The Developer does not provide personal information to third parties except in cases where the user consents or as required by laws and regulations (Articles 17 and 18 of the Personal Information Protection Act).

Article 4 (Entrustment of Personal Information Processing)

The Developer does not entrust the processing of personal information to any third party.

Article 5 (User Rights and How to Exercise Them)

Users may exercise the following rights at any time regarding their personal information:

  • The right to access, correct, delete, or suspend processing of personal data
  • These rights may be exercised via written request, email, or fax, in accordance with Article 41(1) of the Enforcement Decree of the Personal Information Protection Act.
  • A legal representative or authorized agent may exercise these rights on behalf of the user, provided a power of attorney is submitted.
  • The right to access or suspend processing may be restricted in accordance with Articles 35(5) and 37(2) of the Act.
  • Requests for deletion may not be granted if the information is required by other laws.
  • The Developer may verify the identity of the requester to ensure the legitimacy of the request.

Article 6 (Items of Personal Information Collected)

The Developer processes the following information:

  • App: When logging in — email address, display name, Firebase UID

Third-party privacy policies used in the app:

Article 7 (Destruction of Personal Information)

The Developer will destroy personal information without delay when it becomes unnecessary, such as when the retention period expires or the processing purpose is achieved.

  • Destruction procedure: Information is selected for deletion with approval from the privacy officer.
  • Destruction method:
    • Electronic files: Permanently deleted using irreversible methods
    • Paper records: Shredded or incinerated

Article 8 (Measures to Ensure the Safety of Personal Information)

The Developer takes the following security measures to protect personal information:

  • Administrative: Internal management plan, regular staff training
  • Technical: Access control systems, encryption of sensitive data
  • Physical: Access control to data storage rooms and computer systems

Article 9 (Automatic Collection and Rejection of Tracking Technologies)

The Developer may collect your ADID/IDFA, which is a mobile advertising identifier used to provide personalized ads and improve service quality.

How to opt-out:

  • Android: Settings → Google Settings → Ads → Opt out of Ads Personalization
  • iOS: Settings → Privacy → Advertising → Limit Ad Tracking

Article 10 (Additional Information for U.S. Users)

The Developer does not sell your personal information.

Under the California Consumer Privacy Act (CCPA), U.S. users have the following rights:

  • The right to request disclosure of collected data
  • The right to request deletion of personal data
  • The right to opt-out of the sale of personal data

To exercise these rights, contact: skylur@naver.com

Article 11 (Additional Information for Japanese Users)

Personal information of Japanese users may be transferred outside of Japan for advertising or service improvements.

The Developer complies with Japan's Act on the Protection of Personal Information (APPI) and takes appropriate security measures. Requests related to personal information can be made by email or in writing.

Article 12 (Personal Information Protection Officer)

If you have any inquiries or complaints regarding personal data, please contact the Developer:

  • Contact: skylur@naver.com
  • Firebase-related privacy inquiries may also be directed to the above address.

You may also contact the following agencies for additional support:

Article 13 (Duty to Notify)

If any additions, deletions, or changes are made to this Privacy Policy, the Developer will notify users at least 7 days in advance via the website.

However, changes related to key user rights (e.g., new data collection, third-party sharing) will be notified at least 30 days in advance.

  • Notice date: May 3, 2025
  • Effective date: May 3, 2025