NearBe

NearBe Privacy Policy

Last updated: 28 July 2026

This policy covers the NearBe Android app (“NearBe”, “the app”), developed by Alberto Dino Biafelli, trading as DinoSoft Ltd (“we”, “us”). It explains what data the app uses, why, and how you can control it.

Contact: dinosoft.uk@gmail.com

1. The short version

NearBe stores your pins and settings only on your phone. We don’t run a server, we don’t have user accounts, and we don’t sell your data. The only place your location is shared outside your device is with Google Maps, to render the map on screen (see Section 3). The app uses your location — including in the background — to tell you when you’re near a place you saved, or near a type of place you asked it to watch for.

2. Data we use

Location data (including background)

NearBe collects device location, including when the app is closed or not in use, to power its core feature: alerting you when you are near a saved pin or a matching place type (for example, “vintage shop”). Without background location, this feature does not work.

We also use the Activity Recognition API to detect whether you’re still, walking, or driving. This lets the app skip location checks when you’re not moving, saving battery. Activity data is used on-device only and is not stored beyond what’s needed to decide whether to check your location.

Pins and preferences

Pins you add (map coordinates, label, radius, and any place-type you choose to watch for) are stored in a local database on your device. This data does not leave your device except as described in Section 3.

Cached place data

To find nearby shops or places by type, NearBe stores a local copy of relevant OpenStreetMap data for areas you’ve been near. This is public map data, not personal data, and is used only to match against your chosen place types.

Notifications

NearBe generates notifications locally on your device to alert you about nearby pins or matching places. We do not use a third-party push notification service.

3. Third parties

NearBe uses the following services to function. We don’t control their data practices — see their own privacy policies for details.

Google Maps SDK: renders the map you see in the app. To do this, your approximate or precise location and map viewport are sent to Google’s servers when you have the map open — this is the one case where location data leaves your device. Governed by Google’s Privacy Policy.
Google Play services (Location, Activity Recognition, Geofencing): used on-device to detect your location and movement and to trigger geofence alerts. These run locally via Play services; they do not send your location to Google as part of this functionality. Governed by Google’s Privacy Policy.
OpenStreetMap: source of place data. We download and store OSM extracts locally; no personal data is sent to OSM.

We do not use analytics SDKs, advertising SDKs, or any service that shares your data for ad targeting. We do not sell your data.

4. Data retention

We do not operate a backend server, do not keep a copy of your data, and do not retain any data after you delete it or uninstall the app. Retention works as follows, by data type:

Location data: Not logged or stored. Your location is read to evaluate geofences and activity state, used immediately for that check, and then discarded. NearBe keeps no location history.
Pins and preferences: Kept in a local database on your device for as long as you keep the app installed, or until you delete the individual pin. Deleting a pin removes it immediately and permanently.
Cached place data (OpenStreetMap): Kept locally on your device and refreshed periodically when you’re on Wi-Fi to keep it current. It is not linked to your identity and is cleared when you clear the app’s storage or uninstall it.
Notifications: Generated on-device and not stored once shown; no notification history or log is kept.

Uninstalling NearBe, or clearing its storage in Android Settings, deletes all app data immediately. Nothing is retained on our end because nothing is ever sent to or held by us.

5. Your controls

Location and Activity Recognition permissions can be changed anytime in Android Settings > Apps > NearBe > Permissions.
Background location can be revoked; the app will then only work while open (foreground), and background alerts will stop.
You can delete pins individually in-app, or remove all data by uninstalling the app.

6. Children

NearBe is not directed at children and we do not knowingly collect data from children under 13 (or the minimum age in your region).

7. Your rights (UK/EU users)

Under UK GDPR and the Data Protection Act 2018, you have the right to access, correct, or delete your data. Since all app data lives on your device, you can exercise these rights directly by editing or deleting pins, or uninstalling the app. For questions, contact dinosoft.uk@gmail.com.

8. Changes to this policy

We may update this policy as the app changes. Material changes will be reflected here with an updated “Last updated” date. Continued use of the app after changes means you accept the updated policy.

9. Contact

Questions about this policy or your data: dinosoft.uk@gmail.com

This site is open source. Improve this page.