Tadak Privacy Policy

1. Personal Information We Process

1-1. Account and login information

• Guest status, internal user identifier, login state
• Social login provider information for Google, Apple, and Kakao, including provider name, provider user identifier, and email if shared
• Linked account state and last login provider

1-2. Profile and app settings

• Nickname, nickname tag, preferred theme, font, and language settings

1-3. User-generated content (UGC)

• Titles, body text, artist field, language, and visibility setting for writings you create
• Community feed posts, visibility state, quality score, report count, and moderation notes
• Likes, imports, and public sharing history
• Hidden or blocked author state and your hidden-author list

1-4. Report data

• Post reports: reporter identifier, reported post identifier, report reason, and report timestamp
• User reports: reporter identifier, reported user identifier, related post identifier, report reason, report timestamp, and target snapshot
• Aggregated report counts, temporary hidden status, and moderation review state

1-5. Feedback data

• In-app feedback or bug report message, category, submission source, platform, and app version
• Metadata such as submission time, signed-in user identifier when applicable, and client timestamp

1-6. Purchase, restore, and ad data

• Ad removal product ID, purchase start or success or failure or restore state, and store error codes
• Refund or entitlement revocation reason and local ad-removal state
• Ad impression, click, and revenue events, including network and placement information

1-7. Ad identifiers and ATT

• iOS ATT pre-prompt exposure, variant, and authorization status
• Advertising identifier or equivalent ad measurement data within the scope allowed by the operating system and your settings

1-8. Analytics and device or usage data

• Firebase Analytics and Supabase tracking_events for app open, session start or end, practice start or completion, experiment exposure, and ad or purchase events
• anonymous_id, user_id, session_id, practice_id, platform, app version, and event payloads created during operation
• Operational and error logs used for service maintenance and abuse prevention

2. Purposes of Use

• Account identification, sign-in, guest-to-social linking, and session management
• Typing practice, record storage, writing management, and public community posting
• Receiving reports, hiding or blocking authors, temporarily hiding content, moderation review, and policy enforcement
• Reviewing feedback, handling bugs, and responding to support requests
• Providing ads, processing ad-removal purchases, restoring purchases, and handling billing support
• Service analytics, experimentation, quality improvement, operational decision-making, and fraud prevention
• Security, legal compliance, and dispute handling

3. Retention and Deletion Standard

• Account, profile, typing records, private writings, public posts, likes, imports, and hidden-author data are generally retained while the account remains active and are handled as deletion targets when the account is deleted.
• Post reports are handled as deletion targets when tied to the deleted account, but user reports may remain after reporter or target identifiers are removed so moderation history can be retained.
• In-app feedback data and analytics, ad, or billing event logs may be retained in separate logs for service improvement, abuse prevention, billing support, and operational analytics.
• After account deletion, tracking_events, in_app_feedback_events, ad_interstitial_events, att_prompt_events, review_funnel_events, and community_user_reports may remain only in a pseudonymous or identifier-redacted operational log form.
• If you type personal or sensitive information directly into a feedback or report message, that text may remain as submitted content. Please avoid including sensitive information.
• We may retain data longer when required by law, for dispute handling, for security investigation, or under app store billing rules.

4. External Services and International Processing

We use the services below to operate the app, and data may be processed outside Korea in connection with those services.

• Supabase: authentication, profile, record, UGC, report, feedback, and tracking_events storage
• Firebase Analytics: analytics for app usage, sessions, practice, billing, and ad events
• Google AdMob: ad delivery, ad performance measurement, and ad revenue aggregation
• Google, Apple, and Kakao sign-in: authentication and account linking
• Apple App Store and Google Play: purchase, restore, refund, and entitlement handling

Because these providers operate global infrastructure, information may be processed on servers located outside Korea, including the United States and other jurisdictions used by the relevant provider.

5. Ad Identifiers and ATT

• On iOS, we may record ATT pre-prompt behavior and authorization results before or after the system request.
• Advertising identifiers or equivalent ad measurement data are used only within the limits allowed by the operating system, your settings, and applicable policy.
• If you purchase ad removal, ad display can be limited in-app, and restore eligibility is checked against store purchase history.

6. Account Deletion and Post-Deletion Exceptions

• In-app route: `Profile > Account Management > Delete`
• Deletion targets include profile, practice records, private writings, community posts, likes, imports, post reports, hidden-author data, and certain legacy migration audit records directly tied to the account.
• For guest usage, deleting the guest account removes the guest state and the writings or records tied to that account.
• Separate analytics logs, in-app feedback, monetization logs, ATT or review events, user-report moderation logs, and app store purchase history may remain in pseudonymous, separated, or provider-side systems after account deletion.
• Deleting your Tadak account does not automatically delete your Google, Apple, or Kakao account with that provider.

7. Your Rights and How to Exercise Them

• You may contact us about access, correction, deletion, or suspension of processing.
• If you can access the app, please use the in-app account deletion flow first.
• If you cannot access the app or need additional help, contact us by email.
• See the Account Deletion page for deletion scope and the Community Policy for reporting and moderation standards.

8. Security Measures

• We apply access controls, authentication management, transmission protection, and operational monitoring.
• Operational access for reports, moderation, feedback review, and account deletion is limited to what is necessary.
• We follow procedures to reduce impact and prevent recurrence if a security incident occurs.

9. Policy Changes

We will provide notice through public URLs or in-app notice before material changes to service integrations, retention standards, or processing scope take effect.

10. Privacy Contact and Related Links

• Channel: OMILSOFT Privacy Team
• Email: omilsoft@gmail.com
• Email requests are reviewed on business days in the order received.