Gemini (Google) (com.google.android.apps.bard): Privacy & Security Findings

report - rfi-irfos
Skip to content

Permanent Disclosure Ledger

The discipline, demonstrated

On behalf of our research partners, we investigate publicly distributed Android and iOS apps: we decompile them, follow their code and data flows, and trace every connection to the servers it reaches. Hundreds of agents work through each app and join the technical evidence into one picture, which our specialists then review and verify.

387+
Android/iOS apps audited
Every app is decompiled at source-code level, not just scanned from outside.
1.04M+
Smali classes read
The full shipped code we have actually read, not an estimate.
262+
Critical findings recorded
Confirmed findings copied to regulators, not theoretical risks.
970+
Weak points found
Third-party tracking we have provably found inside the binary.
567+
Endpoints investigated
Real servers and countries where data actually flows.
132+
SDK instances mapped
Reusable libraries correlated across the entire corpus.
1 of 387 entries · sorted by elapsed ↓
Showing the report for Gemini (Google).
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Gemini (Google)
NASDAQ
2026-06-26
91d ago
Silent
High
Gemini has none of the tracking SDKs, hardcoded keys, or pre-consent trackers found in nearly every other app in this series, a genuinely clean build. But its conversations, including ones about medical, mental-health or political topics, travel with no certificate pinning, meaning a company-issued certificate on a work phone could read them, and every conversation is permanently tied to your full Google account, with no option for a private, unlinked chat.
com.google.android.apps.bard. Zero third-party tracking SDKs, zero hardcoded credentials, zero pre-consent auto-init - the cleanest of 58+ apps audited in this series. Still: no android:networkSecurityConfig declared, meaning no certificate pinning for gemini.google.com, so an enterprise MDM-pushed certificate can read conversation traffic on a managed device, conversations that routinely include Art. 9 special-category data. WebView permission prompts attribute camera/mic access to the browser, not Gemini. Clearcut + usagereporting behavioral telemetry has a ConsentVerifier library present but no visible consent-gate hook in the binary. Every conversation is mandatorily linked to the full Google identity graph (Gmail, Search, Maps, YouTube, Calendar, Drive), no pseudonymous mode. Four messages sent across 72 days to privacy@/security@google.com; one automated bug-bounty triage bot reply, no human reply ever. BCC: DSB + CERT.at + UK ICO. Case closed and published 2026-09-25, one day after the stated 2026-09-24 embargo.
click to expand
GDPR Art. 32(1)(a)GDPR Art. 6(1)(a)GDPR Art. 5(1)(c)
Yes
Closed
Disclosure
91d 00h 00m 00s
Published
PDF

This ledger is updated in real time as companies respond. Silence is public. Severity is scored primarily by CVSS v4.0, we reserve the right to deviate based on blast radius.