Can I trust Grok?
This app did not meet two or more trust checks, has a critical issue in one, or has a red flag.
- What it means for you
- The app includes code to pass usage and interaction data to Mixpanel, AppsFlyer, and Braze for analytics, attribution, and marketing engagement. Login tokens are stored in the protected Android credential store, isolated from other apps. Google Analytics is configured to exclude advertising identifiers, and support chat identity data is encrypted with hardware-backed storage.
- Main concern
- Mixpanel session replay includes code to transmit all AI conversation content to a third party at 100% sampling
- The developer's description
- Grok is an AI-powered assistant, developed by xAI, designed to be maximally truthful, useful, and curious. Get answers to any question, generate striking images and videos, engage in natural conversations with voice mode, and upload pictures to gain a deeper understanding of your world. With Grok, t
- Third-party services
- 20
- Findings rated low or higher
- 7
Open on Google PlayOpens the app's listing on Google Play in a new tab.
Full findings
Open this scan in your dashboardThe account that ran this scan sees every finding and the Rescan button there.
Trust checks
Secure by Design
Items recorded, result pending reviewSecurity gaps detected
Why this result
This check looks for security issues at high severity or above in the code of this build, and at least one was recorded. Issues of this kind include a credential or token another app on the device can reach, sensitive data stored without protection, and network paths that expose information in transit.
Data Minimization
One criterion not metTracking lacks clear disclosure
Why this result
This build contains analytics or attribution code written to send data to companies other than the developer. No consent step was found before that code runs, and the app's disclosures do not describe the collection in full. Tracking by itself is ordinary; what this check reports is the combination of collection, recipient and absent disclosure.
Manifest Mismatch
One criterion not metDisclosure incomplete or contradicted
Why this result
The check compares the app's privacy disclosures against what the code does, and at least one claim did not match in this build. Mismatches of this kind include a data category collected but not disclosed, a recipient the disclosure omits, and an identifier attached to data the disclosure describes as anonymous.
User Control
StrongNo lock-in
Why this result
The check looks for a way to export the data an account has accumulated and a way to delete the account itself. In this build, either both were found, or the app has no account of its own and keeps its data on the device. For an app without an account, the developer has no server-side copy to export or delete, and deleting the app removes the data in its own storage.
The app includes in-app account deletion that schedules full removal of the account and all conversation data within 30 days, along with separate options to delete all conversation history and all generated media. No proprietary local data formats, export barriers, or artificial switching obstacles were identified. Authentication credentials are stored in the Android system credential store and are not trapped in a proprietary format.
Strengths
- All app traffic uses HTTPS or TLS — no plaintext network connections are possible
- Certificate validation is implemented correctly with no SSL bypass patterns found
- Login tokens are stored in the Android system credential store, protected from backup and other apps
- Google Analytics is configured to not collect the advertising ID or ad personalization signals
- Support chat identity data is encrypted with hardware-backed AES-GCM via Android Keystore
What the app contains
20 services
Third-party services the scan names in the build:
- Mixpanel
- AppsFlyer
- Braze
- Castle Highwind
- Firebase Analytics
- Firebase Crashlytics
- Firebase Messaging
- Firebase Remote Config
- Firebase Performance
- Firebase Sessions
- Google Play Billing
- Google Play Integrity
- Google Maps
- Google Places
- Google Sign-In
- LiveKit
- Ably
- Auth0 JWT
- Intercom
- PairIP
Libraries
| Library | Version | Advisory |
|---|---|---|
| ExoPlayer / media3 | not recorded | none confirmed |
| Room | not recorded | none confirmed |
| Google Play Billing | not recorded | none confirmed |
| AppsFlyer | not recorded | none confirmed |
| Auth0 | not recorded | none confirmed |
| Braze | not recorded | none confirmed |
| Glide | not recorded | none confirmed |
| Datatransport | not recorded | none confirmed |
| Google Sign-In | 12451000 | none confirmed |
| Google Play Services | 12451000 | none confirmed |
Show all 29 librariesShow fewer
Changes since the previous scan
- Version 1.2.21-release.01 (versionCode 11221201), score 82.
- Score 72 before, 82 after.
- Version 1.1.17-release.00 (11117000) before, 1.2.21-release.01 (versionCode 11221201) after.
- Score change since version 1.1.17-release.00 (11117000): +10 points.
- Since the previous scan: 15 findings added, 5 removed.
- Version 1.1.17-release.00 (11117000), score 72.
- First public scan of this app.
Method and limits
Static analysis: the decompiled code, manifest and resources of this build, read file by file. Network traffic at run time is established by a capture of the running app.
- Build SHA-256
- 2f4b0ea03710a26ae6dbd58c3921a49d72dd3e40a96a702a89f11f28f996654c
- Rule pack
- citt-ruleset-2026-08-v1
- Files decompiled
- 31,725
- Scan date
- 13 August 2026
Corrections
No correction is published for this app.
Developer response
No response is published for this app.
Report an error Opens an email to [email protected] that names this app and this scan.