Last updated: 2026-08-04
Contact: nativekey.support@gmail.com
This Privacy Policy explains how NativeKey, an Android custom keyboard app published under the package name com.nativekey.keyboard, handles information when you use the app.
NativeKey is a keyboard input method. It lets you type into other apps, provides optional on-device suggestions and learning, and offers optional AI-assisted writing, rewriting, translation, and understanding features.
NativeKey is a third-party Android keyboard. When enabled in Android system settings, it can:
Android displays a standard warning when any third-party keyboard is enabled. NativeKey is designed so that normal typing does not call AI services and protected fields use a privacy-safe keyboard mode.
NativeKey does not automatically send messages, submit forms, or press a host app’s Send button.
When you type without using AI:
The host app receives the text you enter because that is the purpose of the keyboard.
NativeKey can suggest words from built-in word lists and from on-device learning. Suggestion generation and ranking are performed locally.
Local suggestions are not sent to cloud AI providers for ranking.
When enabled and allowed for the current field, NativeKey may store local statistics such as learned words, correction choices, and word-pair patterns to improve future suggestions.
This information remains in app-private storage on your device.
You can delete learned suggestion data in:
Settings → Privacy & Safety → Local suggestions → Clear learned suggestions
This control removes locally learned suggestion data. It does not remove API keys, keyboard language choices, AI settings, purchase-entitlement records, or Keyboard Lab customization.
NativeKey stores settings locally, including:
On supported devices, NativeKey can use Gemini Nano through Android’s on-device AI system services and ML Kit GenAI APIs.
When on-device AI is selected:
Android or Google system services may download, update, prepare, or manage the on-device model and related components. Those system services are controlled by Google and Android and may handle technical service information under their own terms.
NativeKey does not receive your prompt through a NativeKey server.
Ownership of an On-device AI purchase does not determine whether a particular device technically supports Gemini Nano.
To reduce exposure of sensitive information, NativeKey checks local field metadata and app context, such as input type flags, field hints, package names, and app labels.
This detection is performed locally and does not upload your typed content for classification.
In protected contexts, NativeKey is intended to operate as a normal keyboard only. AI actions, clipboard reading for AI, local suggestions, local learning, and related features are disabled where designed.
NativeKey stores a local record of Google Play purchase status so that the app can show whether each optional product is:
The current implementation keeps separate entitlement records for:
These products are independent. A purchase record for one product does not automatically create ownership of the other.
The local purchase record may contain:
The local purchase record does not contain:
NativeKey excludes its lifetime-entitlement preference file from the Android cloud-backup and device-transfer rules configured by the app.
Cloud AI features are optional.
If you save an API key and explicitly start a cloud AI action, NativeKey may send the following over HTTPS:
The data is sent directly to the provider you selected under:
Settings → Connect your AI
Supported cloud providers may include:
Cloud AI requests use your own API key. NativeKey does not currently provide a shared NativeKey cloud AI account or operate a shared NativeKey cloud AI backend on your behalf.
Outgoing AI actions, such as rewriting or translating text you wrote, run only after you explicitly request the action.
Incoming AI actions, such as translating copied text, may read clipboard plain text only after you initiate the incoming AI flow.
If you do not configure a cloud provider or do not start a cloud AI action, cloud AI transmission does not occur.
When text is sent to Google, Anthropic, or OpenAI, that provider processes it under its own terms, privacy policy, account settings, and retention rules.
NativeKey does not operate those services and cannot guarantee:
For requests concerning data held by a cloud AI provider, use that provider’s account, privacy, and support processes.
NativeKey uses Google Play Billing for optional one-time purchases.
When Billing features are used, NativeKey communicates with Google Play to:
NativeKey may query Google Play when the NativeKey settings app starts or resumes, when purchase information needs to be refreshed, or when you choose Restore purchases.
Google Play Billing operations do not include:
Google Play handles the financial transaction under Google’s own terms and privacy practices.
Cloud AI features require an API key obtained directly from the selected provider.
Settings → Connect your AI.Treat API keys like passwords. You are responsible for use, limits, and billing associated with your provider account.
NativeKey excludes certain preference files, including files that may contain API keys and learned suggestion data, from the Android cloud-backup rules configured by the app.
You should nevertheless assume that a saved key remains on the device until you remove it, clear app data, or uninstall NativeKey.
NativeKey may read clipboard plain text when:
NativeKey does not declare a separate Android clipboard permission. Clipboard access uses Android platform APIs available to the keyboard in the relevant context.
Clipboard text used with on-device AI is processed on the device.
Clipboard text used with a cloud AI action may be sent to the selected provider as described in Section 3.
NativeKey does not send clipboard text to an AI provider in the background without your action.
NativeKey supports two independent optional one-time purchase products:
NativeKey does not currently offer subscriptions.
Prices are supplied by Google Play in localized form. NativeKey does not hardcode or calculate your payment details.
For purchase, acknowledgement, and restore functionality, NativeKey may receive technical purchase information from Google Play, including:
NativeKey does not request or store:
A Google Play purchase token may be handled temporarily in application memory when NativeKey receives, processes, or acknowledges a purchase.
NativeKey does not persist purchase tokens in its entitlement preferences.
NativeKey does not intentionally log purchase tokens.
NativeKey does not send purchase tokens to a NativeKey-operated server.
NativeKey currently does not operate a purchase-verification backend.
A purchase reported by Google Play as pending is recorded as pending and is not recorded as purchased.
NativeKey waits until Google Play reports the purchase as completed before recording the related product as owned.
After NativeKey receives an eligible completed purchase, it may acknowledge the purchase through Google Play.
Acknowledgement informs Google Play that the completed purchase has been processed by the app.
An acknowledgement error does not itself prove that the underlying purchase is invalid. A later Google Play query may return the purchase again and allow another acknowledgement attempt.
Restore purchases performs a current query to Google Play for active purchases associated with the Google Play account currently used by Google Play on the device.
NativeKey does not grant restored ownership from the local cache alone.
If Google Play returns a successful purchase result:
If Google Play is unavailable or returns an error, NativeKey preserves previously verified local ownership instead of treating the connection failure as proof that a purchase does not exist.
Clearing NativeKey app data or uninstalling NativeKey removes the local purchase-entitlement records.
This does not by itself cancel or refund a Google Play purchase.
Eligible purchases may be restored by querying Google Play again with the Google Play account used for the purchase.
NativeKey declares the INTERNET permission so it can contact a cloud AI provider when you explicitly use a cloud AI feature.
The NativeKey input-method service is protected by Android’s BIND_INPUT_METHOD system permission. This allows NativeKey to function as a keyboard and is controlled by Android.
NativeKey uses the Google Play Billing Library for purchase operations. The Billing Library supplies the Android manifest access required to communicate with Google Play Billing.
This Billing access does not give NativeKey access to payment-card numbers, bank-account details, or full payment credentials.
NativeKey does not request permissions for:
Based on the current app implementation:
If this changes in a future version, this policy and the Google Play Data Safety declaration will be updated before or alongside that release.
Learned words, correction choices, and word-pair patterns remain on your device until you:
Saved API keys remain on your device until you:
Other local settings remain until changed, cleared, or removed with the app.
Local purchase-entitlement records remain on the device until NativeKey app data is cleared or the app is uninstalled.
These records are excluded from NativeKey’s configured Android cloud-backup and device-transfer rules.
Removing local entitlement records does not cancel or refund a Google Play purchase.
Eligible purchases may be restored through Google Play.
Purchase tokens are not stored in the local entitlement record.
NativeKey does not store on-device AI prompts or results on a NativeKey server.
Temporary in-app state may remain in memory or local UI state only as needed to display or apply the current result.
Text sent to Google, Anthropic, or OpenAI is handled according to the selected provider’s policies.
NativeKey does not control the provider’s retention period and cannot delete provider-held request data on your behalf.
Google Play retains and processes purchase, payment, account, and transaction information under Google’s own terms and privacy practices.
NativeKey does not control Google’s retention periods or Google Play purchase records.
NativeKey does not create or require a NativeKey account.
NativeKey does not operate a central user-account database or a server database containing your normal typing content.
You can delete local NativeKey data by:
Clearing app data or uninstalling NativeKey removes the local purchase-entitlement records but does not automatically cancel or refund a Google Play purchase.
To manage purchases, refunds, or the Google Play account used for a purchase, use Google Play’s own purchase and account controls.
To request information about deletion of any data that NativeKey may control, contact:
nativekey.support@gmail.com
Because NativeKey does not maintain user accounts or a central database of typing content, there may be no server-side NativeKey data associated with your request.
For data sent to a cloud AI provider, contact that provider or use its account and privacy controls.
For payment and purchase records held by Google Play, use Google’s account, privacy, payment, and support processes.
You can:
NativeKey is not directed to children under 13 or under the minimum age required by applicable law.
We do not knowingly create NativeKey accounts for children because NativeKey does not provide user accounts.
Purchases are handled through Google Play and may be subject to Google Play family, parental, approval, and payment settings.
If you use cloud AI, text may be processed in countries where Google, Anthropic, or OpenAI operate infrastructure.
That processing is initiated by your explicit use of the selected cloud AI provider with your own API key.
On-device AI processing occurs on the supported Android device, although Android system services may contact Google to prepare or update the model and related system components.
Google Play Billing, payment, and purchase information may be processed in countries where Google and its payment providers operate, under Google’s own terms and privacy practices.
We may update this Privacy Policy when NativeKey’s features, providers, purchase model, data handling, or legal requirements change.
The Last updated date at the top will change when the policy is revised.
For material changes, notice may be provided in the app or on this published page where feasible.
Questions or data-deletion requests:
nativekey.support@gmail.com
NativeKey includes in-app Privacy & Safety information explaining that: