No location-sharing notice is not the same as a statement that an app shares nothing. Keep absence of a message separate from a positive privacy claim. Otherwise, the least informative screen can accidentally receive the most reassuring interpretation.
Treat an absent notice as unanswered
Google explains that these notices depend on developer data-safety information and support from stores or manufacturers. Developers are responsible for the declarations. Absence of the notice does not establish absence of sharing. Google's documented controls.
Compare two fictional app screens
App A displays a location-sharing notice with a stated purpose. App B displays no notice during your observation. Create two rows: A, notice shown, purpose as stated; B, notice not shown, purpose unknown from this screen. Do not rank B as safer based on the empty field.
The opposite accusation would also be unjustified. An empty field is not proof that B secretly uploads location. Leave that question unanswered rather than replacing a reassuring guess with an alarming one. The record should reflect what was available, not how suspicious the reader feels.
If A includes an information box, inspect that visible box and distinguish its words from your interpretation. For B, a useful follow-up question is: What location use or sharing purpose is declared for this app, if any? This asks about the product's stated practice, not about the person's current location. There is no need to send a location pin to demonstrate that a notice was absent.
Preserve the limits when sharing findings
A careful summary for B is: no notice was shown in this observation, so this screen did not confirm the declared purpose. Add enough context to distinguish the app and device checked. Do not extend one observation to every installation, store or device.
For A, preserve the declared wording as a declaration rather than calling it an independently verified account of actual transfers. If the two observations concern different app versions or sources, note that difference before comparing. This approach prevents missing information from becoming an unsupported promise or accusation.
For a separate reading task, see our guide to checking unclear game-screen information; it is not the source for Android controls.