개인정보 처리방침 / Privacy Policy

• Account information: account identifier from Apple or Google sign-in, email if provided, display name, and nickname
• Mock trading sync data: account, orders, fills, holdings, positions, chart drawings, and in-app trading settings
• Reward status: check-in dates, streak count, login bonus, and ad reward claim status
• App settings: theme, tutorial completion, briefing unlock status, and briefing notification settings
• Ad and consent information: Google Mobile Ads, User Messaging Platform, iOS AppTrackingTransparency status, Android advertising ID, and ad personalization settings
• App interaction data: launch, reward, and mock trading action counts used to determine review request conditions
• On-device diagnostic logs: app navigation, refreshes, login results, reward/mock trading processing results, error and crash clues, hashed diagnostic installation ID, and session ID
• Server access logs: general access logs for service security, error handling, and abuse prevention

Diagnostic logs are stored on the device in a rotating structure up to 10MB and are designed to exclude auth tokens, advertising IDs, raw email addresses, raw account identifiers, raw installation identifiers, full account data, and full raw server responses.

• Real exchange account information
• Real investment account balances or real order permissions
• Government-issued unique identifiers
• Precise location based on location permissions

• Provide app features, account sign-in, and mock trading sync across devices
• Prevent duplicate rewards and process account deletion requests
• Show ads, manage ad consent, and reflect iOS tracking permission status
• Provide briefing release notifications
• Generate user-requested diagnostic logs and support error analysis
• Maintain service security, handle incidents, and prevent abuse
• Generate AI briefings from public market data

• Cloudflare: API hosting, storage, cache, and security logs
• Google Mobile Ads and UMP: ads and consent management
• Apple and Google: sign-in authentication
• OpenAI or AI relay: AI briefing generation based on public market data
• CoinGecko, Binance, Alternative.me, Frankfurter: market data and indicators
• StoreKit or Play Billing: purchase and restore processing in versions that expose an ad removal pass

AI briefings are designed not to receive personal identifiers or personal mock trading history.

On-device diagnostic logs are not automatically uploaded to external servers and are sent outside the device only when the user generates a log file and chooses a destination from the share sheet.

The app may use Google Mobile Ads to display ads. To serve ads, limit frequency, prevent abuse, and determine ad personalization, the ad SDK may process advertising-related information such as device information, advertising identifiers, app interactions, and approximate region.

In some regions, Google User Messaging Platform consent screens or ad personalization controls may appear. On iOS, the app may request tracking permission through Apple's AppTrackingTransparency system prompt, which users can change in iOS Settings. On Android, Google advertising ID and device ad settings may be used, and users can reset or delete the advertising ID and change ad personalization settings in Android or Google settings.

If the user agrees, the app may send local device notifications at 06:00 and 18:00 KST for official market score and AI briefing releases. Notifications are off by default and can be changed anytime in app settings or device settings.

Users can generate a diagnostic log TXT file from the Data menu in Settings. The file is designed to include only information useful for issue reproduction and customer support, and it is shared only with the app or destination selected by the user from the share sheet.

Diagnostic logs do not include raw installation UUIDs or raw account UUIDs. Instead, they may include a short hashed diagnostic installation ID and session ID that cannot be used to restore the original values.

If a user sends a diagnostic log file to support, the file is reviewed only for error verification and troubleshooting.

Users can request deletion of their account and server data from My Page in app settings. When deleted, server-stored account profile, reward status, mock trading sync data, and nickname-related data are removed. Local cache or local mock trading data remaining on the device may require separate app deletion or cache clearing.

Amounts granted through check-ins, ad views, login, or purchase of an ad removal pass are practice funds for mock trading only. Practice funds have no cash value and cannot be withdrawn, refunded, transferred, or exchanged for real crypto assets.

Account data is retained while the account remains active. Server-side account data is deleted when account deletion is requested. On-device diagnostic logs use a rotating structure up to 10MB and remove older logs first. Files exported by the user follow the policy of the location where the user saves or shares them. Security and error-handling logs may be retained for a limited necessary period. This policy may be updated due to changes in features, ad SDKs, login structure, applicable laws, or store policies.

Contact: support@koujiapps.com