Privacy Policy · 개인정보 처리방침
Sowonkong Privacy Policy
This policy is written in Korean and translated into English. In the event of any discrepancy between the two versions, the Korean version prevails. Menus and buttons are named as they appear on the app's English screens.
At a glance
- There is no sign-up or login, and the operator runs no server that receives information from the app.
- Your child's name, birthday, photos, wishes and notes are stored on your device and are not sent to the operator. However, if iCloud Backup or Google backup is turned on for the device, the operating system may back up this information to your account storage (4.4).
- The app shows Google AdMob ads. To serve ads, Google processes the advertising identifier, an approximate location estimated from the IP address, ad interactions and diagnostic information. The app does not request personalized ads.
- The app uses Google Analytics to see usage statistics and Firebase Crashlytics (crash reporting) to find and fix errors. Google processes a random identifier created for each installation of the app, usage records, error records, and app and device information. The content of your records, such as wish names, photos, notes and your child's name, is not sent, and both are turned off while Kid Mode is on (4.6, 4.7).
- The app sends this information off the device only when you yourself tap to export a backup file, search a shop, or open a saved link.
- Notifications are scheduled on the device and do not pass through any external server.
1. General
Appcellent (the “operator”) operates the mobile app “Sowonkong” (the “app”). The operator complies with the Korean Personal Information Protection Act and other applicable laws, and publishes this policy to explain what information is stored where while you use the app, and what leaves the device. This policy applies equally to the iOS app and the Android app.
The app is a tool that helps parents (guardians) save, as a photo or a short note, the things their child wants, and choose together when it is time for a gift.
2. Personal information processed by the operator
2.1 While you use the app
While you use the app, the operator does not receive your name or contact details or the records you save in the app.
- There is no sign-up or login function.
- There is no server to which the app sends records for the operator.
However, the Google AdMob ads SDK, the Google Analytics SDK and the Firebase Crashlytics (crash reporting) SDK included in the app send information to Google (4.1, 4.6, 4.7). In AdMob, the operator can see only aggregate statistics that cannot identify individuals (such as ad impressions and revenue); in Google Analytics, the operator sees app usage statistics; and in Firebase Crashlytics, error records. These statistics and error records do not contain names, contact details or the records you save in the app.
2.2 When you contact us
| Item | Details |
|---|---|
| Items | Your e-mail address, and the message and any attachments you send |
| Purpose | Reviewing and answering your inquiry |
| Retention period | Destroyed without delay once one year has passed after we finish answering. If a law requires us to keep it, we keep it for the period that law requires. |
You do not need to send your child's photo or real name when you contact us.
3. Information stored on your device
The information below is what you enter or choose in the app yourself, and it is stored in the storage space that the operating system keeps separately for each app. It is not sent to the operator, and the operator cannot access it. The app does not on its own send this information off the device. However, category values made of predefined words, such as how a wish was added, who picked it and what day the gift is for, are sent to Google as usage statistics (4.6). Text you write is not sent. The other cases in which information may leave the device are when you export a backup file (4.2), when you search a shop or open a saved link (4.3; only the wish name or the saved address), and when the device's operating-system backup is turned on (4.4).
| Category | Details | Where it is stored |
|---|---|---|
| Pouch | Name (usually your child's name), color, birthday (optional) | The app's own database |
| Wish | Name, date added, note, “Wants it again” records, where it was seen, price, link, tags, date picked, who picked it, gift day, date granted, one-line review, reaction | The app's own database |
| Photos | Wish photos and review photos (taken with the camera or chosen from the album) | The app's own photo folder (only the file name is kept in the database) |
| Settings | Reminder time, whether gift day reminders are on, Keep adding, the last pouch you chose, and so on | The device's settings storage |
Photo metadata: A photo chosen from the album may contain information inside the file, such as the date it was taken or the location where it was taken (GPS). On the device, the app reads only the date taken, to suggest it as the “date added”; it does not read the location, and it does not send this information off the device. However, because this information is stored on the device together with the photo file, it may be included as is in a backup file (4.2) and in the operating system's device backup (4.4). To keep the location from being recorded, turn off location tags in the device's camera settings, or choose photos from which the location has been removed.
4. When information leaves the device
Within the app, only the ads SDK (4.1), the Google Analytics SDK (4.6) and the Firebase Crashlytics SDK (4.7) use the internet connection. The fonts on the screens are built into the app and are not downloaded while it runs. 4.2 and 4.3 cover cases in which you yourself tap to hand something over to another app or the browser, and 4.4 is a function of the operating system.
4.1 Advertising (Google AdMob)
The app includes an ads SDK provided by Google LLC (Google Mobile Ads SDK). To show and measure ads, this SDK automatically sends the information below to Google, over an encrypted connection (TLS).
| Item | Details |
|---|---|
| Processed by | Google LLC |
| Items |
|
| Purpose | Serving ads, measuring and analyzing ad performance, and preventing invalid clicks and fraud, and security |
| When and how | The ads SDK is prepared (initialized) when the app starts, and from then on it may communicate with Google regardless of how many wishes you have saved or whether Kid Mode is on. Ads are shown after you have saved 6 or more wishes, one per screen on two parent screens (Wish Box and Picked), and the information above is sent when an ad is loaded. No ads are requested on Kid Mode screens. |
| Personalized ads | The app attaches a “non-personalized ads” signal to every ad request and limits ad content to the all-ages (G) rating. According to Google, non-personalized ads may still use the advertising identifier for frequency capping, aggregate reporting and fraud prevention. |
| Retention period | As set out in Google's Privacy Policy. The operator does not receive or keep this information. |
| Learn more | Google Privacy Policy, How Google uses information from sites or apps that use its services |
How to control the advertising identifier is described in section 6. If you do not want the ads SDK to process information, you can delete the app. There is no function in the app to turn off ads alone.
4.2 Exporting a backup file (only when you do it yourself)
When you tap “Export backup file” in Settings, the app puts the pouch, wish and tag records you have not deleted (the information in section 3 except settings) and their photos into a single zip file, and opens the device's share sheet. Records and photos of wishes, pouches and tags you have deleted in the app are not included in the backup file. The file goes only to the place you choose (for example, a messenger, a cloud drive or e-mail), and what happens to it after that is governed by that service's policy. The operator does not receive this file.
The backup file is an unencrypted zip file and may contain your child's photos and name, so do not share it with others, and keep it in a safe place. “Import backup file” reads the zip file you choose on the device and merges it into the records on this device (records that exist in both are replaced with the content of the backup file); it does not send that file anywhere else.
4.3 Searching a shop and opening a saved link (only when you do it yourself)
When you tap a row that searches a shop under a wish's “Where to buy?”, such as “Search on Coupang” or “Search on Naver Shopping”, the app opens an address with the wish name as the search term in the device's browser or in that shop's app. The shops shown depend on the device region: Coupang and Naver Shopping in Korea, Amazon and Rakuten (楽天市場) in Japan, and Google Shopping and Amazon in all other regions. The search term and connection information are then passed to the company that runs that shop (Coupang, Naver, Amazon, Rakuten or Google) and processed under that company's privacy policy. When you tap “Open saved link” or the link on a wish screen, the app opens the address you saved (http and https addresses only) in the device's browser or in the corresponding app.
Device region and screen language: The device region is the country (region) code contained in the device's language settings. The app uses this value on the device only to choose which shops to show; it does not separately collect or send it for this purpose, and it does not use the IP address or location information. The language of the app's screens also follows the device's system language, and no information is separately collected for this. The device language that the Google Analytics SDK sends automatically is described in 4.6.
Search links and saved links are ordinary links, and the operator receives no compensation for them. All shopping links shown outside Korea are also ordinary links. However, “Open Coupang home” under “Where to buy?”, shown in Korea, is a Coupang Partners link. As part of the Coupang Partners program, this app receives a certain commission from it. This link is a fixed address issued by Coupang, and the app sends no records with it, such as the wish name, photos or information about your child. Connection information after the link is opened, and whether a purchase is made, are processed by Coupang under its own privacy policy; the operator cannot know who bought what, and receives only combined results.
The app sends nothing before you tap, and in Kid Mode it does not open shop searches. The fact that you tapped a shopping link (only which row you tapped and whether it was an affiliate link) is recorded in the usage statistics (4.6). The wish name, the search term and the saved link address are not included in the usage statistics.
4.4 Device backup (an operating-system function)
The app only stores records and photos on the device, but if the operating system's backup function is turned on, that data may be copied to your Apple or Google account storage or to a computer. Because an operating-system backup contains the app's database file as it is, text records that are only marked “deleted” in the app (section 8) may also be included.
iPhone and iPad: If iCloud Backup or computer backup (Finder or iTunes) is turned on, iOS may include this app's data (records, photos, settings) in the backup, and the data may be moved along when you move your data to a new device. This is a function between Apple and you, and the operator cannot access that backup.
Android: If Google backup is turned on for the device, Android may automatically back up this app's data (records, photos, settings) to your Google account storage (Google Drive), and it may be restored when you set up a new device with the same account. It may also be moved along when you move to a new device directly (device-to-device transfer). This is a function between Google and you, and the operator cannot access that backup. You can turn it off in the backup menu of the device settings.
4.5 Notifications
Review reminders and advance reminders of gift days (birthday, Children's Day, Christmas) are scheduled on the device and do not pass through an operator server or a push server. The notification text contains the wish name or the pouch name, and whether it is shown on the lock screen depends on the device's notification settings. Tapping a notification opens the corresponding screen in the app; a notification tapped during Kid Mode opens after the parent leaves Kid Mode (section 7).
4.6 Usage statistics (Google Analytics)
The app includes the Google Analytics (Google Analytics for Firebase) SDK provided by Google LLC. The operator uses this tool to see which features are used and how much, and the SDK automatically sends the information below to Google. It is sent over an encrypted connection (TLS).
| Item | Details |
|---|---|
| Processed by | Google LLC |
| Items |
|
| Not sent | Wish names, photos, tags, notes, child and pouch names, saved link addresses, search terms |
| Purpose | Analyzing app usage statistics |
| Advertising identifier | Google Analytics does not use the advertising ID (the Android advertising ID or the iOS advertising identifier), and usage statistics are not used as signals for ad personalization either. |
| Kid Mode | Collection of usage statistics is turned off while Kid Mode is on. |
| Retention period | Kept for the period set in Google Analytics' data retention settings and then deleted (Google Analytics data retention). |
| How to opt out | There is no function in the app to turn off usage statistics alone. Collection stops when you delete the app. |
| Learn more | Google Privacy Policy, How Google uses information from sites or apps that use its services |
4.7 Crash reporting (Firebase Crashlytics)
The app includes the Firebase Crashlytics SDK, a crash reporting tool provided by Google LLC. When the app stops or an unhandled error occurs, the SDK automatically sends the information below to Google, over an encrypted connection (TLS). The operator uses these records to find and fix errors.
| Item | Details |
|---|---|
| Processed by | Google LLC |
| Items |
|
| Not sent | Wish names, photos, tags, child names, saved link addresses, search terms |
| Purpose | Finding and fixing errors |
| When | When the app stops or an unhandled error occurs |
| Advertising identifier | The advertising ID (the Android advertising ID or the iOS advertising identifier) is not used. |
| Kid Mode | While Kid Mode is on, crash reporting is turned off together with usage statistics. |
| Retention period | According to Google, crash records and their associated identifiers are kept for 90 days (Privacy and Security in Firebase). |
| How to opt out | There is no function in the app to turn off crash reporting alone. Sending stops when you delete the app. |
| Learn more | Google Privacy Policy, Privacy and Security in Firebase |
5. Provision to third parties, outsourcing of processing, and transfer abroad
The only information the operator receives and keeps directly is e-mail inquiries. Where inquiry e-mails are kept is described in section 13.
Apart from that, information is transferred to Google outside Korea, as shown below, through the ads SDK of 4.1, the Google Analytics SDK of 4.6 and the Firebase Crashlytics SDK of 4.7.
| Item | Advertising (Google AdMob) | Usage statistics (Google Analytics) | Crash reporting (Firebase Crashlytics) |
|---|---|---|---|
| Recipient | Google LLC | Google LLC | Google LLC |
| Countries of transfer | The USA and other countries in which Google operates data centers | The USA and other countries in which Google operates data centers | The USA and other countries in which Google operates data centers |
| Contact | The contact options given in the Google Privacy Policy | The contact options given in the Google Privacy Policy | The contact options given in the Google Privacy Policy |
| Items transferred | Device identifiers, IP address and approximate location, ad interactions, diagnostic information and so on (the items in 4.1) | App instance ID, usage records, app and device information and approximate region, and the category values of the four in-app actions (the items in 4.6) | Where the error occurred (stack trace), device type, operating-system version and app version, time of the error, installation identifier (the items in 4.7) |
| Timing and method of transfer | Sent encrypted over the network when the ads SDK is initialized while the app runs, or when an ad is loaded | Sent encrypted over the network while you use the app (except while Kid Mode is on) | Sent encrypted over the network when the app stops or an unhandled error occurs (except while Kid Mode is on) |
| Purpose of use | Serving ads, measuring and analyzing ad performance, and fraud prevention and security | Analyzing app usage statistics | Finding and fixing errors |
| Retention and use period | As set out in Google's Privacy Policy | As set in Google Analytics' data retention settings (4.6) | 90 days (4.7) |
| How to refuse, and its effect | Sending stops when you delete the app. The Android advertising ID can be reset or deleted as described in section 6, and the app's other features still work if you do so. | Sending stops when you delete the app. There is no function in the app to turn off usage statistics alone. | Sending stops when you delete the app. There is no function in the app to turn off crash reporting alone. |
6. Processing of behavioral information (advertising)
The app does not request ads tailored to your interests (personalized ads). However, as described in 4.1, the ads SDK processes ad interactions and device identifiers, so we explain this below.
- Items, method, purpose and retention period: As in 4.1.
- Controlling it on Android: In the device settings, under the Privacy (or Google) menu › Ads, you can reset or delete the advertising ID. Menu names may differ by device.
- iPhone and iPad: The app does not ask for permission to track, so the advertising identifier (IDFA) is not provided. You can also block apps from asking to track in Settings › Privacy & Security › Tracking.
- The app does not request ads in Kid Mode, and it does not show personalized ads aimed at children under 14.
- Google Analytics (4.6) and Firebase Crashlytics (4.7) do not use the advertising ID, and usage statistics are not used for ad personalization.
7. Information about children under 14
- The app is made for guardians (parents) to use and is not designed for children.
- Guardians may enter their child's name, birthday, photos and wishes themselves. As described in section 3, this information is stored on your device and is not sent to the operator. If iCloud or Google backup is turned on for the device, the operating system may back up this information to your account storage (4.4).
- The operator does not collect personal information directly from children under 14.
- “Kid Mode” is a full-screen mode that a guardian turns on on their own device. In Kid Mode, no ads are requested, there are no outside links or purchases, and going back is blocked. To leave, press and hold the lock in the upper right for 2 seconds. On a device with a screen reader turned on, you leave by long-pressing the lock and then going through a confirmation dialog.
- If a notification is tapped during Kid Mode, the Kid Mode screen stays as it is, and the corresponding screen opens after the guardian leaves Kid Mode. Kid Mode also does not ask for notification permission.
- Because the ads SDK is already prepared when the app starts (4.1), it may communicate with Google even during Kid Mode. However, no ads are requested or shown on Kid Mode screens.
- Ads are shown only on two parent screens, in a non-personalized way, and only with the all-ages (G) rating.
- While Kid Mode is on, Google Analytics' collection of usage statistics and Firebase Crashlytics' crash reporting are turned off (4.6, 4.7).
- Please take care when sharing a backup file that contains your child's photos or name with others.
8. Retention period and destruction
8.1 Information on the device
- It is kept on the device until you delete it.
- When you delete a wish in the app, it disappears from the screen and that wish's photo files are deleted (files that could not be deleted right away are cleaned up the next time you open the app, starting with those more than a day old).
- Text records such as wish names, notes, pouch names and birthdays remain in the database on the device, marked “deleted”, in preparation for a future feature for using the app on several devices together. These records are not shown on the screen and are not included in backup files (4.2), but they may be included, together with the database, in the operating system's device backup (4.4). The operator cannot access these records either.
- The zip file created when you export a backup file remains in the app's temporary folder and is deleted the next time you export (if the file is more than 1 hour old) or when the operating system cleans up temporary files.
- To delete all records completely, delete the app. On Android, you can also delete them in the device settings under App info › Storage › Clear data.
- Backup files you have already exported and operating-system backups (4.4) remain even if you delete the app, so you need to delete them separately where they are.
8.2 Information kept by the operator
Inquiry e-mails are deleted without delay, in a way that cannot be recovered, once the retention period in 2.2 has passed.
8.3 Information processed by Google
Information sent by the ads SDK is kept for the period set out in Google's Privacy Policy and then destroyed. Usage statistics are kept for the period set in Google Analytics' data retention settings and then deleted (4.6). According to Google, crash records are kept for 90 days (4.7).
9. Rights of users and legal representatives
- Information on the device: You can view, correct and delete it yourself in the app at any time (editing and deleting wishes and pouches, changing settings). How to delete everything is described in section 8.
- Information kept by the operator (inquiry e-mails): You may request access, correction, deletion or suspension of processing at the contact in section 13; the operator will act without delay and let you know the result. An agent, or the legal representative of a child under 14, may also make such a request.
- Information processed by Google: You can exercise your rights by the means Google provides (the advertising ID settings in section 6, and the guidance in Google's Privacy Policy). Collection of usage statistics and crash reporting stop when you delete the app (4.6, 4.7).
10. App permissions
All the permissions the app uses are optional. If you do not allow one, only that feature cannot be used; the other features work as usual.
| Permission | Used for | Notes |
|---|---|---|
| Camera (optional) | Taking wish and review photos | Requested on iOS. On Android, the app opens the device's camera app and receives only the photo taken. |
| Photos (optional) | Choosing wish and review photos from the album | On iOS, the app may request access to the photo library. On Android, it receives only the photos you choose in the system photo picker. |
| Notifications (optional) | Review reminders, advance reminders of gift days | Requested on iOS and on Android 13 or later. The app requests it when, after you create your first pouch, it asks you in the app first and you choose “Get reminders”; when you pick a wish (if it has not asked yet); and when you turn on notifications in Settings. It is not requested in Kid Mode. |
You can change permissions you have allowed at any time in the app permissions menu of the device settings. Importing a backup reads only the file you choose in the system file picker.
11. Security measures
- The app's records and photos are stored in the storage space that the operating system keeps separately for each app, so other apps cannot read them.
- In case you lose the device, we recommend turning on the device lock (passcode, biometric authentication).
- Backup files are not encrypted, so please take care where you keep them and whom you share them with (4.2).
- Data sent by the ads SDK, the Google Analytics SDK and the Firebase Crashlytics SDK is sent over an encrypted connection (TLS).
- The operator keeps inquiry e-mails in an e-mail account that only the operator can access.
12. Automatic collection tools
The app does not use cookies. The ads SDK's use of the advertising identifier is described in 4.1 and section 6, Google Analytics' use of the app instance ID in 4.6, and Firebase Crashlytics' use of the installation identifier in 4.7. The website on which this policy is published (appcellent.dev) is served through Cloudflare, and the connection information and visit statistics processed when you view the page are described in the site privacy policy.
13. Privacy officer and contact
| Item | Details |
|---|---|
| Privacy officer | Appcellent |
| Contact | appcellent.dev@gmail.com |
Requests for access to personal information, inquiries and complaints are received at the contact above. Inquiry e-mails are kept in Google's Gmail (Google LLC, USA).
14. Remedies for infringement of rights
If you need advice or a remedy for an infringement of your personal information, you can contact the following Korean bodies.
- Personal Information Dispute Mediation Committee: 1833-6972 (in Korea, no area code), www.kopico.go.kr
- Privacy Infringement Report Center (Korea Internet & Security Agency, KISA): 118 (in Korea, no area code), privacy.kisa.or.kr
- Supreme Prosecutors' Office: 1301 (in Korea, no area code), www.spo.go.kr
- Korean National Police Agency: 182 (in Korea, no area code), ecrm.police.go.kr
15. Changes to this policy
If the information the app processes changes (for example, if a family-sharing server, affiliate shopping links that pass on search terms, or another way of advertising is introduced), we will revise this policy and announce the changes and their effective date on this page and in the app update notes.
In addition, the app does not process sensitive information or pseudonymized information, and it does not process biometric information, such as recognizing faces in photos, or make automated decisions.
| Version | Effective date | Changes |
|---|---|---|
| 1.0 | 2026-11-11 | First version |
| 1.1 | 2026-11-11 | Google Analytics usage statistics added |
| 1.2 | 2026-11-11 | Crash reporting (Firebase Crashlytics) added; three in-app actions added to usage statistics |
| 1.3 | 2026-11-12 | The shops under “Where to buy?” now depend on the device region (Japan: Amazon and Rakuten; other regions: Google Shopping and Amazon; all ordinary links); explanation of the device region and screen language added; English version published; the “7 days before” period removed from the notice of changes (section 15) |