# MapMap Nav — store privacy questionnaire answers

Draft answers for the App Store "App Privacy" nutrition label and the
Google Play "Data Safety" form, derived directly from
`privacy/privacy-policy.md`. These match what the app actually does today
(17 July 2026 build). **Treat as a draft for final legal/App Review
sign-off before submission** — the two items flagged "Reviewer note"
below are genuine judgment calls under each platform's evolving
guidance, not settled fact.

---

## App Store — App Privacy ("nutrition label")

**Does this app collect data?** No, with one narrow exception (licence
key / territory download requests — see below).

**Does this app track you (per Apple's definition — used for advertising
or shared with data brokers, linked across other companies' apps/sites)?**
No.

| Data type | Collected? | Linked to identity? | Used for tracking? | Notes |
|---|---|---|---|---|
| Precise Location | **Not Collected** | — | — | Read from device GPS, used only to render the map puck and compute on-device guidance. Never transmitted off the device. |
| Coarse Location | Not Collected | — | — | Same as above. |
| Search History | Not Collected | — | — | Search runs against the on-device territory index only. |
| Contact Info | Not Collected | — | — | No account, no sign-in. |
| User Content | Not Collected | — | — | No saved places sync, no UGC. |
| Identifiers (device/licence key) | **Collected** | Not Linked to identity | Not Used for Tracking | The app's licence key is sent with territory-download and key-verification requests to `api.mapmap.ai`, purely to check entitlement and remaining fair-use allowance. Purpose: App Functionality only. |
| Usage Data | Not Collected | — | — | No analytics SDK is integrated in this build. |
| Diagnostics | Not Collected | — | — | No crash-reporting SDK is integrated in this build. |
| Purchases | Not Collected | — | — | No in-app purchase or commerce flow. |

**Reviewer note (location):** Apple's "collected" definition centres on
data that leaves the device. Location here never leaves the device, so
"Not Collected" is the honest answer for this build — but reconfirm
against current App Store Connect guidance at submission time, and revisit
immediately if any future build adds crash reporting, analytics, or
support tooling that could bundle location.

---

## Google Play — Data Safety form

**Does your app collect or share any of the required user data types?**
Yes, limited to one item (below); no data is **shared** with third
parties in Play's sense (sent to a party outside MapMap's own
infrastructure for their own purposes).

| Data type | Collected | Shared | Purpose | Optional? | Notes |
|---|---|---|---|---|---|
| Approximate/Precise location | **No** | No | — | — | Used on-device only for map position and guidance; never transmitted. Location permission is requested at runtime (S2b in the UI spec) but the app is fully usable if declined. |
| App activity / search or browse history | No | No | — | — | Search runs against on-device data. |
| Personal info (name, email, etc.) | No | No | — | — | No account system. |
| Device or other IDs | **Yes** | No | App functionality | Required | Licence key sent with territory-download and key-verification calls to `api.mapmap.ai`, to check entitlement and download allowance. Not linked to a user identity (no account), not used for advertising. |
| Financial info | No | No | — | — | No purchases. |

**Is all user data encrypted in transit?** Yes — all network calls to
`api.mapmap.ai` use HTTPS/TLS.

**Do you provide a way for users to request data deletion?** Not
applicable in the strict sense — we hold no server-side user data to
delete (no account, no stored location/search history). State this
plainly in the Play Console "data deletion" field rather than linking a
deletion flow that doesn't apply.

**Reviewer note (location + server logs):** Play's guidance on what
counts as "collected" has shifted over time and can include data
processed only transiently in memory. Two things worth a final legal
check before submission:
1. Confirm "Location: Not collected" still holds under the current Play
   Console definitions given the app requests the runtime permission even
   though it never transmits the resulting coordinates.
2. Standard web server access logs on `api.mapmap.ai` will contain the
   calling IP address for territory-download and key-verification
   requests, as any HTTPS server's logs do. Confirm with whoever operates
   that infrastructure whether IP addresses are retained beyond routine
   operational logging, and disclose accordingly if so (see also
   `privacy/privacy-policy.md`, "What we don't collect").

---

## Where these answers come from

Every row above traces back to `privacy/privacy-policy.md`. If that
policy changes, update this file in the same change — they must never
drift apart, since both are shown to the same App Review teams.
