Little Sprouts ABC
Mobile app · Bramble Kids Studio · com.example.sprouts
- App identifier
- com.example.sprouts
- Publisher
- Bramble Kids Studio
- Platform
- Android
- Versions
- App 5.1.2 · Android 13
- Scan date and region
- Apr 30, 2026 · US-East (Virginia lab)
- Consent state
- Parental gate accepted; rejection not offered in app
- Scan method
- Lab device — authorized runtime traffic capture
- Coverage
- Partial · methodology 0.8
Observed connections (4 endpoints, 4 companies)
Each row is a transmission observed in the tested session, the operator identified for that endpoint, and the information seen in requests. This table is the accessible equivalent of the data-sharing map.
| Observed endpoint | Identified operator | Role | Scenarios | Information observed |
|---|---|---|---|---|
ads.adreach.exampleContents not readable | Adreach Exchange Declared | Advertising services |
| Network information only; contents unknown |
collect.tallymark.example | Tallymark Analytics Declared | Analytics and measurement |
| Usage & viewing, Identifiers, Network |
api.orbitalcloud.exampleContents not readable | Orbital Cloud Declared | Content delivery and infrastructure |
| Network information only; contents unknown |
cdn.nimbuscdn.example | Nimbus Edge Declared | Content delivery and infrastructure |
| Network |
Documented relationships
Ownership and business relationships come from public records. They do not show that data from this product moved between these companies.
Adreach Exchange → Meridian Media Group
DeclaredDocumented ownership
Source: Meridian Media Group annual report 2025, list of subsidiaries · Mar 2, 2026
Adreach Exchange → Tallymark Analytics
DeclaredDocumented business relationship
Source: Tallymark integrations page lists Adreach · May 14, 2026
Unknown Further sharing unknown
TrustIQ observes what leaves the product. What recipients do afterward, including onward sharing, is outside what this scan can see.
Open questions
Orbital Cloud
- Orbital Cloud hosts services for many customers. Which customer operates the contacted subdomain, and for what purpose, is not established.
Nimbus Edge
- Content delivery contact establishes where files were fetched from, not why. Purpose is attributed to the publisher, not to Nimbus Edge.