Understand location permissions.

The published consumer policy describes precise or approximate location while the app is open and, if background or Always access is granted, periodically or continuously when it is not open.

Frequency and accuracy depend on the device, operating system, connectivity, settings, and use. A permission is not a guarantee of a particular update frequency.

The policy describes uses including nearby agencies, geographic alerts, tip context or routing, safety, security, diagnostics, and product improvement. Read the full policy for the purposes and disclosure circumstances.

When you choose a current-location option for a submission, you direct that location to the selected participating agency. Text and media can also reveal where something happened even without a location attachment.

You can review operating-system permission and eligible in-app choices. Revoking permission changes future access but does not automatically delete prior information. Limited profile visibility does not disable location collection.

Lucas location features are not an emergency dispatch or hazardous-navigation system. Use the appropriate emergency channel when assistance is urgently required.

Your device’s current position, a place selected in an app and the location of something you observed may be different. If you are reporting an earlier observation, make the relevant place and time explicit. A current device coordinate alone may not explain where the event happened.

Location can be useful context, but it can also reveal a private routine or address. Review the permission request and the information being attached. The published policy describes permitted location use, including background access where granted. Do not assume that following an agency or changing a profile preference answers every location question.

For a particular contribution, consider why location is relevant and which agency is intended to receive it. A description such as a named entrance or an approximate intersection may explain an observation differently from a precise device coordinate. Use the options actually supported by the feature and be clear about uncertainty.

Later changes to permission affect future device access in accordance with the platform and feature behavior. They do not retrieve information already delivered to another organization. Keep that distinction in mind when choosing what to share, and read the agency-records explanation for what happens after delivery.

A device permission can allow an app to obtain the phone’s location. A place in a tip can describe where an event happened. A followed department can represent an area whose updates a person wants to read. These are related to geography, but they do not necessarily describe the same place or time.

For example, someone could read a request from a workplace department while they are at home, then describe an observation made earlier somewhere else. The relevant place belongs with the observation. The phone’s current position is a different piece of information.

When you review a permission or a submission, identify which kind of location is being used and why. Do not assume that changing one choice removes every location already supplied in another form.

Source: Lucas Privacy Policy, effective September 14, 2026

The Privacy Policy describes precise or approximate device location when permission is granted, including background access when allowed. Device settings and the current feature determine the options presented to the user. Read the actual prompt instead of assuming all location permissions have the same scope.

Changing a device permission can affect what the service can obtain going forward. It does not automatically remove a place included in a previous account or an attachment already delivered. Profile visibility is also a separate control.

If you need help, describe the device, the setting and the use you are asking about. You can ask a policy question without sharing your own precise location. Avoid sending a sensitive example when a general explanation would answer the question.

Source: Lucas Privacy Policy, effective September 14, 2026

A building name, street sign, camera view or detailed description can reveal a place. Even a file that has no obvious map marker can contain location clues in what it shows. Consider those clues alongside any explicit location field.

For a useful tip, explain the place relevant to the observation and distinguish it from where you are now. Include only what is needed to understand the account. If the available feature cannot represent the situation clearly, ask the agency for its preferred reporting route.

This page explains the choices and limits described in the consumer policy; it does not certify the location controls of a particular app release. The policy and the options shown in the current product should be read together.

The recipient may need the event’s location without needing a complete account of your movements. Describe the observation you are reporting, and ask for clarification if a requested detail seems unrelated to that task.

Source: Lucas Privacy Policy, effective September 14, 2026