Can I trust Anker soundcore?
This app did not meet one of the trust checks that applied to it, with no red flags.
- What it means for you
- The build includes code to send biometrics to soundcore/Anker cloud, and files to soundcore Anka AI. The build includes code to send another 4 data points to other third parties. Two findings are worth reading before this build handles anything a user would want kept to themselves. One is a high severity finding related to Network Security. One more is an open question the analysis could not settle.
- Findings rated low or higher
- 49
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
One criterion not metSecurity 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
StrongTracking done right
Why this result
The check looks at analytics and attribution code for companies other than the developer: the data it reads, the companies named in code as recipients, and whether a consent step runs before that code. In this build, either no such code was recorded, or a consent step runs before it and the app's own disclosures describe the collection.
Every Google analytics, crash reporting, performance and messaging channel in the app is switched off in the app's own configuration and stays off until code turns it on, which means nothing is reported automatically at first launch. The app opens with a welcome screen that asks the user to read the Terms of Use and Privacy Policy and tap Agree and continue before proceeding, and settings carry a Share App Analytics switch that plainly states what diagnostics and crash data are collected and how to turn it off, alongside a The user's Privacy Choices screen. The AI features that include code to send data onward are behind their own separate agreement dialog, and cloud sync of notes is behind an explicit toggle the user has to enable. No collection was found that runs ahead of those gates.
Manifest Mismatch
StrongEverything visible
Why this result
The check compares the app's privacy disclosures against what the code does: the data categories collected, the companies named in code as their recipients, and the identifiers attached to each. The comparison covers the store listing, the in-app privacy text and any privacy manifest shipped in the build. Every claim compared matched the code here.
The app's own disclosures line up with what the code does, and in places go further than most. A dedicated AI Features and Data Sharing notice names the outside processors by name, Azure AI and OpenAI, lists exactly what goes to them including voice commands, audio recordings, text submitted for translation or summarization, and device model and region, and states the data is not used for advertising or sold on. A separate notice covers AI translation and gives deletion contact addresses. The recording features state that audio is encrypted in transit and that temporary cloud copies are deleted after transcription. The voiceprint feature is described in its own opt-in text, including that voice characteristics are derived from a cached recording segment and held in encrypted cloud storage for recognition only, with a delete path. Analytics and crash reporting are described in the settings text that controls them, and the bundled open source component notices ship with the app.
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 has a working way out. Account deletion is a real in-app flow, confirmed by email with a verification code, and the recordings side of the app can export audio, transcriptions and summaries to files in a choice of formats that can be saved anywhere on the phone and shared. Sleep and listening data sit in ordinary formats rather than a closed one, and nothing was found that obstructs leaving the service or holds data hostage.
What the app contains
The scan kept no list of third-party services for this build.
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
- 088a17777e755e92a71e679ecf2f2372408a4dbbdb895f65cee8ba18f59fc019
- Rule pack
- citt-ruleset-2026-08-v1
- Files decompiled
- 300
- Scan date
- 10 September 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.