Data the App processes
Birth-chart calculation uses your date of birth, solar or lunar calendar, gender, and optional birth time and place. If you choose to save a profile, its name and original inputs are kept in App storage. These original inputs are not sent to the Seori Labs reading server or Firebase. Depending on operating-system settings, copies of App data may be backed up or restored.
Android v1.4.0 does not require a name, email address or linked account. For content requests, it processes pseudonymous user identifiers, authentication tokens and session information generated by Firebase and the Seori Labs Platform.
To provide plain-language readings, the App sends derived chart facts calculated on your device and content requests to the Seori Labs Platform. These facts include classifications for the five elements, ten gods, decade, annual and monthly flows. These requests do not include original profile names, dates of birth, birth times or birth places.
To protect the service and diagnose failures, the App may process Firebase App Check app/device-integrity signals and minimal request metadata and server diagnostic logs, such as request time, response status, and a pseudonymous user identifier.
Android v1.4.0 provides ads on entry to readings and optional rewarded ads for additional readings. It does not offer ticket purchases or account-linking screens. If you used purchase features in an earlier version, market-issued purchase tokens, order identifiers, pseudonymous account references and entitlement records may be processed for verification, restoration, fraud prevention and legal obligations. The relevant market processes payment-instrument details; Seori Labs does not receive card numbers.
Account-linking providers in earlier versions include Kakao on Android, Kakao or Apple on iOS, and Toss Login in AppsInToss. If you used these features, authorization codes and provider account identifiers may be processed for authentication and entitlement verification, with account references pseudonymized. The absence of current purchase features does not mean that all earlier records have been deleted.
Google AdMob in native apps may process IP addresses, approximate location, permitted device or advertising identifiers, ad interactions and diagnostic information when requesting and displaying ads. Requesting non-personalized ads does not stop all advertising-SDK data processing. An ad privacy (UMP) screen is shown according to regional and provider requirements. Android v1.4.0 provides an Ad privacy option in Settings when the provider requires that option to be available. AppsInToss ads use Toss advertising functionality and policies.
When usage analytics is enabled, Google Analytics for Firebase processes events such as launches, sessions and reading use, pseudonymous installation or browser identifiers, app and device information, and approximate region. The Seori Labs Platform also processes App usage events and pseudonymous identifiers. Native SDKs may measure purchased products, prices, currencies, quantities and advertising events in versions with those features. GA4 events exclude original birth inputs, names, derived charts, login-account IDs and feedback answers.
Android v1.4.0 keeps usage analytics off before your first choice. You can allow or decline it and turn future collection on or off in Settings. The App stores your choice, notice version, language and choice time. Events from periods when analytics is off are not stored for later transmission. Withdrawal stops future analytics collection; it does not delete earlier server records. Earlier versions and other markets may lack this choice screen and enable analytics by default. GA4 advertising-ID collection and ad personalization are disabled, and ad privacy choices are managed separately.
Android v1.4.1 opens Home without a separate usage-analytics screen and preserves your earlier on or off choice. For installations without a saved choice, analytics starts on only when a fresh result from the existing privacy SDK confirms that consent and a separate privacy-options entry are not required and the region is outside GDPR applicability. Analytics stays off if consent is required or the region cannot be confirmed. You can turn it on or off in Settings. Default activation is not saved as a record of user consent. Events during the region check or while analytics is off are not retained for later transmission.
The birth place is a place you enter, not a reading of your current GPS location. The App does not request access to device location, contacts, photo or video libraries, microphone or health information. If you choose to share, the generated image or text may be sent to the app or recipient you select.