Key Ddal — Privacy Policy
Version: 1.4.0
Effective date: 2026-10-08
1. Operator and scope
Akra Dev, based in Seoul, Republic of Korea, provides Key Ddal: ASMR Keyboard. This policy covers the Android app distributed through Google Play. Contact help@akra.kr for privacy and support requests. The app does not provide user accounts or server-hosted user profiles.
2. Information kept on your device
The app stores owned items, keyboard selections, currency, tap and reward progress, duplicate-reward protection records, and settings on your device. Advertising frequency and purchase-entitlement recovery records may also be stored locally. App-owned code does not upload this progress or synchronize it to an account. Text entered in the in-app typing room exists only in session memory; it is not saved, transmitted, or sent as an analytics event.
When you enable the Android system keyboard, composing text is processed transiently in its separate input-method process and delivered to the focused app. Key Ddal does not store, log, upload, or send this text to analytics. The app receiving your input handles that text under its own policies. Keyboard appearance, sound and haptic preferences, style points, and reward records stay on this device.
3. Advertising and privacy choices
The app includes Google Mobile Ads and Google User Messaging Platform (UMP). When ad requests are permitted, Google may process IP addresses, app and ad interactions, diagnostic information, and device identifiers such as the advertising ID for ad delivery, measurement, and fraud prevention. Consent messages are provided where required. Where privacy choices are available in Settings, you can revisit them. Rewarded ads are optional.
The app's AdMob service is linked to its Firebase and Google Analytics services. This makes collected Analytics data available to AdMob and AdMob ad-revenue data available in Analytics for monetization and engagement reporting, including retention. This connection does not turn on usage analytics for users who have left it disabled, or activate advertising audiences. Advertising consent and usage-analytics choices remain separate.
AdMob mediation can also request and display ads from Unity Ads. Unity may process device identifiers, IP address and approximate location, app/ad interactions and SDK diagnostics for ad delivery, measurement and fraud prevention. Advertising requests remain subject to UMP and applicable privacy choices. Keyboard text is not sent to Unity. See https://unity.com/legal/game-player-and-app-user-privacy-policy .
4. Usage measurement and diagnostics
Starting with app version 1.0.6, usage statistics sharing is initially enabled. A previously saved choice to turn it off is respected, and you can turn it off at any time in the app settings. Earlier app versions start collection only after you enable it. While enabled, Firebase Analytics may process app launches, sessions, screen events, app-instance identifiers, app and device information, and approximate location. Analytics advertising-ID collection and default advertising-personalization signals are disabled, and the app does not set a user ID. Firebase Crashlytics may process stack traces, device and app information, and installation identifiers to diagnose crashes and unresponsiveness. App-owned diagnostic records use bounded error codes and sanitized context, without Type text, credentials, or raw purchase tokens.
5. Configuration delivery and providers
The app retrieves signed notices, version requirements, translations, and policies over HTTPS from GitHub Pages at akra.kr. The host receives connection information such as the IP address and requested path. Configuration requests do not include gameplay progress or typed text. Google services and GitHub process information under their respective privacy notices and may process it in other countries. See https://policies.google.com/privacy , https://firebase.google.com/support/privacy , and https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement .
6. Purchases and billing
New in-app purchases are disabled in the current configuration. Where purchase or restore functionality is available, Google Play handles payment; the app does not receive payment-card details. The app may process transaction status and entitlement information and uses a hash instead of a raw purchase token in its local records. This policy will be updated before a new purchase-verification service is introduced.
7. Retention, deletion, and requests
Local progress and settings are deleted when you clear app data or uninstall. Type text does not persist after the session. Remote configuration is cached locally for offline use. Google, Unity and GitHub retain service records according to their purposes, settings, and policies; uninstalling does not necessarily remove those records. Information sent by email is used to handle your request and necessary follow-up. Send privacy access, correction, or deletion requests to help@akra.kr. We may request minimal information needed to identify the request and will handle applicable rights under relevant law. There is no separate account-deletion flow because the app has no accounts.
8. Permissions and security
Optional local reminders request notification permission; vibration provides haptic feedback. No microphone recording is used.
Network access supports advertising, consent, diagnostics, measurement, and configuration downloads. The app does not request contacts, camera, microphone, precise-location, or photo access. Sounds use bundled files. Remote configuration uses HTTPS, signatures, and integrity checks; failed verification retains usable cached or bundled settings. These measures do not guarantee absolute security.
9. Audience and changes
The app is intended for people aged 13 and over and is not directed to children. Additional local requirements, including guardian consent where applicable, must be followed. Material privacy changes will be announced in the app or on this page, with separate consent when required. Published documents carry a version and effective date, and prior published versions are retained.