SaengSaeng Card (SugarCard)
Effective date: October 4, 2026
This policy applies to the Android app SaengSaeng Card – SugarCard (package name com.sugarmount.sugarcard), published by simpest under the developer name SugarMount (“we”, “us”). It describes, based on the actual implementation, what data the app handles and what it does not.
1. Summary
| Data | How it is handled | Processed by |
|---|---|---|
| Card messages, finished card images and videos | Created and stored on your device only. Never sent to our servers. When you choose to share, they go only to the app you pick. | Your device |
| History of messages you wrote | Stored only in the app's on-device database. You can delete entries in the app. | Your device |
| Advertising data (device identifiers, advertising ID, IP address, etc.) | May be collected by the Google AdMob SDK under Google's policies. | |
| Usage stats (app usage events, device information) | Collected automatically by the Firebase / Google Analytics SDK. Never includes your messages or card images. | Google (Firebase) |
| App config requests and push notification token | The app talks to Firebase services to receive notices and update information. | Google (Firebase) |
| Subscription purchase details | Handled by Google Play Billing. We do not receive your payment details. | Google Play |
| Connection data (IP address, User-Agent, cookies) | May be passed when the main screen connects to a Naver search page. Never includes your messages (see section 5). | Naver |
| Account information | Not collected. The app has no accounts. | — |
We do not operate a server for this app, and we do not directly collect personal information such as your name, contact details or address.
2. Card messages and images
- Card images, fonts and background music are bundled with the app. Placing your message on a card and turning it into an image or video (MP4) all happens on your device.
- The messages you type and the card images and videos you create are never sent to our servers or to ad or analytics services.
- When you share a card, the app creates the image or video in its temporary storage (cache) and hands it to the app you choose (for example, a messenger). What happens next is governed by that app's policy.
- When you tap share, the app saves the message, the time it was written and simple stats such as character count to an on-device history. You can delete entries one by one on the history screen, and the history is removed when you uninstall the app.
- If you share text from another app into SaengSaeng Card, that text is only used to fill in the card message field.
- The app does not access your photos, contacts, location, camera or microphone.
3. Ads
The app shows banner ads, app open ads, and native ads on the exit and history screens through Google AdMob (Google Mobile Ads SDK). To serve ads and prevent abuse, the ad SDK may collect and process the following under Google's policies:
- Device identifiers and the advertising ID
- IP address (which may be used to estimate the device's approximate location)
- Interactions with ads (impressions, clicks) and app usage information
- Diagnostic information (ad SDK performance and errors)
- Other items listed in the Google Mobile Ads SDK data disclosure
This data is collected and processed by Google; we do not access it directly. Please refer to Google's documentation for the exact items and purposes.
- Google Privacy Policy
- How Google uses information from sites or apps that use its services
- Google Mobile Ads SDK data disclosure
Changing your ad choices
- The current version does not show a separate ad consent screen or offer an ad settings menu inside the app.
- You can reset or delete your advertising ID in Android Settings under Google > Ads. Once deleted, the advertising ID is no longer used for personalized ads.
- On Android 13 and later, you can adjust ad-related features under Settings > Security & privacy > Ads privacy (menu names may vary by device).
- A subscription reduces ads. The Basic plan removes app open ads and pop-up ads, and the Premium plan also removes banner ads. However, the current version shows the ad on the exit screen whether or not you subscribe.
4. Usage stats, app config and notifications
The app includes the Google Firebase SDK. Your messages, card images and videos are never included in any of the features below.
- Usage stats (Firebase / Google Analytics)
- May send automatically collected events such as app opens and screen usage, together with device information (model, OS version, app version, language and region settings, etc.), an app instance ID and the advertising ID, to Google. We use this to understand how the app is used and to improve it. The current version does not offer an in-app setting to switch this off.
- App config (Firebase Remote Config)
- When the app starts, it fetches notices, FAQs and maintenance or update information. Technical information such as the Firebase installation ID and app version is sent to Google in the process.
- Push notifications (Firebase Cloud Messaging)
- Firebase creates a per-device notification token so that notifications can be delivered. We do not separately collect this token or link it to other information. On Android 13 and later, notifications are shown only if you allow them, and you can turn them off at any time in Android Settings.
5. Other internet connections
Because of code shared with an older spell-check feature, the app's main screen may connect to a Naver search page (search.naver.com) and download a web page when it opens. This request never includes the messages you type or your card contents. As with any web request, however, your IP address and device and connection details (such as the User-Agent) may be passed to Naver, and cookies set by Naver may be kept while the app is running and sent back. This is handled under the Naver Privacy Policy.
6. Subscription
- Subscriptions for benefits such as fewer ads are handled through Google Play Billing. Payment details such as your payment method, name and billing address are handled by Google Play and are not shared with us.
- The app only checks the subscription state provided by Google Play to decide whether to show ads and which benefits to apply. The subscription menu may not be shown in some versions.
- Cancellations, refunds and purchase history follow Google Play's policies and procedures. Google Play Terms of Service
7. Permissions
| Permission | Purpose |
|---|---|
| Internet, network state | Communicate with ads, Firebase services and Google Play Billing |
Google Play Billing (com.android.vending.BILLING) | Subscription purchases and subscription status checks |
Advertising ID (AD_ID), Android ad services (ACCESS_ADSERVICES_*) | Used by the Google ad and analytics SDKs for the advertising ID and ad measurement |
Show notifications (POST_NOTIFICATIONS) | Showing Firebase notifications. The app does not prompt for it; you can turn it on or off in Android Settings. |
| Install referrer, wake lock, foreground service, receive messages | Used internally by the Google ad, Firebase and AndroidX libraries |
| Read/write storage (Android 12 and earlier only) | May be declared in some versions, but the app never requests it and does not read your photos or files. |
8. Accounts
The app does not create accounts or require sign-in. Because we hold no user accounts, there is no separate account deletion feature. Data the app stores on your device is removed when you uninstall the app.
9. Purposes, retention and deletion
| Data | Purpose | Retention | How to delete |
|---|---|---|---|
| Message history (message, time written, character count, etc.) | Let you revisit and share earlier messages | Stored on your device only | Delete entries on the history screen; removed when you uninstall the app |
| Card images and videos for sharing | Hand off to the app you choose | In the app's temporary storage (cache) on your device | Uninstall the app or clear its cache in Android Settings |
| App settings (screen size, review prompt count, subscription product info, preview setting, etc.) | Keep the app working | Stored on your device. May be included in your Google account backup if you turned on Android backup, or in a device-to-device transfer when you move to a new device (message history is not included) | Deleted when you uninstall the app |
| Usage stats, app config and notification technical data | Improve the app; deliver notices and update information | According to Google's (Firebase) data retention settings | To request deletion, contact us. |
| Advertising data | Serve ads and prevent abuse | According to Google's policies | You can reset or delete your advertising ID in Android Settings. |
10. International transfer of data
We do not sell or provide personal information to third parties. However, the Google SDKs included in the app send the data below to Google servers outside Korea.
| Item | Details |
|---|---|
| Recipient | Google LLC (contact: Google privacy inquiries) |
| Destination countries | The United States and other countries where Google operates data centers |
| When and how | Sent over the network from time to time while you use the app |
| Data transferred | Device identifiers such as the advertising ID and Firebase installation ID, IP address, app usage events, device information, notification token, ad interaction data |
| Purpose | Ads, usage stats, notices and update information, notifications |
| Retention | According to Google's policies and Firebase data retention settings |
| How to refuse | You can delete your advertising ID or turn off notifications in Android Settings. If you do not want any of this data sent, please stop using and uninstall the app; the app cannot be used in that case. |
11. Your rights
You can do the following yourself or by request:
- Delete saved message history on the app's history screen
- Reset or delete your advertising ID, and turn notifications on or off, in Android Settings
- Ask us to access, delete or stop processing data sent to Google using the contact details below. We handle what we can verify without delay, and point you to Google's procedures for data that Google processes.
12. Third-party services used
| Service | Purpose | Information |
|---|---|---|
| Google AdMob (Google Mobile Ads SDK) | Ads | Google Privacy Policy |
| Firebase / Google Analytics | Usage stats | Privacy and Security in Firebase |
| Firebase Remote Config | Notices, FAQs and update information | Privacy and Security in Firebase |
| Firebase Cloud Messaging | Push notifications | Privacy and Security in Firebase |
| Google Play Billing | Subscription | Google Play Terms of Service |
| Naver search web page | Connection from code shared with an older spell-check feature (no user messages included) | Naver Privacy Policy |
13. Children's privacy
The app is not primarily directed at children under 13 (under 14 in Korea). It does not ask for age or knowingly collect children's personal information. If you believe a child's information has been sent, please contact us below and we will help delete it after checking.
14. Changes to this policy
If the way the app handles data changes, we update this page and its effective date.
15. Contact and privacy officer
For questions about data handling, or to request access or deletion, please email us.
- Developer: simpest (SugarMount)
- Privacy officer: Stephen, Jeong (simpest)
- Email: sugarmount21@gmail.com
- Google Play: SaengSaeng Card (SugarCard)
Users in Korea can also report or seek advice on privacy violations to the Personal Information Infringement Report Center (privacy.kisa.or.kr, 118 in Korea) or the Personal Information Dispute Mediation Committee (www.kopico.go.kr).
Effective date: October 4, 2026