GeoNap

Last updated: July 12, 2026

This policy is also available online at mba-labs.com/products/geonap.

GeoNap is designed with a simple principle: your location and alarm data belong to you. This document explains exactly what information the app uses, where it stays, and what it never does.

---

Location Data

GeoNap uses your device's location exclusively to monitor geofenced regions. Location data is processed entirely on your device — it is never transmitted to any server, stored in a database, or shared with third parties.

When you create an alarm, the latitude, longitude, and radius are saved locally. This data never leaves your device unless you explicitly use the Share button, which generates a standard Apple Maps link.

The app requests "Always On" location permission so that iOS can wake the app in the background when you enter or exit a monitored region. You can revoke this permission at any time in Settings → Privacy & Security → Location Services → GeoNap.

---

On-Device Storage

All alarm data — including names, coordinates, radii, time windows, active days, and trigger history — is stored locally using SwiftData in the app's private container. This data is included in standard iOS backups (iCloud Backup or iTunes/Finder) if backups are enabled.

No account, login, or network connection is required to use GeoNap.

---

iCloud Sync

GeoNap is designed to support iCloud sync via CloudKit so that your alarms can appear on all your Apple devices signed into the same Apple ID. When iCloud sync is active, alarm records are stored in your personal iCloud container and governed by Apple's privacy policy. Apple does not use CloudKit data for advertising.

If iCloud sync is unavailable or disabled, the app falls back to local-only storage automatically — no data is lost. You can disable iCloud sync at any time in Settings → [Your Name] → iCloud → GeoNap.

---

Auto-Notify Contacts

If you use the optional Auto-Notify feature, you can pick contacts to automatically message when an alarm fires. Picking a contact uses Apple's system contact picker — GeoNap never gets bulk or ongoing access to your address book, only the specific contact(s) you choose.

For each contact you add, GeoNap stores that contact's name and phone number or email address — nothing else from their contact card. This is saved using SwiftData and, like your alarms, is optionally synced via iCloud so your Auto-Notify contacts carry over to your other devices signed into the same Apple ID.

Contact info is never transmitted to any server I operate. It's only used to address the message you configure, sent through Messages or a Shortcuts automation you control. You can remove a contact from an alarm or from Auto-Notify Defaults at any time in Settings.

---

Apple Watch

If you use GeoNap with a paired Apple Watch, the iPhone app shares your active alarms — name, location-derived region, radius, and status — with the Watch app so it can show and alert on them.

This data is sent device-to-device using Apple's WatchConnectivity framework; it never passes through any server I operate. On the Watch, it's stored in a shared App Group container local to that device so both the Watch app and its complication can read it — it is not synced to iCloud from the Watch.

If you enable the optional debug log, it may record when a Watch is paired or unpaired, or when the GeoNap Watch app is installed or removed, to help diagnose sync issues. It does not record your alarm data itself. Uninstalling GeoNap from your Watch, or unpairing the Watch, removes this shared copy.

---

Transit Feed Downloads

The Transit Alarm feature downloads GTFS data directly from public transit agency servers. These feeds contain stop names, coordinates, and route information — no personal data is included.

Downloaded GTFS data is cached in the app's caches directory on your device. Cached files may be deleted by iOS when storage is low; the app will re-download on demand.

No custom GTFS URL you enter is stored beyond the current session, and no information about which agencies you browsed is transmitted anywhere.

---

Notifications

GeoNap delivers local notifications entirely on-device using iOS's UNUserNotificationCenter. Notifications are generated by the app itself when a geofence event fires — they are not sent through any push notification server or remote service. No notification content is transmitted off your device.

You can manage notification permissions in Settings → Notifications → GeoNap.

---

Analytics & Crash Reporting

GeoNap does not include any third-party analytics SDKs, advertising networks, or crash reporting services. The app does not track how you use it and does not collect diagnostic information beyond what iOS provides natively in Settings → Privacy & Security → Analytics & Improvements.

---

Deleting Your Data

You can delete individual alarms by swiping left on any alarm row, or delete all data by removing the app from your device. Uninstalling GeoNap removes all locally stored alarm records. If iCloud sync was enabled, you can also delete the app's CloudKit data in Settings → [Your Name] → iCloud → Manage Account Storage → GeoNap.

---

Calendar Access

If you turn on Calendar Scanning in Settings, GeoNap reads events from the calendars you choose to look for upcoming trips with a location — for example a flight, train, or meeting. This happens entirely on your device: calendar data is never uploaded, stored outside the app, or shared with third parties. Only the location text of a candidate event is sent to Apple's geocoding service to convert it into map coordinates, the same way manually dropping a pin already works in GeoNap. Calendar Scanning is off by default; you can turn it off at any time in Settings → Calendar Scanning, and revoke calendar access entirely in iOS Settings → Privacy & Security → Calendars → GeoNap.

---

Questions

If you have questions about privacy or data handling, you can reach the developer through the App Store support link on GeoNap's product page.

© 2026 Robert Bartis. All rights reserved.