Waze
Utility location · declared: 16 data types collected, 1 shared No tracking declared
Measured network activity crowdsourced
Observed in donated App Privacy Reports — measured on real iPhones by iOS itself, not declared by the developer. Every row below was reported by at least 3 separate accepted donations and published under a human verdict — rows marked inherited verdict arrived after a reviewer approved this app's evidence and inherited that decision. Contact counts and dates are aggregates across the donated reports.
| Contacted domain | Company | Classification | Donations | Contacts | Seen |
|---|---|---|---|---|---|
ctilesgcs-am.waze.com |
— | first-party | 7 | 116 | 2026-07-28 → 2026-07-30 |
adsassets.waze.com |
— | first-party | 7 | 83 | 2026-07-28 → 2026-07-30 |
firebaselogging-pa.googleapis.com |
Google LLC 1 |
analytics | 7 | 81 | 2026-07-28 → 2026-07-30 |
rt-xlb-am.waze.com |
— | first-party | 7 | 81 | 2026-07-28 → 2026-07-30 |
tts-assets.voice.waze.com |
— | first-party | 7 | 79 | 2026-07-28 → 2026-07-30 |
wig-am.waze.com |
— | first-party | 7 | 73 | 2026-07-28 → 2026-07-30 |
ads-resources.waze.com |
— | first-party | 7 | 68 | 2026-07-28 → 2026-07-30 |
cres.waze.com |
— | first-party | 7 | 68 | 2026-07-28 → 2026-07-30 |
cresg.waze.com |
— | first-party | 7 | 68 | 2026-07-28 → 2026-07-30 |
inbox-am.ingress.waze.com |
— | first-party | 7 | 67 | 2026-07-28 → 2026-07-30 |
firebaseappcheck.googleapis.com |
— | unknown | 7 | 47 | 2026-07-28 → 2026-07-30 |
sdk.waze.com |
— | first-party | 7 | 19 | 2026-07-28 → 2026-07-30 |
firebase-settings.crashlytics.com |
Google LLC 1 |
analytics | 7 | 16 | 2026-07-28 → 2026-07-30 |
renderer-am.waze.com |
— | first-party | 7 | 15 | 2026-07-28 → 2026-07-30 |
firebaseremoteconfig.googleapis.com |
Google LLC 1 |
unknown | 7 | 10 | 2026-07-28 → 2026-07-30 |
firebaseinstallations.googleapis.com |
— | unknown | 7 | 7 | 2026-07-28 → 2026-07-30 |
is1-ssl.mzstatic.com |
— | cdn | 7 | 7 | 2026-07-28 → 2026-07-30 |
itunes.apple.com |
— | unknown | 7 | 7 | 2026-07-28 → 2026-07-30 |
gapi.waze.com |
— | first-party | 4 | 8 | 2026-07-28 → 2026-07-29 |
www.google.com |
— | unknown | 4 | 8 | 2026-07-28 → 2026-07-29 |
venue-image.waze.com |
— | first-party | 4 | 4 | 2026-07-28 → 2026-07-29 |
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 |
|---|---|---|---|
| Location | 4 | 32 | 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.