Trace companion-app data to every stated outside recipient

Define what counts as an outside recipient

Use recipient roles before hunting for company names. The app publisher is the first party. Outside roles may include cloud hosting, analytics, crash reporting, customer support, content moderation, login, payments, advertising, model or voice processing, and other integrated services. Apple describes third-party partners as analytics tools, advertising networks, third-party SDKs, and other external vendors whose code is integrated into an app. Google Play uses its own definitions and notes that a service provider processing on the developer’s behalf may not appear as “sharing.” Therefore, “no data shared” on one store panel does not necessarily mean that no outside organization processes data. It means you must read the panel using that platform’s definitions and compare it with the longer policy.

Make a data-to-recipient ledger

Create one row for each data category you might expose: registration details, profile text, conversation content, uploaded images, voice recordings, contacts, precise or approximate location, device identifiers, usage events, technical error logs, purchases, and support messages. Add columns for where the claim appears, who receives the data, why, whether it can be linked to an account or device, whether the transfer is required or optional, and how to stop or delete it. This prevents a policy sentence such as “we work with trusted partners” from seeming complete. The useful question is narrower: which partner role can receive which data for which purpose? If the document names analytics but never says whether conversation content enters analytics events, mark that connection unknown rather than assuming either outcome.

Compare both app-store disclosures with the policy

On Apple platforms, inspect the App Privacy section for data used for tracking, data linked to you, data not linked to you, and the stated purposes. Apple tells developers to include practices of integrated third-party partners. On Google Play, open Data safety and expand every data type rather than relying on its summary. Google tells developers to account for third-party libraries and SDKs, while also explaining exceptions to what appears as sharing. Store panels are developer-provided structured summaries, and the two stores use different taxonomies. Use them as navigation aids, not identical audits. Search the current policy for “share,” “disclose,” “service provider,” “processor,” “partner,” “vendor,” “affiliate,” “advertising,” “analytics,” and “SDK,” then connect each clause back to your ledger.

Follow named services and feature-specific transfers

A vendor list, subprocessor page, cookie notice, or SDK disclosure can turn a generic recipient category into a checkable path. Open only links published by the app operator or the named service, and verify that the app’s policy actually connects that vendor to the feature you plan to use. Social login can send identifiers through an identity provider; voice transcription may involve a speech processor; payment may move you to a store or separate checkout; community moderation may expose selected content to review tools or reviewers. These examples are possible roles, not claims about every companion app. Also distinguish your deliberate share action—such as exporting a message—from background transfer. Write down what triggers each route and whether you can use the core experience without it.

Use permissions and settings without overreading them

Device permissions show access that an app requests; they do not by themselves prove that information is transmitted or shared. Google explicitly distinguishes its permissions list from Data safety. A microphone permission may enable local capture, remote processing, or both, depending on the implementation and disclosure. Test with optional permissions denied, use neutral content, and observe whether the relevant feature explains why access is needed. Then inspect privacy, advertising, personalization, connected-account, export, and deletion settings. A toggle can reduce one use without deleting earlier records or stopping a different recipient path. Record the exact label and consequence instead of translating “personalization off” into “all sharing off.” Avoid network interception or unofficial scanning unless you have the knowledge and authorization to use it safely; ordinary users can make a strong disclosure audit without claiming a forensic result.

Resolve contradictions with narrow questions

If the store says no sharing but the policy lists analytics partners, first check whether the platform’s service-provider exception explains the difference. If it does not, ask support a question that contains one data type, one feature, and one recipient role: “When I use voice chat, is the audio or transcript sent to an external speech or model provider, and can I use text chat without that transfer?” Request the current policy section or settings path rather than a broad promise that data is safe. Keep the reply date and sender domain, but remove account identifiers from notes. No reply is not proof of undisclosed sharing, and a friendly reply is not technical verification. The correct audit state can be confirmed, conditional, contradictory, or unknown.

Make a decision without inventing certainty

Decide against your planned use, not against an imaginary perfect app. A weather-like location feature and a private conversation feature expose different data. You might accept technical crash records but decline advertising linkage, or use text while leaving voice and contact discovery off. Before sharing anything personal, require a clear answer for the data categories that matter most to you, a usable control for optional transfers, and an understandable deletion or exit path. If a critical conversation, image, or voice path remains unknown, postpone that feature or choose a lower-disclosure activity. Repeat the ledger after a major update, policy change, new permission prompt, or new connected service. The result is a dated evidence snapshot, not a permanent verdict about the app.

Keep exploring this topic