Privacy is not one feature: a plain-English comparison of offline AI claims, cloud processing consent, local history, export, and deletion for African-language voice tools.

Privacy for an African-language voice tool has several separate parts: where your voice and text are processed, what permission is requested, whether chats remain on your phone, and how you can take or remove your data. Check each part before relying on an “offline” or “private” claim, especially when a conversation includes health, money, family, or work details.

Start with the processing claim

“Offline AI” can mean different things. It may mean the tool can open without a connection. It may mean some tasks run on the device. It may mean voice recording happens locally before a request goes elsewhere. The phrase alone does not tell you where your spoken Twi, Ghanaian English, or mixed-language prompt is processed.

Look for a direct answer to these questions:

• Does the conversation work with no internet connection?
• Does the app send voice audio, transcribed text, or both to a cloud service?
• Which features require cloud processing?
• What happens when the connection drops?

A tool that needs the cloud for a reply can still offer useful privacy controls. It should say so plainly. Do not assume that a microphone icon means the whole interaction stays on your device.

For voice tools, the distinction matters because a recording may contain more than the question you meant to ask. A busy trotro, a child speaking nearby, a name called across the room, or a phone notification can become part of the audio. Before using voice mode for sensitive topics, find out what leaves the device and when.

Check consent at the moment it matters

A single privacy policy checkbox at sign-up gives you little control when every new conversation has a different level of sensitivity. Good consent controls make the cloud decision visible before a request is sent.

The useful options are easy to understand:

• Never: do not send this kind of content to the cloud.
• Ask each time: let you decide for every request.
• This session: use the same choice until you end the session.

Each setting has a tradeoff. “Never” may prevent cloud-dependent replies. “Ask each time” gives you close control, though it adds a decision before you speak. “This session” reduces repeated prompts when you are discussing something ordinary, such as practising phrases or drafting a message.

Read the prompt itself. Does it explain what will be sent? Does it show the consequence of declining? A vague “Continue” button can hide an important choice. Clear language should tell you if the app will send audio, text, or both, and should let you stop before transmission.

Nkomo provides cloud-consent choices for never, ask each time, and this session. That is particularly useful for conversations that move between casual Twi practice and something more personal. For a closer look at voice interaction and consent, read The Three Jobs Behind Hold, and What Cloud Consent Can Cost You.

Separate local history from cloud processing

A tool can send a request to the cloud and still keep its visible chat history only on your device. These are different questions. Local history affects what remains available on the phone after the conversation. Cloud processing concerns what was needed to generate a response.

Check the history setting with the same care you give cloud consent:

• Is history stored on the device, in an account, or both?
• Can you turn it off before starting a sensitive conversation?
• What happens to existing history when you turn it off?
• Is deletion immediate, or does the app describe a waiting period?

“History off” should have a clear result. With Nkomo, turning off on-device history purges it immediately. That gives you a practical boundary: use history when saved context helps, then turn it off when you no longer want those chats retained on the device.

Local storage still needs ordinary phone security. Use a screen lock, avoid sharing an unlocked phone, and consider who can access device backups. A private app setting cannot protect a conversation if someone can open your phone and read it.

If you want to think through the difference between practising language and keeping the practice record, What Happens When You Want Twi Practice to Stay on Your Device? offers a useful starting point.

Test export and deletion before you need them

Privacy control includes leaving. An app should let you export your data in a usable form and request account deletion without a long email exchange or a hidden support route.

Before you build months of conversations into a tool, check:

• Can you export your data in one step?
• Does the export include the information you expect to keep?
• Can you delete the account from the app?
• Does the deletion flow explain what it removes and what you should save first?

Export protects your ability to move or retain your own record. Deletion protects your ability to stop using the service. They solve different problems, so look for both.

Nkomo offers one-tap data export and account deletion. Export first if there is anything you want to keep. Then review the deletion screen carefully, because deletion may be final.

Use a five-minute privacy check

Install the app, open its privacy settings, and run one ordinary test conversation before sharing anything sensitive. Find the cloud-consent control. Turn history on and off to see what changes. Locate export and deletion. Try a connection-dependent feature with your internet off, if the tool presents itself as offline.

Then decide what belongs in voice mode. A simple request such as “How do I say this politely in Twi?” has a different risk from a conversation containing a diagnosis, payment detail, or family dispute. Choose the setting that fits the subject before you hold the microphone.