Bubble Level Privacy Policy
Last Updated: 2026-05-08
Bubble Level (hereinafter referred to as the “App”) is a free app that provides level measurement and calibration functions. This Policy has been prepared based on the Personal Information Protection Act of the Republic of Korea and explains the matters directly processed by the App operator as well as the use of third-party SDKs required for Google Play Data Safety submissions. Inquiries and requests related to personal information directly processed by the App operator will be reviewed based on this Policy and applicable laws of the Republic of Korea.
1. Information Directly Processed by the App Operator
The App does not provide any function for entering personally identifiable information such as name, email address, or phone number, and does not transmit such personally identifiable information to the App operator’s own servers.
To provide its functions and maintain settings, the App may store or process the following information on the user’s device.
- Device sensor data
- Item: Accelerometer data
- Purpose: To provide level measurement and calibration functions
- Processing method: Processed in real time on the device
- Retention and transmission: Under the current implementation of the App, the App does not provide a function that continuously records or stores all raw accelerometer measurements. However, such data may be temporarily processed in memory for screen display, lock display, and calibration calculations. When the calibration function is used, calibration values calculated from raw measurements may be stored as local settings as described below. The App operator does not provide a function for transmitting raw accelerometer measurements to its own servers.
- Local settings
- Items: Calibration values (`calibrationX`, `calibrationY`), whether ads are displayed (`showAds`), app language (`appLanguage`), and analytics consent status (`analyticsConsentGranted`)
- Purpose: To maintain calibration values, app settings, language settings, and analytics consent status
- Storage location: AsyncStorage on the user’s device
- Retention period: These values may remain on the device until the user changes the settings, resets the calibration values, deletes the App data through the operating system, or deletes the App.
2. Third-Party Advertising and Analytics Tools
The App includes the following third-party SDKs for advertising and app quality improvement. These SDKs may process relevant data for advertising, analytics, security, fraud prevention, and service improvement, even if such information is not directly collected by the App operator.
2-1. Google Mobile Ads (AdMob)
- Purpose: To display ads, measure advertising performance, and prevent fraudulent use
- Information that may be processed: Advertising ID, IP address, approximate location, device information, app interactions, ad interaction information, and similar data
- Timing and method of processing: Such information may be transmitted to Google’s global infrastructure through the SDK during ad requests, ad display, and advertising performance measurement.
- App settings: The current App is configured to use the non-personalized ads request option (`requestNonPersonalizedAdsOnly`) when requesting ads. However, the actual method of ad processing may vary depending on Google policies, user settings, applicable regional laws, and SDK behavior.
- Choices: Users may manage advertising-related choices through Android advertising settings, Google advertising settings, or Google advertising privacy options provided depending on their region and Google policies.
- Reference policy: https://policies.google.com/privacy
2-2. Google Firebase Analytics
- Purpose: To analyze usage statistics, screen views, and improve app quality
- Information that may be processed: App usage information, screen views, event information, basic device information, app diagnostic information, automatic events, and similar data
- Timing and method of processing: Such information may be transmitted to Google or Firebase’s global infrastructure through the SDK during App launch, SDK initialization, and use of analytics functions to which the user has consented.
- Consent settings: The App checks the consent status and then applies the consent or collection settings for Firebase Analytics. Custom analytics events and screen view records defined by the App operator are used only when the user has allowed analytics consent in the App settings.
- Important note: The Firebase Analytics SDK may process basic app usage information, device information, automatic events, and similar data during App launch and SDK initialization.
- Choices: Users may allow or withdraw analytics consent in the App settings.
- Reference policy: https://firebase.google.com/support/privacy
2-3. Microsoft Clarity
- Purpose: To analyze user behavior, improve usability, and improve app quality
- Information that may be processed: App usage information, screen usage flow, user interactions, device and session-related information, and similar data
- Timing and method of processing: If the SDK is initialized after the user has allowed analytics consent, such information may be transmitted to Microsoft’s global infrastructure.
- Consent settings: The App activates Microsoft Clarity only when the user has allowed analytics consent in the App settings. If consent is withdrawn, the App subsequently calls the function to stop collection.
- Choices: Users may allow or withdraw analytics consent in the App settings.
- Reference policy: https://www.microsoft.com/privacy/privacystatement
3. Reason for Explaining the Google Play Data Safety Section Together
This section is not intended to provide a separate choice function to users. Rather, it is provided to ensure that the description in this Privacy Policy is consistent with the Data Safety section of the App published on Google Play.
The Google Play Data Safety section must reflect not only data directly processed by the App operator, but also data that may be collected or shared by third-party SDKs included in the App. Therefore, separate from the fact that the App operator does not collect personally identifiable information through its own servers, this Policy also discloses data that may be processed by AdMob, Firebase Analytics, and Microsoft Clarity.
The collection, sharing, processing purposes, and availability of user choices displayed in the Google Play Data Safety section are based on the actual functions of the App version currently distributed on Google Play and the behavior of third-party SDKs.
4. User Choices and Control
- Analytics consent: Users may allow or withdraw analytics consent in the App settings. Even if analytics consent is refused or withdrawn, users can still use the core functions of the App, such as level measurement, calibration, and language settings.
- Deletion of calibration values: Users may delete local calibration values by using the reset function in the App, deleting App data through the operating system, or deleting the App.
- Advertising-related choices: Users may manage advertising-related choices, such as resetting the advertising ID or limiting personalized ads, through Android advertising settings, Google advertising settings, or Google advertising privacy options provided depending on their region and Google policies.
- Data held by external providers: Requests concerning data held by Google or Microsoft are subject to each provider’s privacy policy and settings tools.
- Scope of direct processing by the App operator: Users may contact the inquiry contact listed in this Policy regarding inquiries or requests related to personal information directly processed by the App operator.
5. Retention and Deletion
- The App operator does not directly collect sensitive personal information.
- All raw accelerometer measurements may be temporarily processed in memory for level calculations, screen display, lock display, and calibration calculations. Under the current implementation of the App, the App does not provide a function that continuously records or stores all raw measurements. However, when the calibration function is used, calibration values (`calibrationX`, `calibrationY`) calculated from raw measurements may be stored as local settings data.
- Local settings data may be stored on the device until the user changes the settings, resets the calibration values, deletes the App data through the operating system, or deletes the App.
- If the user withdraws analytics consent in the App settings, the App will stop subsequent custom analytics events and screen view records and will call the consent or collection-stop functions of Firebase Analytics and Microsoft Clarity.
- The retention periods and deletion methods for data already processed by advertising and analytics SDKs are subject to the privacy policies and service policies of each external provider.
6. Overseas Processing and Transfer
The App operator does not transfer users’ personal information overseas through its own servers. However, Google and Microsoft may process relevant data through each provider’s global infrastructure, including servers located overseas such as in the United States, in the course of providing advertising or analytics functions.
The following describes the main processing timing and methods to the extent understood by the App operator. Specific processing countries, retention periods, deletion methods, and whether data is provided to third parties are subject to each provider’s policies.
1) Google Mobile Ads (AdMob)
- Information that may be processed: Advertising-related data such as IP address, advertising ID, app interactions, device information, and approximate location
- Timing and method of processing: Such information may be transmitted to Google’s global infrastructure through the SDK during ad requests, ad display, and advertising performance measurement.
- Purpose: To provide ads, measure advertising performance, and prevent fraud
- Choices: Users may change settings if advertising privacy options are enabled in the App, and may also use Google advertising settings and Android/iOS advertising settings.
2) Firebase Analytics
- Information that may be processed: Usage statistics data such as app usage information, screen views, event information, and device information
- Timing and method of processing: Such information may be transmitted to Google/Firebase’s global infrastructure through the SDK during App launch, SDK initialization, and use of analytics functions to which the user has consented.
- Purpose: To analyze usage statistics and improve app quality
- Choices: Users may withdraw analytics consent in the App settings.
3) Microsoft Clarity
- Information that may be processed: App usage information, user behavior data, and device and session-related information
- Timing and method of processing: If Microsoft Clarity is initialized after the user has allowed analytics consent, such information may be transmitted to Microsoft’s global infrastructure through the SDK.
- Purpose: To analyze usability and improve app quality
- Choices: Users may withdraw analytics consent in the App settings.
7. Permissions and Access
The App uses the device’s accelerometer data for the level measurement function. Raw accelerometer measurements may be temporarily processed on the device for level calculations, screen display, lock display, and calibration calculations. Under the current implementation of the App, the App does not provide a function that continuously records or stores all raw measurements. However, when the calibration function is used, calibration values calculated from raw measurements may be stored as local settings on the device.
The App may use the network to the extent necessary for displaying ads and operating third-party SDKs. The current App does not provide any function that directly requests access permissions for the camera, contacts, location, microphone, or files, and does not provide any function that collects data through such permissions and transmits it to the App operator’s own servers.
8. Children and Adolescents
Although the App’s Google Play content rating may be displayed as suitable for ages 3 and above, the App is not designed as a service primarily directed at specific children. In addition, the App does not provide any function for entering personally identifiable information such as name, email address, or phone number. Ad exposure is subject to Google Mobile Ads policies, and guardians may limit the receipt of personalized ads through device OS settings or the Google advertising settings page.
9. Security Measures
- The App operator does not store users’ personal information in its own server-side database.
- Local settings are stored on the user’s device.
- The App does not directly collect sensitive information or unique identification information.
- The analytics function checks the user’s consent status and then applies the consent or collection settings. However, during App launch and SDK initialization, the Firebase Analytics SDK may process basic app usage information, device information, automatic events, and similar data.
- The current App is configured to use the non-personalized ads request option when requesting ads. However, the actual method of ad processing may vary depending on Google policies, user settings, applicable regional laws, and SDK behavior.
10. Policy Changes and Contact Information
- If the service details or applicable laws change, this Policy will be updated and the revision date will be indicated.
- Personal Information Protection Officer and grievance handling contact: App operator
- Email: denver.gl.goo@gmail.com
- When making an inquiry, please avoid disclosing unnecessary personal information and provide only the information necessary for the inquiry.
This Policy takes effect on 2026-05-08.