And after a followup question:

```markdown

Reasons it's relatively privacy-respecting:

• On-device storage: Chat conversations and message content stay in local DataStore storage -- they are not sent to Google or any remote server.
• On-device inference: The AI inference runs entirely locally, so your prompts and responses never leave your phone.
• Optional analytics: Firebase Analytics is optional at build time (the google-services plugin is disabled by default), meaning a self-built version from source could ship without any Google analytics at all.
• Open source: The code is open source, so all of this is auditable -- there's no hidden telemetry you can't find.
• Local credential storage: OAuth tokens and API keys are stored locally, not transmitted anywhere except to the relevant service (HuggingFace).

Reasons for caution:

• Pre-built analytics: If you install a pre-built version (e.g., from an app store), it likely DOES include Firebase Analytics, meaning Google receives events about which features you use, which models you download, and when errors occur.
• FCM push notifications: FCM is active, which means Google can send your device messages with deeplinks -- this is a potential attack surface.
• Arbitrary MCP servers: The app can connect to arbitrary MCP servers configured by the user, and those servers could exfiltrate data -- the app doesn't appear to sandbox or audit those connections.
• Local token vulnerability: HuggingFace OAuth tokens are stored locally but grant access to your HuggingFace account; if the device is compromised, those tokens could be extracted.
• Account visibility: The GET_ACCOUNTS permission gives the app visibility into what Google accounts are on the device.
• Benchmark data: Benchmark performance data (model speeds, device info) is stored locally and could theoretically be included in analytics.

Bottom Line

For an app made by Google, it's better than you might expect. The core value proposition -- on-device AI -- means your actual conversation content stays private. But if your concern is "does Google get data about me," then yes, a standard build sends them analytics about your usage patterns. If you built it from source without google-services.json, you'd eliminate that entirely.

If you're privacy-sensitive, the open-source nature is the biggest asset -- you can verify exactly what's happening and build a version without the analytics. ```