ELIM Kids (the “Service”) provides illustrated Bible stories and prayer content for children and their parents or guardians.
The operator of ELIM Kids (the “Operator”) values your personal information and complies with applicable laws, including the Personal Information Protection Act of the Republic of Korea.
This Privacy Policy explains what personal information is processed when you use the Service, why it is processed, how long it is retained, and your rights in relation to that information.
1. Purposes of Processing Personal Information
The Operator may process personal information to the extent necessary for the following purposes:
- Providing and operating the Service
- Providing illustrated Bible stories and prayer content
- Verifying access rights to content
- Maintaining reading progress and settings on your device
- Preventing duplicate processing of reading events and generating book popularity statistics
- Managing subscriptions and payments
- Verifying subscription purchases made through the Apple App Store and Google Play
- Checking premium subscription status
- Handling subscription renewals, cancellations, expiration, and purchase restoration
- Preventing fraudulent payments and duplicate processing
- Responding to inquiries and providing customer support
- Handling inquiries about errors and payments
- Providing information about use of the Service
- Handling user requests and disputes
- Analyzing and improving app usage
- Analyzing app launches, sessions and screen usage through Google Analytics for Firebase
- Improving usability and the Service
- Maintaining service reliability
- Preventing misuse of the Service
- Investigating system errors and security issues
- Responding to service disruptions
The Operator does not use personal information for purposes other than those stated above. If a processing purpose changes, the Operator will take the measures required by applicable law.
2. Personal Information We Process
The following information may be processed depending on how you use the Service:
| Category | Information that may be processed | Purpose |
|---|---|---|
| Subscription payments | Store platform, product ID, purchase token or transaction ID, subscription status, and expiration time | Maintaining an on-device queue of purchases awaiting verification, verifying payments through the stores, and restoring purchases |
| On-device usage information | Reading progress and resume position, saved books, app settings, and selected avatar | Maintaining your reading experience and settings |
| Raw reading-event records on the server | App installation UUID, reading session UUID, book ID, reading start and completion times, and active reading time | Preventing duplicate processing of reading events and generating book popularity statistics |
| App feedback and story reports | Feedback or report content, the book, page and language when reporting a story, and an optional email address for a reply | Reviewing feedback to improve the Service, checking content errors, and responding to inquiries |
| App usage analytics | App instance ID, app and device information, approximate location derived from masked IP addresses, app launches, sessions, screen views, and purchase and subscription event information that may be processed automatically (see Section 11) | Analyzing app usage and improving usability and the Service |
| Technical information | Server request logs and error logs | Responding to service issues and maintaining security |
The Service does not currently create separate parent login accounts or email-based accounts. The Operator seeks to avoid collecting personal information that is unnecessary to provide the Service.
When payments are made through Apple or Google, payment details such as credit card numbers and expiration dates are processed by the relevant payment platform. The Operator does not directly collect or store those details.
We have not identified a feature in the current app that allows individual users to write and save their own prayer records. Prayer content provided by the app is distinct from records created by users.
Reading progress and saved books are stored on your device. The reading start and completion event information listed above is sent to the server. App installation UUIDs and reading session UUIDs are not directly linked to a user’s name or login account. However, these identifiers distinguish reading events, so this does not mean that no personal information is processed.
Purchase evidence is transmitted to Apple or Google services for verification.
3. Protecting Children Under 14
ELIM Kids is designed for children, and protecting children’s personal information is important to us.
The Operator does not ask children to provide unnecessary information such as their name, telephone number, address, photographs, or precise location.
Where a legal representative’s consent is required to collect or use the personal information of a child under 14, the Operator obtains that consent and carries out the necessary verification procedures in accordance with applicable law.
A parental verification step is included in the subscription purchase flow. Separate parent account management is not currently available.
Parents or guardians may request access to, correction or deletion of, or suspension of the processing of their child’s personal information.
4. Retention of Personal Information
The Operator deletes or destroys personal information without undue delay once the purpose of processing has been fulfilled or the retention period has expired. Information that must be retained under applicable law is kept for the period required by that law.
The following retention criteria apply:
| Information | Retention criteria |
|---|---|
| Subscription and purchase verification information | For as long as needed to manage subscriptions, restore purchases, and handle disputes, and for any legally required retention period |
| On-device reading progress and settings | Until you use the relevant reset function in the app or delete the app’s data |
| Raw reading-event records on the server | 30 days from the date the records are stored on the server. Records older than 30 days are aggregated into cumulative completion counts by book and then deleted during the next successful daily aggregation job. |
| Aggregated book statistics | Cumulative completion counts that do not contain UUIDs are retained long term as book popularity statistics. The number of installations that completed a book and repeat-reading metrics for the most recent 30 days are calculated only from raw records within that period. |
| App feedback and story report records | Feedback or report content, information identifying the reported story, and any optional reply email address are retained for one year from submission and then deleted. |
| Service error and security logs | For the minimum period necessary to fulfill their purpose |
Raw records containing UUIDs are managed separately from aggregated book statistics that do not contain UUIDs. If a daily aggregation job does not run or fails, deletion of the raw records may be delayed until the next successful run.
Providing an email address is optional; feedback and story reports can be submitted without one. Without an email address, we may be unable to send you an individual email reply. Specific retention periods for service request logs will be reflected in this Policy once the relevant operational policies have been confirmed.
6. Outsourced Processing
The Operator may use external service providers for certain tasks necessary to provide the Service, such as cloud hosting, data storage, and payment verification.
Where personal information processing is outsourced, the Operator manages and supervises the service providers and discloses their identities and the scope of their work as required by applicable law.
The Operator manages the outsourcing status and processing scope of the cloud, database, authentication, and customer support services actually used in its operating environment.
7. International Transfers
If the Service uses overseas cloud infrastructure or service providers located abroad, personal information may be processed or stored outside the Republic of Korea.
Where an international transfer occurs, the Operator provides information about the recipient, destination country, categories of information, purpose, timing and method of transfer, and retention period, and takes the measures required by applicable law.
8. Deletion and Destruction Procedures
The Operator deletes or destroys personal information without undue delay when it is no longer needed, including when its retention period expires or the purpose of processing has been fulfilled.
Personal information in electronic files is deleted in a manner that prevents recovery or reconstruction. Any paper records containing personal information are shredded or incinerated.
If retention is required by law, the relevant information is kept separately and destroyed when the legally required retention period ends.
9. Rights of Users and Legal Representatives
Users and their legal representatives may exercise the following rights as provided by applicable law:
- Request access to personal information
- Request correction or deletion of personal information
- Request suspension of the processing of personal information
- Withdraw consent in accordance with applicable law
- Request deletion of personal information, including reading records stored on the server
On-device reading progress and settings can be managed using the app’s reset functions. Requests relating to personal information, including reading records stored on the server, may be submitted to the email address below.
The Operator handles requests after verifying the identity of the user or their legal representative in accordance with applicable law.
Requesting deletion of server reading records and other personal information
How to reset app data and request deletion of server reading records (Korean) →
Uninstalling the app may not delete all information stored on the Operator’s servers. Store subscriptions must be managed separately from uninstalling the app.
10. Security Safeguards
The Operator applies the following safeguards to protect personal information:
- Limiting access to personal information to those who need it
- Securely managing server credentials and secret keys used for payment verification
- Using appropriate encryption for network communications
- Verifying payment information and access rights
- Protecting against unauthorized access and abnormal requests
- Performing security reviews and system maintenance as needed
The Operator continually reviews and improves its technical and organizational safeguards.
11. Advertising and Analytics Services
App usage analytics: Google Analytics for Firebase
The Android and iOS apps use Google Analytics for Firebase (GA4), provided by Google, to analyze app usage and improve usability and the Service. Analytics information is transmitted to Google for external processing.
Information that may be processed includes an app instance ID; app and device information such as app version, operating system and device model; approximate location derived from masked IP addresses; and usage events such as app launches, sessions and screen views. The SDK may also automatically process purchase and subscription events and parameters such as product ID, product name and price.
Screen names sent by the Operator for screen-view measurement are fixed values defined by the developer, such as home, settings, feedback and book_pages. The information processed is not limited to screen names.
The Operator does not set a separate Analytics User-ID or directly include email addresses, feedback content, partnership codes, prayer content or raw receipts in Analytics events. Even without a separate User-ID, usage events may be linked through identifiers such as the app instance ID. This does not mean that analytics information is completely anonymous or that no personal information is processed.
Advertising ID collection, iOS IDFV collection and ad personalization are disabled for Analytics, and advertising-related consent values are set to denied. These settings apply to Analytics and do not mean that collection or processing by other SDKs, such as AdMob, is controlled by these settings.
Users or their legal representatives may contact help@sion-software.com with questions about analytics processing or requests to stop collection or delete information. The app currently has no feature for turning off Analytics collection or viewing and sharing the app instance ID. Functions and procedures for the Operator to delete individual Analytics data using that ID have not been implemented or verified. An email inquiry alone therefore does not guarantee that Analytics collection for a particular user can be stopped or that their existing data can be deleted.
Official information: Android SDK data disclosures, iOS SDK data disclosures, and Analytics SDK policy.
Advertising SDKs and speech recognition
Advertising display functionality is currently disabled in the app’s code. However, advertising SDKs and advertising ID permissions are included, so the SDK behavior in the actual release build and the privacy disclosures in the app stores still need to be verified.
The pronunciation practice feature uses the device’s speech recognition functionality. The scope of processing by the speech recognition service provider may vary depending on the device and operating system settings. The Operator will provide information after reviewing the release environment.
We have not identified a feature in the current app code that uploads audio recordings to the Operator’s servers.
12. Privacy Contact
Please use the following contact details for privacy inquiries and requests to exercise your rights:
- Service: ELIM Kids
- Operator: Sion Software (시온소프트웨어)
- Privacy Officer: Seongman Kim (김성만)
- Email: help@sion-software.com
Users may also contact the Personal Information Infringement Report Center, the Personal Information Dispute Mediation Committee, or other relevant authorities for advice and redress concerning privacy infringements.
13. Changes to This Policy
This Policy may be updated to reflect changes in applicable law, the Service, or the way personal information is processed.
If material changes are made, the Operator will notify users through the Service or provide a separate notice in the manner and within the time required by applicable law.
Effective date: October 30, 2026