What you need to know
A private AI app should clearly explain where prompts are processed, what leaves the device, who receives it, what is stored, and how data can be deleted. No account and local inference are useful signals, but neither proves every feature is private. Check normal chat separately from search, downloads, reports, analytics, and backups.
Privacy is a data flow, not a badge
A useful privacy review follows information from input to deletion. Identify the content involved, where computation happens, which network destinations are contacted, how long local or remote copies remain, and which controls the user has. Repeat that review for each feature because chat, document processing, web search, and support reports can have different boundaries.
Account-free access removes one direct identifier and reduces signup friction. It does not show whether an IP address, device identifier, prompt, diagnostic record, or search query reaches a server. Encryption protects data in specific states, but it does not answer who can access plaintext during processing. Precise explanations matter more than isolated privacy words.
Build evidence in layers
Begin with the privacy notice and feature documentation. Look for named recipients, stated purposes, retention periods, deletion steps, backup behaviour, and distinctions between required and optional connections. Next, test whether a fresh local conversation works with connectivity disabled. Where practical, observe network destinations without placing sensitive material into the app.
No single test settles every question. Offline generation supports a local-inference claim, but it cannot prove that previous content was never transmitted. Network observation can reveal contacted domains, but encryption can hide request contents. The strongest conclusion combines documentation, repeatable behaviour, platform permissions, and controls that you have actually exercised.