Snap Palette Privacy Policy
Last Updated: 2026-05-08
Snap Palette (the “App”) is a free app that extracts colors from images captured or selected by users. This Policy has been prepared based on the Republic of Korea’s Personal Information Protection Act 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 users to enter 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.
- Image Information
- Items: Images captured by the user or selected from the device photo library, color extraction results
- Purpose: Taking photos, selecting images, extracting colors, and saving or sharing result images requested by the user
- Processing method: Processed on the device
- Retention and transmission: The App operator does not transmit or store captured/selected images or color extraction results on its own servers. However, temporary files may be created during the operation of the App, and result images that the user directly saves to the device photo library may remain on the device until the user deletes them.
- Local Settings
- Items: App language (`appLanguage`), screen theme (`app_theme_mode`), whether ads are shown (`showAds`), whether the camera grid is shown (`showCameraGrid`), analytics consent status (`analyticsConsentGranted`), permission notice confirmation status (`permissionsConfirmed`), ad display control information (`admobResultCompletedCount`, `admobLastResultInterstitialShownAt`), and calibration values if such functional calibration values are stored (`valueX`, `valueY`)
- Purpose: Maintaining App settings, managing consent status, managing permission notice status, controlling ad display frequency, and improving App operation
- Storage location: Local storage on the user’s device, such as AsyncStorage
- Retention period: The information may remain on the device until the user changes the settings, deletes 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 improving App quality. These SDKs may process relevant data for purposes such as ad delivery, 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) and UMP
- Purpose: Displaying ads, measuring ad performance, confirming advertising-related consent and privacy options, and preventing fraud
- Information that may be processed: Advertising ID, IP address, approximate location, device information, App information, App interactions, ad interaction information, consent status, etc.
- Timing and method of processing: During ad requests, ad display, and ad performance measurement, data may be transmitted through the SDK to Google’s global infrastructure.
- Choice options: Users may manage advertising-related choices through Android/iOS advertising settings, Google advertising settings, or Google advertising privacy options provided according to the user’s region and Google policies.
- Reference policy: https://policies.google.com/privacy
2-2. Google Analytics for Firebase
- Purpose: Analyzing usage statistics, analyzing screen views, and improving App quality
- Information that may be processed: App usage information, screen views, event information, basic device information, App diagnostic information, automatically collected events, etc.
- Timing and method of processing: During App launch, SDK initialization, and the use of analytics functions consented to by the user, data may be transmitted through the SDK to Google’s or Firebase’s global infrastructure.
- Consent settings: The App checks the consent status and then applies Firebase Analytics consent or collection settings. Custom analytics events and screen view records defined by the App operator are used when the user has allowed analytics consent in the App settings.
- Notice: The Firebase Analytics SDK may process basic App usage information, device information, automatically collected events, and similar data during App launch and SDK initialization.
- Choice options: Users may allow or withdraw analytics consent in the App settings.
- Reference policy: https://firebase.google.com/support/privacy
2-3. Microsoft Clarity
- Purpose: Analyzing user behavior, improving usability, and improving App quality
- Information that may be processed: App usage information, screen usage flow, user interactions, device and session-related information, etc.
- Timing and method of processing: If the SDK is initialized after the user has allowed analytics consent, data may be transmitted to Microsoft’s global infrastructure.
- Consent settings: The App activates Microsoft Clarity when the user has allowed analytics consent in the App settings. If consent is withdrawn, the App subsequently calls the function to stop collection.
- Choice options: 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 users with a separate choice function. Rather, it is provided to ensure that the explanation 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 operation 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 App’s core functions, such as image selection, photo capture, and color extraction.
- Advertising-related choices: Users may manage advertising-related choices, such as resetting the advertising ID or limiting personalized ads, through Android/iOS advertising settings, Google advertising settings, or Google advertising privacy options provided according to the user’s region and Google policies.
- Permission management: Users may allow or withdraw camera access permission, photo storage permission, and similar permissions through the device operating system settings.
- Local data deletion: Users may delete local settings and consent status by using the operating system’s App data deletion function or by deleting the App.
- Data held by external providers: Requests regarding 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: Inquiries or requests related to personal information directly processed by the App operator may be sent to the contact information provided in this Policy.
5. Retention and Deletion
- The App operator does not directly collect sensitive personal information.
- The App operator does not store users’ personal information, captured/selected images, or color extraction results on its own servers.
- Local settings data may be stored on the device until the user changes the settings, deletes App data through the operating system, or deletes the App.
- Temporary files created during App function processing may be deleted during App operation or according to the operating system’s policies.
- Result images that the user directly saves to the device photo library are stored on the device until the user directly deletes them.
- If the user withdraws analytics consent in the App settings, the App stops subsequent custom analytics events and screen view records, and calls 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 in the United States and other countries, in the course of providing advertising or analytics functions.
The following describes the main processing timings 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: During ad requests, ad display, and ad performance measurement, data may be transmitted through the SDK to Google’s global infrastructure.
- Purpose: Providing ads, measuring ad performance, and preventing fraud
- Choice options: Users may change options 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: During App launch, SDK initialization, and the use of analytics functions consented to by the user, data may be transmitted through the SDK to Google/Firebase’s global infrastructure.
- Purpose: Analyzing usage statistics and improving App quality
- Choice options: 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, data may be transmitted through the SDK to Microsoft’s global infrastructure.
- Purpose: Analyzing usability and improving App quality
- Choice options: Users may withdraw analytics consent in the App settings.
7. Permissions and Access
- The App may use camera access permission to take photos. Photos or videos taken are not recorded or transmitted to the App operator’s own servers, and the App does not request microphone permission.
- The App may use photo selection and photo add/save access so that users can select images from device photos or save result images to the device photo library. Photo selection uses the device photo library flow provided by the operating system or an equivalent process.
- On Android, advertising ID permission may be used to provide ads. The App may use the network to the extent necessary for displaying ads, viewing the Privacy Policy, confirming advertising consent/privacy options, and operating analytics SDKs.
- Currently, the App does not provide any function that collects data through contacts, location, or microphone permissions and sends it to the App operator’s own servers.
8. Children and Adolescents
The App’s Google Play content rating may be displayed as suitable for ages 3 and up; however, the App is not designed as a service primarily directed to children. In addition, the App does not provide any function for users to enter personally identifiable information such as name, email address, or phone number.
Ad display is subject to Google Mobile Ads policies, and guardians may limit the receipt of personalized ads through the 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.
- Captured/selected images and color extraction results are processed on the device.
- Local settings and consent status are stored on the device.
- The App does not directly collect sensitive information or unique identification information.
- For analytics functions, the App checks the user’s consent status and then applies consent or collection settings. However, during App launch and SDK initialization, the Firebase Analytics SDK may process basic App usage information, device information, automatically collected events, and similar data.
- The security, retention periods, deletion methods, and choice tools of external SDKs are subject to each provider’s privacy policy and service policies.
10. Policy Changes and Contact Information
- If the service content or applicable laws change, this Policy will be updated and the revision date will be indicated.
- Person responsible for personal information protection and complaint handling: App operator
- Email: denver.gl.goo@gmail.com
- When making an inquiry, please avoid disclosing personal information and provide only the information necessary for the inquiry.
This Policy takes effect on 2026-05-08.