Privacy Policy for Keyboard Engine
Last updated: August 20, 2026
Keyboard Engine (“Keyboard Engine,” “the App,” “we,” “us,” or “our”) is provided by FocusedSeven. This Privacy Policy explains how information is handled when you use the App, including its custom keyboard, themes, sounds, word suggestions, typing practice, Google Play subscriptions, analytics, and support features.
Contact
FocusedSeven
Privacy and support email: keyboardenginedev@gmail.com
1. Summary
Keyboard Engine is designed to process keyboard input locally on your device. The App is not designed to send the text you type with the keyboard to FocusedSeven’s servers.
The App currently has no user account system, cloud sync, server-based typing suggestions, online AI typing service, or developer-operated cloud storage for keyboard input.
The App stores settings and optional learned suggestion data locally. It also integrates Google Play Billing for subscriptions, Google User Messaging Platform for privacy choices, Google Analytics for Firebase for app-usage measurement, and Firebase Crashlytics for crash, ANR, and diagnostic reporting. The Google Mobile Ads SDK and an AdMob app/ad-unit configuration remain included for possible future use, but the current version does not call the Mobile Ads initialization or ad-loading APIs, request ads, display ads, or provide ad-based unlocks. These services may process limited consent, analytics, diagnostic, and purchase information as described below.
2. Keyboard input
The App processes characters, words, commands, language and layout choices, cursor actions, and other input on your device so that the keyboard can function.
Keyboard input is not intentionally collected, transmitted, sold, or used by FocusedSeven for advertising or profiling. Text you enter can still be received by the app or website into which you type and may be processed by Android, your device manufacturer, accessibility services, backup services, or other software installed on your device. Those services are outside FocusedSeven’s control.
The App is designed not to learn from password fields, fields marked by the receiving app as not allowing personalized learning, and certain sensitive field types. No technical safeguard can guarantee that every third-party app labels every field correctly.
Optional voice typing opens the speech-recognition service installed on your Android device. Keyboard Engine does not bundle a speech model and does not directly receive microphone audio; the selected speech provider may process audio on-device or through its own servers under that provider’s privacy terms. Keyboard Engine receives the recognized text returned by Android and inserts it into the active text field.
The optional clipboard toolbar keeps recent copied text and any clips you choose to save in local App storage so you can paste them again. Recent clipboard history can include up to 30 unsaved entries, while saved clips remain until you remove them. Clipboard contents are not included in custom analytics events and are removed when you clear the App’s storage or uninstall the App.
The Custom Theme editor has its own temporary in-app color copy/paste function. Copying a theme color inside that editor does not place the copied color code into Android’s system clipboard and therefore does not add that theme color to the keyboard’s clipboard history.
Optional local utilities can use information available from your device while those utilities are in use. For example, Compass and Magnetic Field use the device magnetometer; G-force and Level use the accelerometer; Light Meter uses the ambient-light sensor; RAM and Storage use Android memory and storage statistics; and Calculator, Unit Converter, Timer, and Clock operate locally. The Magnetic Field utility also stores the highest measured magnetic-field peak locally so its permanent peak marker can persist between sessions. Raw sensor readings, utility values, and device-status readings are not intentionally included in Keyboard Engine custom analytics events.
The Timer utility stores the timer duration and end time locally while a timer is running. On Android 13 and newer, Keyboard Engine may request the standard notification permission so it can show the timer-finished alert. On Android versions that require special access for precise background alarms, Keyboard Engine may also ask for Android's “Alarms & reminders” access (SCHEDULE_EXACT_ALARM) solely to schedule a timer you explicitly start so that it can expire at the selected time even when the keyboard is not in the foreground. Timer does not require or use the broader Notification Access permission used by the Music utility. Timer selections, remaining time, and completion state are not intentionally included in custom analytics events. You can deny or revoke these permissions in Android settings, but timer alerts or precise background completion may then be unavailable.
The optional Music utility can control the currently active Android media session. Android requires you to grant Keyboard Engine Notification Access in system settings before Android will allow the App to query other apps' active media sessions. Keyboard Engine uses that access only to locate the active media session, read media-session metadata and playback state needed for the on-keyboard controls (such as track title, artist, duration, playback position, and whether playback is playing or paused), and send previous, play/pause, next, repeat/restart, repeat-mode, shuffle-mode, and seek commands to that media session. The Music panel’s Next / Repeat / Random mode control can make best-effort requests for repeat-one, shuffle off, or shuffle on. The active music app remains authoritative and may ignore, restrict, or interpret those commands differently depending on the app, account, or playback context. To make the Previous control target the actual previous song when a media app supports direct queue-item navigation, Keyboard Engine may also read that active media session’s currently exposed queue item identifiers and their order. Those queue identifiers are used transiently for the Previous command and are not stored as a playlist or listening history by Keyboard Engine.
Android's Notification Access capability is broader than the Music utility needs. Keyboard Engine's notification-listener service does not intentionally parse, save, upload, or build a history of notification contents. Track metadata and playback state used by the Music utility are handled transiently for the control panel and are not intentionally included in custom Firebase Analytics events. Granting Notification Access is optional; declining or revoking it disables Music controls but does not prevent normal keyboard use. You can revoke Notification Access at any time in Android settings.
3. Local suggestions and learned data
When word suggestions or learning are enabled, the App may locally store learned words, general word frequencies, sentence-start word frequencies, next-word relationships, language preferences, and similar suggestion information. This information remains on your device and is used to improve local suggestions. Sentence-start frequencies are used to seed the suggestion strip when the current text field or sentence is blank; for example, a word that you repeatedly use to begin messages can become an immediate starting suggestion.
You can clear learned words in Keyboard Engine settings. You can also remove local App data through Android settings or by uninstalling the App.
4. Local settings and entitlement state
The App may store the following locally:
- selected languages and keyboard layouts;
- up to 30 recent clipboard-history entries, plus clips you choose to save, when the clipboard tool is used;
- theme, font, sound, haptic, key appearance, cursor-control, and other keyboard settings;
- custom themes and keyboard presets;
- typing-practice settings and statistics;
- the locally remembered Magnetic Field peak used for its permanent peak marker;
- a temporary Timer duration and end-time state while a timer is running;
- onboarding, help, consent-flow, and popup status;
- legacy rewarded-ad unlock state from older versions, which may be cleared during migration;
- subscription entitlement state needed to enable or remove PRO features.
Local information normally remains until you change or reset it, clear the App’s storage, or uninstall the App.
5. Google Play subscriptions and purchases
Keyboard Engine offers Keyboard Engine PRO through Google Play Billing. Google Play processes payment authorization, payment methods, receipts, taxes, renewals, cancellations, refunds, chargebacks, and related billing records. FocusedSeven does not receive your full payment-card number.
The App may receive limited purchase information from Google Play, such as the product purchased, purchase state, acknowledgement state, purchase token, active or inactive entitlement state, selected base plan, localized price and currency, and related billing response information. The App uses this information to open the purchase screen, acknowledge purchases, unlock or restore PRO, remove PRO when entitlement ends, prevent fraud, and provide support.
The current App does not send purchase tokens to a FocusedSeven-operated subscription server. Google remains the primary holder of your Google Play purchase and payment records. A future secure verification service may be introduced; this policy will be updated before or when that occurs.
Subscriptions renew automatically according to the terms shown by Google Play unless cancelled. You can manage or cancel a subscription through the in-app “Manage subscription” button or through Google Play’s subscription center.
6. Advertising SDK status
The current version does not request or display advertisements and does not offer ad-based feature unlocks. Built-in keyboard themes and Font Glow are available in the free version. Premium fonts, sounds, keyboard presets, selected visual effects, and other features explicitly marked as PRO may require Keyboard Engine PRO.
The Google Mobile Ads SDK, AdMob app ID, and an AdMob rewarded-ad unit may remain configured in the App so advertising can be restored in a future version without recreating the integration. Ad loading is disabled in the current version: the App does not call the Mobile Ads initialization or rewarded-ad loading APIs. Merely retaining the inactive SDK configuration does not create an ad impression or an ad request from the App’s code.
If advertising is introduced again, this policy and the App’s disclosures will be updated as needed before or when that change takes effect.
7. Consent and privacy choices
The App uses Google’s User Messaging Platform to request and store privacy choices where required. The App requests updated consent information when appropriate and provides a “Privacy choices” option when Google indicates that a privacy-options entry point is required. Where applicable, the App uses that consent result to enable or disable Firebase Analytics storage.
Where consent is legally required, Analytics storage and related storage or access are based on your consent. You may withdraw or change that consent through the available Privacy choices screen. Depending on your choice and region, Firebase Analytics may remain inactive. The current version does not use this consent flow to request or display ads because ad loading is disabled.
8. Analytics, Crashlytics, diagnostics, and security
The App uses Google Analytics for Firebase to understand App usage, onboarding, keyboard activation, and feature engagement. Depending on Google configuration, device settings, region, and applicable privacy choices, Analytics may process information such as App instance identifiers, App version, device model, operating system, device language, general region inferred from IP address, App launches, engagement, and automatically collected events and user properties.
The App also sends privacy-limited custom Analytics events. These may record whether Keyboard Engine is enabled or selected as the active keyboard; which App screen or optional utility was opened; keyboard-session duration and a coarse count of keyboard interactions; whether the emoji panel was opened; selected built-in theme, font, sound, and key-material identifiers; coarse key-material opacity; counts of enabled keyboard languages, saved custom themes, imported keyboard designs, design exports, and presets; keyboard-design actions such as import, export, selection, deletion, sharing, layout compatibility, and whether an export kept the current theme; whether a custom theme was created, updated, or deleted together with the total custom-theme count; the name and coarse value of a changed keyboard setting; enable/disable state for toolbar tools or utilities; premium-feature taps; and subscription-plan, purchase-start, pending, cancellation, success, or error states. Keyboard-design artwork, filenames, user-created design names, colors, and file contents are not included in these custom events. Slider-related setting events are debounced to avoid logging every pixel of movement. These events are intended to measure setup completion, feature discovery, and which settings are useful without recording the content being typed or the private media/sensor values described above.
The App uses Firebase Crashlytics to identify and investigate crashes, non-fatal errors, and application-not-responding events. Crashlytics may process crash stack traces, thread and process state, App version, device model, operating-system version, available memory and storage, network state, installation or instance identifiers, timestamps, and related diagnostic information.
FocusedSeven does not intentionally send typed text, individual key values, emoji content, learned words, custom-theme colors or contents, preset names or contents, the actual list of selected keyboard languages, raw utility sensor readings, Timer durations or remaining-time values, or Music track titles, artists, playback positions, or media-session commands to Firebase Analytics or Firebase Crashlytics as custom analytics event data. Analytics may receive the feature and setting metadata described above, including setting names and coarse values, but not the text entered through the keyboard or the media/sensor values listed here.
Google Play Billing, Google Mobile Ads, Google User Messaging Platform, Firebase, Android, and Google Play may also process diagnostic and security information needed to provide their services, detect fraud, investigate failures, and maintain performance. This can include App version, device and operating-system information, app-launch information, SDK performance, error codes, network status, and crash or diagnostic details generated by those services.
9. Support communications
When you contact FocusedSeven, we receive the information you choose to provide, such as your email address, message, screenshots, device model, Android version, App version, purchase details, or diagnostic information.
Support information is used to answer your request, troubleshoot problems, verify purchases where possible, prevent abuse, maintain business records, and comply with legal obligations. Do not send passwords, private messages, full payment-card details, or other unnecessary sensitive information.
10. Purposes and legal bases
Depending on your location, information is processed for the following purposes and legal bases:
- to provide the keyboard, subscriptions, purchases, and requested features, based on performance of a contract or steps requested before entering a contract;
- to remember local settings and operate optional features, based on your request and the App’s legitimate interests in providing a functional service;
- to measure App usage, improve features, prevent fraud, secure the App, diagnose errors and crashes, and enforce terms, based on consent or legitimate interests as applicable and on legal obligations;
- to handle support, disputes, refunds, tax, accounting, and regulatory duties, based on contract, legitimate interests, and legal obligations.
11. Sharing and third parties
FocusedSeven does not sell the text you type or intentionally share it for advertising.
Information may be processed or shared in these limited situations:
- with Google Play and Google Play Billing for app distribution, purchases, subscriptions, entitlement checks, security, fraud prevention, taxes, and compliance;
- with Google User Messaging Platform for privacy choices and consent signals, and with the dormant Google Mobile Ads SDK configuration only if advertising is enabled in a future version;
- with Google Analytics for Firebase and Firebase Crashlytics for usage measurement, crash and ANR reporting, diagnostics, performance investigation, security, and App improvement;
- with email and support providers when you contact us;
- with professional advisers or authorities when reasonably necessary to comply with law, protect rights, investigate fraud or abuse, or resolve disputes;
- in connection with a merger, acquisition, financing, or transfer of the App, subject to appropriate notice and legal safeguards.
Some privacy laws define certain personalized-advertising disclosures as “sharing” or a “sale” even when no money is paid for personal information. Where required, applicable choices are provided through the consent or privacy-options interface.
12. International processing
Google and other service providers may process information in countries other than the country where you live. Those providers are responsible for using legally recognized transfer safeguards where required. FocusedSeven will use appropriate safeguards for information it directly controls.
13. Retention and deletion
Local keyboard settings, learned words, clipboard-history entries, typing-practice data, legacy rewarded-unlock state, and local entitlement state remain on your device until removed through App controls, Android settings, migration cleanup, or uninstalling the App.
Support emails and related records are retained only as long as reasonably needed to respond, troubleshoot, prevent abuse, resolve disputes, and meet accounting or legal requirements.
Google Play, Google Mobile Ads, Google Analytics for Firebase, Firebase Crashlytics, and other service providers retain information under their own policies, project retention settings, and legal obligations. FocusedSeven cannot directly delete records controlled solely by another provider. You can manage Google account, advertising, and purchase information through Google’s controls.
To request access to or deletion of information you provided directly to FocusedSeven, email keyboardenginedev@gmail.com. We may need to retain limited information when required for legal, fraud-prevention, tax, accounting, security, or dispute-resolution purposes.
14. Your privacy rights
Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection; to withdraw consent; and to complain to a data-protection authority. You may also have rights concerning targeted advertising, sale, or sharing under applicable US state laws.
Many Keyboard Engine data items are stored only on your device, so the most direct way to exercise deletion or correction is through the App’s reset controls, Android’s App storage controls, or uninstalling the App. For information held by Google, use Google’s privacy and account controls. For information directly held by FocusedSeven, contact keyboardenginedev@gmail.com.
15. Children and age-related treatment
Keyboard Engine is intended for users aged 13 and older and is not directed to children under 13. We do not knowingly request that children under 13 send personal information to FocusedSeven.
Advertising-consent age thresholds vary by country and can be higher than 13. Where required, the App must apply appropriate under-age treatment and avoid requesting consent from a user who cannot legally provide it. A parent or guardian may contact keyboardenginedev@gmail.com regarding information a child provided directly through support.
16. Security
The App is designed to minimize data collection and keep keyboard input local. Reasonable technical and organizational safeguards are used for information directly controlled by FocusedSeven, but no device, software, transmission, or storage system can be guaranteed completely secure.
17. Changes to this policy
This policy may be updated when features, service providers, laws, or platform requirements change. The updated policy will be posted at the App’s privacy-policy location and may also be shown in the App. The “Last updated” date will identify the current version.
18. Contact
Privacy, support, and data-rights requests:
keyboardenginedev@gmail.com