1. On July 15, 2026, Google Play announced additional guidance for declaring precise and approximate location in the Data Safety form; this is a clarification of the existing policy, so enforcement standards remain unchanged; 2. Precise location means data that identifies a user's exact whereabouts within a few meters, typically collected through GPS, ACCESS_FINE_LOCATION, or device sensors; 3. Approximate location means data that only identifies a general area such as a city or neighborhood, typically collected through ACCESS_COARSE_LOCATION, IP addresses, or Wi-Fi/BSSID signals; 4. In the Data Safety form, select the Location data type and tick every category you actually collect - precise, approximate, or both - then state the purpose and whether the data is shared with third parties; 5. Location derived from IP address, Wi-Fi, or other signals must still be declared as approximate location even if your app requests no location permission; 6. In practice, request precise location only when the core feature truly needs it and offer approximate location where possible; runtime permission prompts should explain the reason in context; 7. Action item: review your Data Safety form and privacy policy against the new guidance - per the announcement you have at least 30 days from July 15, 2026 to bring app updates into compliance.