Privacy Policy for Byeolmung

Effective date: June 20, 2026

This Privacy Policy explains how Byeolmung, also shown as 별멍, handles information when you use the iOS app, support channels, subscription features, AI-generated horoscope features, and account deletion tools.

Contact: For privacy questions, support requests, or account deletion help, email innerbuilder.co@gmail.com.

Information We Collect Or Process

Profile and astrology inputs

Byeolmung may store your selected zodiac sign, birth date, locale, notification preferences, display preferences, and app-level profile identifier. Birth date is used to derive or confirm your zodiac sign and to personalize app views. Compatibility features may store a partner profile that can include a partner name or nickname, birth date, zodiac sign, recent compatibility score, and related cache key.

Location permission and sky features

AR Sky and astronomy timing features may request device location permission so the app can calculate constellation direction, altitude, azimuth, rise timing, transit timing, and related sky context. If you do not grant location permission, the app can use a configured birth city or a general fallback where available. Byeolmung does not use location permission for advertising or cross-app tracking.

Account and sign-in data

Byeolmung uses Firebase Auth for social sign-in. Depending on the provider you choose, Firebase may process identifiers from Apple, Google, or Kakao sign-in. The app and backend may receive a Firebase user identifier, sign-in provider, ID token, and account details the provider makes available for authentication or account display. The Cloudflare backend stores an authentication mapping in D1 that links the Firebase provider identifier to the app's local user identifier.

Subscriptions and purchases

Byeolmung Pro subscriptions are purchased through Apple's StoreKit system and managed with RevenueCat. We may process product identifiers, entitlement status, trial state, purchase status, expiration dates, renewal status, and RevenueCat customer identifiers. Apple processes payment details; Byeolmung does not receive your full card number or Apple ID payment credentials.

App data stored on device and in iCloud

Byeolmung uses SwiftData for app storage. User profile, partner profile, and subscription state may sync through your private iCloud account using CloudKit when iCloud is available. Local-only data can include regenerable horoscope caches, astronomy events, and app usage metrics such as view counts or streak state. iCloud sync is controlled by Apple ID and device settings.

Backend requests and technical data

When the app calls the Cloudflare Worker backend, the request may include the route payload needed for that feature: zodiac signs, date, locale, reading layer, reading depth, optional app-level user identifier for rate limiting, Firebase ID tokens for authenticated account actions, and subscription deletion requests. Cloudflare may process IP address, headers, request timing, and security logs as part of providing the backend and protecting it from abuse.

Support messages

If you email support, we process your email address, message content, attachments you choose to send, and the facts needed to investigate your request. Avoid sending sensitive information that is not needed for support.

How We Use Information

To provide daily horoscope, detailed reading, compatibility, AR Sky, notification, and Live Activity features.
To derive zodiac and sky context from birth date, sign, locale, date, and location permission where you grant it.
To authenticate accounts with Firebase Auth and keep a server-side ownership mapping for account actions.
To manage Byeolmung Pro access through StoreKit and RevenueCat.
To cache horoscope and compatibility output, reduce repeated AI requests, and rate limit abuse.
To respond to support, privacy, and account deletion requests.
To comply with platform, security, fraud prevention, and legal obligations.

AI Horoscope Processing

Byeolmung uses AI model providers, including OpenAI and Anthropic where configured for a feature or fallback, to generate horoscope and compatibility text. Prompts are designed to use the minimum context needed, such as zodiac sign, date, locale, reading mode, compatibility sign pair, and astrology reference context. We do not intentionally send payment credentials, Firebase ID tokens, or unrelated support emails to AI model providers for horoscope generation.

The Cloudflare Worker may also consult an external astrology reference source and local zodiac element and modality frames before generating a response. AI output can be cached so repeated requests for the same sign, date, locale, and reading mode do not require a new model call.

Service Providers

We use service providers to run the app and process data for the purposes described in this policy:

Apple for iOS, StoreKit purchases, subscription management, iCloud, CloudKit Private Database, push-related platform services, and App Store distribution.
Firebase Auth for account sign-in and identity token verification.
RevenueCat for subscription entitlement management and customer deletion workflows tied to Byeolmung Pro.
Cloudflare for Workers, D1, KV caching, rate limiting, and static legal site hosting.
OpenAI and Anthropic for AI-generated horoscope and compatibility text when used by app features.
Email providers used to receive and respond to support messages sent to innerbuilder.co@gmail.com.

Storage And Retention

On-device SwiftData remains until you delete app data, delete your account inside the app, or remove it through device and iCloud controls. CloudKit-synced profile, partner, and subscription state follow your Apple iCloud behavior and deletion propagation.

Cloudflare KV horoscope cache entries for daily readings are generally short-lived, and the current app backend uses a 30-hour cache for daily horoscope keys. Compatibility cache entries may be retained longer because they are keyed by sign pair and locale rather than directly by name or payment information. D1 authentication mappings remain until account deletion or support-assisted deletion. RevenueCat customer records are controlled by RevenueCat and Apple subscription systems, and deletion requests are sent through the backend when you delete your account.

Support emails are retained for as long as needed to respond, keep a record of the request, protect the service, or meet legal obligations. We aim to remove identifying account data within 30 days after a completed account deletion request unless a longer period is required for security, fraud prevention, payment records, or legal compliance.

Account Deletion

You can start account deletion in the app from Settings when the feature is available for your signed-in account, or you can contact innerbuilder.co@gmail.com. The deletion flow is designed to:

Verify the signed-in Firebase account with a fresh Firebase ID token.
Delete the Cloudflare D1 authentication mapping for the server-resolved app identifier.
Request deletion of the matching RevenueCat customer record for the server-resolved app identifier.
Delete SwiftData app entities on device so iCloud can propagate deletion where CloudKit sync applies.
Clear app-specific local defaults and return the app to a fresh state.

Deleting your Byeolmung account does not cancel an active Apple subscription by itself. Apple manages subscriptions, renewals, cancellations, and refunds through your Apple ID. You can cancel in iOS Settings or the App Store subscription management screen.

Your Choices

You can deny location permission or later change it in iOS Settings.
You can manage iCloud sync through Apple ID and iCloud settings.
You can cancel subscriptions through Apple subscription settings.
You can request account deletion or privacy help at innerbuilder.co@gmail.com.

Children

Byeolmung is not designed for children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child provided personal information through the app or support channel, contact us so we can review and delete it where required.

Security

We use platform security controls, Firebase token verification, Cloudflare security features, and Apple account protections to help protect the service. No internet or device storage system is perfectly secure, so please use a protected device, keep your Apple ID secure, and contact support if you suspect unauthorized access.

International Processing

The providers listed above may process information in countries other than your country of residence. Where required, we rely on the safeguards provided by those processors, platform terms, and applicable law.

Changes To This Policy

We may update this Privacy Policy as Byeolmung changes. The effective date at the top shows when this version became active. Material changes will be reflected in the app, on this site, or through another reasonable notice channel.