South Hoopfests
Exposure Events · Build 5.0.1
Review the recorded findings below. An overall grade is withheld where required checks lack coverage; a new scan may provide additional evidence.
Overview
6 finding categories to review
South Hoopfests (com.exposure.southhoopfests) was scanned at version 5.0.1 on 2026-09-03 but is not graded, because the analysis did not complete enough of its checks for a score to mean anything. The checks that did run recorded 6 finding categories across 8 occurrences; because the analysis did not complete, the absence of anything more severe is not a result. 4 tracking SDKs are present in the package, which describes what ships, not what runs or what it sends. This is static analysis of a single build: it does not observe the app running and does not establish that any data is exposed.
Start with these findings
mediumShips third-party ad/analytics SDKs but Data Safety declares no data shared1 occurrence
Interpretation & review guidance
The app ships third-party advertising/analytics SDKs (which typically transmit data to those third parties) yet its Data Safety label declares that no data is shared. Declared ‘no sharing’ alongside ad/attribution SDKs is a common Data Safety mismatch worth confirming.
How often Data Safety labels disagree with the package →
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
lowData Safety label omits Location2 occurrences
Interpretation & review guidance
The app's Google Play Data Safety label omits a data category it can actually access — a permission it requests, or an advertising/device identifier it references. Under-declaring collection is a Play policy issue and a COPPA/privacy concern. This is a static signal: a requested permission is capability, not proof of collection — confirm against runtime behavior.
How often Data Safety labels disagree with the package →
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
lowFirebase Realtime Database reference1 occurrence
Interpretation & review guidance
A Firebase Realtime Database URL. Nearly every app that uses Firebase ships one. It's only an exposure if the database rules are world-readable — that's what live verification checks.
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Build & components
0 components recorded. Certificate parsing does not validate APK signature integrity.
Inspect build evidence →Findings
6 categories · 8 occurrences. Severity totals describe categories. Expand a finding for interpretation and review guidance.
mediumShips third-party ad/analytics SDKs but Data Safety declares no data shared1 occurrence
Interpretation & review guidance
The app ships third-party advertising/analytics SDKs (which typically transmit data to those third parties) yet its Data Safety label declares that no data is shared. Declared ‘no sharing’ alongside ad/attribution SDKs is a common Data Safety mismatch worth confirming.
How often Data Safety labels disagree with the package →
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
data-safety:sharing- Recorded match
Pattern recorded; identifying value redacted.
1 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
lowData Safety label omits Location2 occurrences
Interpretation & review guidance
The app's Google Play Data Safety label omits a data category it can actually access — a permission it requests, or an advertising/device identifier it references. Under-declaring collection is a Play policy issue and a COPPA/privacy concern. This is a static signal: a requested permission is capability, not proof of collection — confirm against runtime behavior.
How often Data Safety labels disagree with the package →
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
data-safety:Location- Recorded match
Pattern recorded; identifying value redacted.
2 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
lowFirebase Realtime Database reference1 occurrence
Interpretation & review guidance
A Firebase Realtime Database URL. Nearly every app that uses Firebase ships one. It's only an exposure if the database rules are world-readable — that's what live verification checks.
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
resources.arsc- Recorded match
Pattern recorded; identifying value redacted.
1 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
lowFirebase Storage bucket reference1 occurrence
Interpretation & review guidance
A Firebase Cloud Storage bucket reference (the default <project>.appspot.com). Storing user files here is normal — it's only an exposure if the Storage security rules allow public read/list, which live verification tests.
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
resources.arsc- Recorded match
Pattern recorded; identifying value redacted.
1 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
lowGoogle API key (client-shipped; restriction unverified)2 occurrences
Interpretation & review guidance
Android apps are designed to ship Google API keys in the client; Google restricts them by app signing certificate + enabled API. This is only a problem if the key is left unrestricted — presence alone is expected, not an exposure.
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
resources.arsc- Recorded match
AIza•••••••• (21–40 chars, redacted)
2 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
lowOutdated target SDK (API 25)1 occurrence
Interpretation & review guidance
The app targets an outdated Android API level, which opts it out of newer platform security defaults (e.g. scoped storage, cleartext-off by default).
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Parsed app configuration
- Representative location
AndroidManifest.xml:tsdk25- Recorded match
targetSdkVersion=25
1 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
No categories match these filters. Clear the search or choose all severities.
Privacy signals
Capabilities and bundled software do not prove that data was collected or transmitted.
Precise location Approx. location
Requested permission inventory (10)
Data collection & flow (privacy signal, not part of the grade)
- Approximate location, Precise location requested while 2 ad/attribution SDK(s) are present (Google AdMob, Google AdServices) — location commonly feeds ad targeting.
- Persistent-identifier APIs referenced in code (Advertising ID (AAID), Android ID, Device ID / IMEI) with 4 analytics/ad SDK(s) present — the mechanism used for cross-app profiling.
- Calendar data requested with third-party analytics/ad SDKs present.
This maps what the app can access (permissions it requests, identifier APIs its code references) to the third parties bundled in it. It reflects capability and SDK presence — not proof that a specific value was transmitted.
Trackers & SDKs (4 detected · privacy signal, not part of the grade)
Build & components
Scanned build 5.0.1. Store metadata may describe a newer release.
c191889bcced7cd11dd0e83fdd027cdfe87dd32e72534135c4c37a6733de0628Signing certificate (who signed this build — factual, not part of the grade)
a7:4c:eb:29:ef:be:b4:40:36:59:18:03:be:57:b1:2f:f2:7e:b6:f9:2c:c4:9c:d9:0a:13:81:2a:a7:0a:4c:aaThe certificate fingerprint identifies the parsed signing certificate. Knowing this public fingerprint does not establish ownership or validate the APK signature.
Component inventory
No components recorded. Analysis is incomplete or coverage is unknown.
Export SBOMAbout this app · store information
About this app
Experience South Hoopfests events the right way!
Screenshots
Scan history
Each row is an observed scan. Gaps between scans do not establish how long a finding existed.
| Scanned (UTC) | Build | Score | Grade |
|---|---|---|---|
| 2026-09-03 05:05 UTC | 5.0.1 | 89 | B |
Export & share
Exports describe the recorded assessment. Signed evidence proves origin and integrity, not completeness or safety.
Coverage & gap matrix · Verify signed evidence
API users can request authenticated, scan-specific exports at /v1/scans/35499701-7a9e-4da1-b58e-bece068349e9/findings.sarif (also coverage.json and proof.json).
Request a correction or removal · How to interpret a scan · Browse apps