[question]: Avoid precise location storage

[hls-app]

How can we help?

Hi,

I am looking at enabling location using OneSignal.Location.setShared(true); but want to share only the coarse/vague location instead of the precise location. Currently, our app needs precise location for app functionality but we don't want the same for marketing/informational push notifications.

Our use cases will be limited to sending push notifications to users in that area and we don't need precise accuracy. While this may seem less harm to store precise location, we found that the location stored is accurate to meters, which we don't take consent of. We have disabled the feature for that reason but would love to enable it if any of the following options are possible:

1. Onesignal allows an extra flag to force coarse location storage only. Example: OneSignal.Location.set(shared: true, forceCoarseLocation: true);
2. Allow us to populate the location field through API or SDK

Also, I have a question around how frequent is the location data is updated? Ours is a location based app and people could use it from different locations when travelling but at the same time can opt in to a specific city to receive updates from.

If there is an existing way to tackle this challenge, please let us know.

Code of Conduct

• I agree to follow this project's Code of Conduct

[hls-app]

https://documentation.onesignal.com/reference/update-user

Allows updating location via API.