Prompt AI Keyboard (“the app”) is a custom keyboard for iOS and Android. This policy explains what data the app handles and why. It is written to be short and plain. The app does not require an account and does not collect your name, email address, or any other personal identity information.
In short
The detail is in the sections below; this is the whole of it in ten lines.
- No account. The app never asks who you are, and collects no name or email address.
- Typing is not sent anywhere on its own. The keyboard sends text only when you tap an AI action or the microphone.
- An AI action sends the text in the field, plus which mode you chose, to our backend and on to Google’s Gemini API — for that request, and nothing else.
- Reply is the one mode that reads your clipboard, and only while the key is set to it. It shows you what it has read before you tap.
- Secret text is locked on your phone. Encrypt and Decrypt use no AI and send your text nowhere. We never see the message and never see the passphrase, and we cannot recover either.
- Voice sends the clip you recorded. On iPhone the app holds the microphone open for the length of a voice session, which is why iOS shows its orange indicator for the whole session; nothing is recorded or sent until you tap the microphone key.
- The words autocorrect learns and your recent rewrites stay on the device. Neither is uploaded, and both can be erased from settings.
- You are counted, not identified. An anonymous install ID carries your daily usage count and whether you have Pro. Nothing links it to you.
- We do not keep your text or audio once a request has been processed.
- Crash reports carry no text. If the app or the keyboard fails, we receive a diagnostic report — what went wrong and where in the code — never what you were writing.
What the app sends, and when
The app only sends data to our servers when you actively trigger a feature — it does not run in the background or send what you type as you type.
- Enhance and the other rewrite modes. When you tap the Enhance key, the text you have entered in the current field is sent to our backend, which forwards it to Google’s Gemini API to produce a rewritten version. The result is returned to the keyboard and replaces — or, for Continue writing and Ask AI, is added below — your text. This is the same for every mode the key can be set to: enhance, fix grammar, shorten, lengthen, rephrase, change tone, continue, reply, ask, and translate. Which mode you chose is sent with the text so the backend knows what to do with it, and Translate additionally sends the two languages you have picked. The text is sent only to perform the rewrite you asked for.
- Secret text is encrypted and decrypted on your device, and nothing about it is sent to us. Encrypt and Decrypt are the two modes that do not use AI and do not send your text anywhere. The scrambling happens on the phone, using a passphrase you choose; we never see the passphrase and we never see the text. The passphrase is stored on the device — in the iOS Keychain, or on Android encrypted with a key held in the Android Keystore — and it is never sent to us and never recoverable by us. If you forget a passphrase, we cannot help you get the text back, because we have neither the passphrase nor the text. One thing worth knowing about where it is kept: on iPhone the Keychain is Apple’s, so if you use iCloud Keychain, Apple may sync the passphrase between your own devices and include it in an encrypted device backup — under your Apple account, never ours. On Android the key that seals it lives in the device’s Keystore and is not backed up at all, which is why a reinstall or a factory reset loses the stored passphrases. The one thing that does touch the network is the count: encrypting uses one of your daily AI requests, so the keyboard asks our backend to record that before it encrypts. That request carries your anonymous install ID and nothing else — no text, no passphrase. Decrypting is free and makes no request at all. A message you unlock is shown in the keyboard and nowhere else: it is not typed into the conversation and not added to your saved rewrites.
- Presets stay on your device. The prompts you save as presets, the topics you create, and which presets you favorite or used recently are stored on the device, alongside the keyboard's other settings, and are never sent to us. A preset you insert becomes ordinary text in the field: it is sent only if you then tap Enhance, exactly as text you typed yourself would be.
- Reply mode reads your clipboard. Reply is the one mode whose input is not the text in the field: it sends the message you have copied to our backend, so that the AI can write an answer to it. The keyboard shows you a preview of what it has read before you tap, and it only reads the clipboard while Reply is the mode the key is set to.
- Voice transcription. If you use voice input, the recorded audio clip is sent to our backend and forwarded to Google’s Gemini API to be transcribed into text, which is returned to the keyboard. Audio is sent only to perform the transcription. Voice input requires the microphone permission, which you grant in the app; on iOS the keyboard also requires “Allow Full Access”.
- On iOS, the app holds the microphone open for the length of a voice session. iOS does not allow a keyboard to use the microphone at all, so the AI Keyboard app records on the keyboard’s behalf and keeps running in the background while voice typing is switched on. iOS shows the orange microphone indicator for that whole session, not only while you are speaking. Nothing is recorded, saved or sent until you tap the microphone key on the keyboard; audio outside a dictation you started is discarded as it arrives and never reaches storage or the network. The session is off until you turn it on, ends after a period you choose (fifteen minutes by default), and can be ended at any time from the app’s Voice typing screen.
- Importing a preset from an image. If you choose “From image” on a presets screen in the app, the photo or screenshot you pick is reduced in size on your device and sent to our backend, which forwards it to Google’s Gemini API to read the prompt in it. The text read from it is returned to the app’s preset editor, where nothing is saved until you tap Save. The image is sent only for that request and is not stored by us. The keyboard itself never sends images.
- Clipboard context (optional, iOS “Allow Full Access”). You can attach the current clipboard text to a rewrite as reference material, by tapping the clipboard key. It is sent in the same request and is not stored separately. Nothing is read from your clipboard unless you tap that key or use Reply mode.
Our backend runs on Google Firebase / Google Cloud. We do not sell your data, and we do not use the content of your text or audio to build advertising profiles.
The anonymous install ID
To enforce fair daily usage limits (and to recognise an active subscription), the app generates a random anonymous install identifier the first time it runs and stores it on your device. This ID is not linked to your identity — it is a random value, not your name, email, phone number, or any device hardware identifier. It is sent with each request so the server can count usage per install and apply the free-tier daily limit or your Pro entitlement.
Subscriptions and purchase verification
If you subscribe to Pro, the purchase is processed by Apple (App Store) or Google (Google Play) — we never see or store your payment details. To confirm a subscription is valid, the app sends the store-issued purchase receipt to our backend, which verifies it directly with Apple or Google and records that your anonymous install ID is entitled to Pro (and when that entitlement expires).
App integrity (App Check)
The app uses Firebase App Check (Apple App Attest / Google Play Integrity) to confirm requests come from a genuine, unmodified copy of the app. This protects the service from abuse. App Check does not identify you and does not collect personal data.
Crash and diagnostic reports
The app uses Firebase Crashlytics so that a crash or a fault is something we can find and fix rather than something you have to describe to us. A report is sent when something goes wrong, and it contains:
- what failed and where in our code (the stack trace), and the app version it happened in;
- your device model, operating system version, and how much memory was free at the time;
- the anonymous install ID described above, so that several reports from one device can be recognised as one device;
- a small amount of our own context about the state the app was in — which rewrite mode was selected, which keyboard layer was open, whether iOS Full Access was granted.
It never contains anything you wrote. Not the field you were typing in, not your clipboard, not a transcript of your dictation, not a passphrase or the name you gave one. This is not a promise we ask you to take on trust: the rule is enforced by a test in the shared code that drives real failures with a known string in every place your words can be, and fails the build if any of it reaches a report.
The iOS keyboard cannot send anything itself — Apple does not allow it the memory — so when the keyboard fails, a report is written into storage the app and keyboard share and sent the next time you open the app.
Crashlytics is a Google service; reports are retained for up to 90 days. You can read Google’s terms at firebase.google.com/terms/crashlytics.
What we store, and for how long
- Usage counters — a per-install, per-day count of how many enhancements/transcriptions you used, stored against your anonymous install ID. These automatically expire about two days after the day they cover.
- Subscription entitlement — a record that your anonymous install ID has Pro and when it expires, kept while the subscription is active.
- The content of your text and audio is not stored by us after a request is processed. It is sent to Google’s Gemini API to generate the response and is handled under Google’s terms for that API. See Google’s privacy information at https://ai.google.dev/gemini-api/terms and https://policies.google.com/privacy.
Website analytics
Our marketing website (promptkeyboard.app) uses Google Analytics to understand aggregate, anonymous traffic (page views, approximate region, device type). This uses cookies and is separate from the app; it does not identify you and does not apply to using the keyboard itself. You can opt out with Google’s browser add-on: https://tools.google.com/dlpage/gaoptout.
Children
The app is not directed at children under 13 (or the equivalent minimum age in your country) and we do not knowingly collect personal information from them.
Your choices
- You can stop all data being sent by not using the Enhance key or the microphone, or by removing the keyboard in your device settings.
- On iOS, you can disable “Allow Full Access” to prevent clipboard context being read.
- Uninstalling the app removes the anonymous install ID stored on your device.
Changes to this policy
If we change how the app handles data, we will update this policy and revise the effective date above.
Contact
Questions about this policy: support@promptkeyboard.app.