Your Keyboard Knows Everything. I Built One, and Here Is What I Think You Should Know.
I built an AI keyboard, so I know exactly what can happen to the words you type. Here’s what keyboard apps can see, when your data can leave your phone, and why privacy mode matters.

The first time I really thought about keyboard privacy, it honestly made me uncomfortable.
A few months ago, I realized that I had given a keyboard app permission to see practically everything I typed. And the strange part? I had never really stopped to think about what happened to that information after I typed it.
I had used that keyboard for years.
It had potentially seen passwords, bank details, private conversations, job applications, personal searches, and all the random things people type into their phones when nobody else is watching.
And somewhere along the way, I had agreed to a privacy policy that I never actually read.
That experience was one of the reasons I decided to build FlickReply.
Not because I wanted to create another keyboard.
I wanted to build a keyboard where I understood exactly what was happening with the information people type.
The uncomfortable truth about keyboards
Here is something that is easy to forget:
A keyboard has to see what you type.
That is simply how a keyboard works. It sits between your fingers and the app you are using and turns your taps into text.
So asking whether a keyboard can see your typing is not really the right question.
The better question is:
What happens after the keyboard sees it?
That is where things become important.
Different keyboards can handle your data in very different ways.
Standard keyboards
Traditional keyboards can process your typing locally on your phone. Your taps become text, and that text is passed to the application where you are typing.
There is no reason for your keyboard to send everything to a remote server just because you are typing.
Cloud-connected keyboards
Some keyboards use cloud services for features such as predictions and other improvements.
In those situations, certain typing patterns or information may be sent to servers.
The information may be described as anonymous or anonymized, but that does not automatically mean you should stop asking questions about it.
Once information leaves your device, you should know where it goes, why it is being sent, and what happens to it.
AI keyboards
This is where things get even more interesting.
AI keyboards can work in very different ways.
Some may send information to an AI model whenever you type. Others may only send something when you specifically request an AI feature. Some can process certain features locally.
So when someone says, "It's an AI keyboard," that does not tell you enough.
You need to know when the AI is actually being used and what information is sent to it.
What I decided when I built FlickReply
When I started building FlickReply, I wanted one simple principle:
The keyboard should be dumb by default and smart only when you ask it to be.
That idea became the foundation of how FlickReply works.
Ordinary typing stays local
When you are simply typing a message, writing a note, entering a URL, or doing anything else that does not require an AI feature, FlickReply is just a keyboard.
Your ordinary typing stays on your phone.
There is no reason for the keyboard to quietly send your messages somewhere just because you are using it.
AI features activate when you ask
The AI features work differently.
If you tap the smart reply button, that is a clear request for AI assistance. The conversation on your screen can then be sent to an AI model to generate the response.
If you tap the polish button, the message you have written can be sent for rewriting or improvement.
The important part is that you initiate the action.
The keyboard is not supposed to quietly upload your messages in the background while you are simply typing.
You ask for AI help, and then the AI feature is used.
Privacy mode
I also wanted something that was extremely simple.
So FlickReply has a Privacy Mode.
One tap turns off the AI features.
The keyboard continues working normally. You can still type, use emojis, and access your clipboard history.
The difference is that the AI features are turned off, so nothing needs to be sent to an AI service.
I use this mode myself when I am entering things like passwords, banking information, or anything else I do not want an AI model to see.
It is not complicated.
There is no need to search through multiple settings.
One tap and the AI features are off.
Your data should not be the product
This was another principle I wanted to keep simple.
We do not sell typing data.
We do not use typing data for advertising.
We do not train models on your messages.
But there is something more important behind that statement.
The architecture is designed around the same idea.
If you wanted to sell someone's typing data, you would first need to build systems that collect and store that data.
We did not build that system.
That is an important distinction.
A privacy promise is useful, but the way a product is designed should support that promise too.
How to check any keyboard's privacy claims
You might be reading this and thinking:
"Of course you are saying this. You built FlickReply."
That's fair.
You should question us.
Actually, you should question every keyboard.
Including the one you are currently using.
Here are a few simple things you can check yourself.
- Read the privacy policy
Yes, I know.
Nobody enjoys reading privacy policies.
But keyboards are different from many other apps because they can see what you type.
Look for phrases such as:
"We collect" "Third parties" "Advertising" "Anonymized"
Try to understand what information is collected, who can receive it, and whether the information can actually be connected back to you.
Don't just look for the word "private."
Look at the details.
- Check the permissions
A keyboard needs permission to function as a keyboard.
That part is normal.
But pay attention to everything else it asks for.
Does it need your location?
Does it need access to your contacts?
Does it need your microphone?
Think about whether those permissions actually make sense for what the keyboard is supposed to do.
If they don't, that's worth questioning.
- Look for a privacy mode
If an AI keyboard provides cloud-based AI features, there should be a straightforward way to turn those features off.
You shouldn't have to dig through several menus just to stop AI functionality.
A simple privacy mode gives you more control over when AI features are allowed to operate.
- Check whether you can delete your data
Another useful question is:
Can you delete your data?
If you have used AI features, can you request deletion of your interaction history?
Find out what the company says about data deletion before assuming your information disappears automatically.
- Follow the money
This is one of the simplest questions you can ask about any free product.
If a keyboard is completely free, has no paid tier, and has no advertising, ask:
How does the company make money?
There may be a perfectly reasonable answer.
But you should know what that answer is.
The privacy mode I wish every app had
I originally expected to use FlickReply's Privacy Mode occasionally.
I ended up using it more often than I expected.
For me, it makes sense when I am:
Entering passwords or 2FA codes Using banking or payment screens Scheduling medical appointments Entering sensitive ID information Having conversations involving legally sensitive topics
In those situations, I don't need smart replies or AI polishing.
I just need a keyboard.
And that's exactly what FlickReply becomes in Privacy Mode.
A keyboard.
No smart replies.
No polish feature.
No AI.
No cloud-based AI interaction.
Just typing.
It may be slightly less convenient, but sometimes having that extra peace of mind is worth it.
The bottom line
I'm not going to tell you to trust FlickReply simply because I built it.
Instead, I want you to understand how the keyboard works and make your own decision.
That's the standard I think every keyboard should be held to.
Don't blindly trust my keyboard.
Don't blindly trust Google's.
Don't blindly trust Microsoft's.
Ask questions.
Read the privacy policy.
Check the permissions.
Understand when your information leaves your phone.
And use privacy controls when you need them.
Your keyboard sees an incredibly personal part of your life: the things you type.
That makes keyboard privacy worth taking seriously.
FlickReply is designed around a simple idea:
Be smart when you need AI, and stay private when you don't.
If that's the kind of keyboard you are looking for, give FlickReply a try.
And if you choose another keyboard instead, that's okay too.
Just make sure you know what you are agreeing to.