Do not read a short store privacy badge as proof that no information leaves a companion app. For MindCraftAI’s Linger, the Google Play data-safety panel and the linked developer policy provide materially different descriptions. Read both before deciding what you are comfortable submitting.
The store panel observed for this review said no data was collected or shared. The linked policy describes account and device information, advertising, third-party processing and possible conversation summaries. We have not inspected the backend and cannot resolve the discrepancy by assertion. A cautious sharing decision can still be made from the information available.
Ask what each document actually describes
A store panel is a compact declaration. A policy provides a longer account of categories, purposes, processors and retention. Neither is a personal audit of your device or a guarantee that a particular request has already been carried out.
Read the policy linked from the correct app listing. This matters because several unrelated products use the Linger name. The product covered here has the Google Play package ID com.linger.ai.girlfriend.chat.talk.love and is published by MindCraftAI Apps.
Do not import the privacy promises of another companion, even one with the same name. A statement about a different operator says nothing about this app’s storage, advertising or model providers.
Trace the feature you want to use
Instead of trying to judge “privacy” as one all-or-nothing label, ask what a particular action could involve.
| Action | A useful question |
|---|---|
| Writing a message | What text is processed to produce the reply or maintain context? |
| Using voice input | Is the feature dictation, an uploaded voice note or a live call? |
| Attaching an image | Who processes the attachment, and do I have the right to submit it? |
| Watching an ad | What advertising or device information does the policy describe? |
| Deleting an account | Which records are removed, and which have separate retention? |
The linked policy identifies providers for authentication, advertising, chat and image processing, as well as technical diagnostics. It also distinguishes local history from possible server-side summaries. These are the developer’s descriptions, not independently tested data flows.
Do not confuse microphone features
The policy describes microphone use for on-device dictation, with recognized text sent as the message. That is different from an assertion that every kind of audio feature is processed locally.
Read the prompt and current feature explanation before granting a permission. A permission name alone cannot establish the complete path of every input or output. You can choose to keep using text if you do not need another mode.
The same principle applies to the camera. The policy describes a photo attachment feature. Do not include someone else’s face, documents in the background or location information merely because a photo is easy to take.
Reduce the information a conversation needs
Many conversational tasks work with less identifying detail. You can say “a colleague” instead of using a name, “a busy workplace” instead of naming an employer, and “a town I visit” instead of giving a precise address.
For a fictional scene, use invented people and places. For a discussion of an ordinary decision, remove facts that do not change the question. A model does not need a bank statement, identity document or another person’s private messages to help you explore a harmless hypothetical scenario.
This is data minimization in practical terms: keep the detail that serves the task and omit the detail that merely makes you identifiable. It does not certify the service’s security, but it limits what you choose to submit.
Ask a narrow question when something remains unclear
If the discrepancy affects your decision, use the developer’s official support contact to ask about the specific category. For example: “Does the app retain a server-side summary after I remove the visible local chat?” Avoid sending the full conversation just to ask that question.
If you want to remove information, use the current in-app process or the policy’s data-request route and keep a private record of your request. Do not claim an outcome until you receive appropriate confirmation. The history and deletion guide helps separate those actions.
Until the public descriptions are reconciled, avoid absolute claims such as “nothing is collected” or “everything stays on my phone.” You can keep the conversation useful while choosing a smaller, less identifying set of inputs.
Sources and scope
Checked October 29, 2026: the correct Linger Google Play listing and its linked MindcraftAI privacy policy, dated May 23, 2026. The public disclosures differ; no backend inspection, traffic analysis or individual deletion test was performed. This is a practical reading guide, not a legal or security certification.