Contacts
Messaging · declared: 0 data types collected, 0 shared No tracking declared
Sensor & data access crowdsourced
iOS itself recorded these accesses on donors' iPhones — how many times the app touched each privacy-protected resource. Every row was reported by at least 3 separate accepted donations and published under a human verdict (rows arriving after an app's evidence was approved inherit that verdict). Counts are totals across the donated reports; access times are never collected.
| Resource | Donations | Accesses | Seen |
|---|---|---|---|
| Contacts | 4 | 166 | 2026-07-29 → 2026-07-30 |
How to read this
- A contact is a measurement, not an accusation. iOS records that the app (or code inside it, like an ad or analytics SDK) reached the domain. It does not show what data was sent.
- Counts reflect the donors' usage. A heavily-used app produces more contacts; compare domains within this app, not across apps.
- Separate donations, not proven separate people. Donations are anonymous by design, so we can count donations — we cannot prove three donations came from three donors. Human review weighs that before anything publishes.
- "Not in label" is the finding that matters. It means measured behavior with no matching disclosure in the app's own store privacy label — the declared-vs-observed gap this database exists to expose.
Domain owner/type attribution from Apple's App Privacy Report where the donor's export carried it; tracker classification via the AdGuard companiesdb (CC BY-SA 4.0). You can add to this evidence: donate your own App Privacy Report — parsed in your browser, shared only with your per-app consent, accepted anonymously (no account, no email, no IP address stored).
Think something here is wrong?
Evidence and research improve when people push back. Tell us what to re-check — a misattributed domain, an outdated classification, a claim about your own app — and a human will review it. Responses can take up to 30 days.