Last updated: July 31, 2026
- Summary
- Location data
- Camera, photos & videos
- Device storage & files
- Notifications & background service
- In-app purchases (PRO)
- Analytics & crash reporting
- Third-party services
- Permissions reference
- Data sharing
- Data retention & deletion
- Children's privacy
- Security
- Your rights
- Changes to this policy
- Contact
1Summary
| Data type | Collected | Where it's stored | Shared with third parties |
|---|---|---|---|
| GPS location (tracks) | Yes, with your permission | On your device only | No |
| Photos / videos you attach | Yes, with your permission | On your device only | No |
| Account / personal profile | Not collected | — | — |
| Advertising ID | Android: read by Firebase Analytics for measurement only, not ads. iOS: not read (see Section 7/9) | — | Google (Analytics processor, Android only) |
| Crash logs / basic app diagnostics | Yes, on Android and on iOS (Fresca) | Google Firebase | Google (processor) |
| Purchase status (PRO unlock) | Yes | Google Play / device | Google Play Billing |
2Location data
Location is the core function of geo3bit. When you start recording a track, the App reads your device's GPS coordinates (latitude, longitude, altitude, speed, heading, accuracy, satellite count) at the interval you configure in Settings.
Foreground location
Used while the App is open and visible, to show your live position and statistics on screen.
Background location
Used only while you are actively recording a track and the App is minimized, so recording can continue uninterrupted (e.g. while you lock your phone screen during a hike or bike ride). A persistent notification is always shown while background location is active, as required by Android and iOS. Background location is not collected at any other time.
Manual route creation (PRO)
The PRO "Create Manually" feature lets you place points on a map without GPS recording. If you use the address search field, the query is resolved using your device's built-in geocoder (no third-party paid mapping API is used, no location query is logged by us).
Storage of location data
All recorded GPS points are saved locally on your device as GPX files. geo3bit does not upload your tracks to any server, and we cannot see your location history. You may export and share a track yourself (e.g. via the Share or Export Package features), which is always a deliberate action you initiate.
3Camera, photos & videos
You may optionally attach photos or videos to points along your track, either by taking a new photo/video with the in-app camera or by selecting an existing item from your device's gallery. These files, together with the GPS coordinates and timestamp of the point they're attached to, are stored locally in the App's data and are included if you choose to export a track as a ZIP package.
4Device storage & files
geo3bit reads and writes files on your device to: save GPX track files, import GPX/KML/TCX files you choose to open, and create/extract ZIP packages (PRO feature) containing a track plus its attached media. The App only accesses files you explicitly pick via the system file/photo picker, or files it created itself.
5Notifications & background service
While recording, geo3bit shows a persistent notification with live stats (time, distance, points) and Pause/Resume/Stop controls, as required by Android for foreground location services. On Android, if your device restarts while a recording was in progress, the App may restart this notification so you can resume — this uses only locally stored state, no data leaves your device for this purpose.
Battery optimization exemption (Android)
When you start your first recording, geo3bit shows the standard Android system dialog asking to exempt the App from battery optimization. This is needed because Doze mode and manufacturer battery managers can suspend GPS delivery during long screen-off recordings, causing permanent gaps in your track. The exemption is used only to keep an active, user-initiated recording running; when no recording is in progress the App does no background work. The request is shown once, declining it does not block any feature, and no additional data is collected as a result of granting it.
6In-app purchases (PRO)
geo3bit offers an optional, one-time PRO upgrade purchased through Google Play Billing (Android) or the App Store (iOS). Payment details (card numbers, billing address, etc.) are handled entirely by Google/Apple — geo3bit never sees or stores your payment information. We only receive a confirmation that a purchase was completed, which is stored locally on your device to unlock PRO features.
7Analytics & crash reporting
geo3bit uses Firebase Analytics and Firebase Crashlytics (Google) to help us understand basic, aggregated app usage and to diagnose crashes so we can fix bugs. This may include: device model, OS version, app version, crash stack traces, and anonymous usage events (e.g. "track started"). This data is not linked to your name, email, or location history, and is not used for advertising.
Platform note: geo3bit ships as a single iOS app under the Fresca brand (bundle id app.bit3.fresca); the legacy GeoZvit brand remains Android-only. Firebase Analytics and Crashlytics are integrated and active on both Android and the Fresca iOS app.
geo3bit does not display third-party advertising. On Android, the Advertising ID is read by the bundled Firebase Analytics library for measurement/attribution purposes only (not ad personalization or ad serving) — see Section 9. On iOS, no Advertising ID (IDFA) is read and no App Tracking Transparency prompt is implemented, because no tracking occurs.
8Third-party services
| Service | Purpose | Data involved |
|---|---|---|
| Google Firebase (Analytics, Crashlytics) — active on Android and on the iOS (Fresca) app | Crash diagnostics, anonymous usage statistics | Device/app metadata, crash logs — no location, no personal identifiers |
| Google Play Billing / Apple StoreKit | Processing the one-time PRO purchase | Purchase confirmation only; payment details handled entirely by Google/Apple |
| OpenStreetMap tile servers | Displaying map tiles in the App | Standard map-tile HTTP requests (no personal data sent beyond what's required to fetch a tile) |
| Google Maps JavaScript API (optional) | Alternative map rendering, only if you enter your own API key in Settings | Subject to Google's own terms for that key; disabled by default |
| Device geocoder (Android/iOS system service) | Resolving an address you type into a search field (PRO manual route feature) | The text you search for, handled by your device's OS — not by geo3bit servers (we have none) |
9Permissions reference (Android & iOS)
Android
| Permission | Why it's needed |
|---|---|
| ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION | Record GPS track points |
| ACCESS_BACKGROUND_LOCATION | Continue recording while the App is minimized |
| FOREGROUND_SERVICE / FOREGROUND_SERVICE_LOCATION | Keep recording reliably while the screen is off, with a visible notification |
| POST_NOTIFICATIONS | Show the live tracking banner notification |
| RECEIVE_BOOT_COMPLETED | Restore the tracking notification if the phone restarts mid-recording |
| WAKE_LOCK | Keep the GPS pipeline and the live notification running while the screen is off during an active recording, so your track has no gaps |
| REQUEST_IGNORE_BATTERY_OPTIMIZATIONS | Show a one-time system dialog asking to exempt the App from battery optimization — otherwise Doze mode and manufacturer battery managers can suspend GPS during long screen-off recordings, permanently losing parts of your track. Optional: you can decline and the App keeps working |
| CAMERA / RECORD_AUDIO | Capture photos/videos (with sound) to attach to a track point |
| ACTIVITY_RECOGNITION | Detect activity type (e.g. walking, driving, cycling) to improve track statistics; not used for advertising or profiling |
| com.google.android.gms.permission.AD_ID (via ACCESS_ADSERVICES_ATTRIBUTION) | Pulled in transitively by the bundled Firebase Analytics library (see Section 7/8) for measurement/attribution — not used for ad personalization, since the App shows no ads |
| com.android.vending.BILLING | Process the one-time PRO purchase via Google Play Billing |
| INTERNET / ACCESS_NETWORK_STATE | Load map tiles, send crash/analytics data, process purchases, check connectivity |
| SYSTEM_ALERT_WINDOW, READ_APP_BADGE and other OEM badge permissions (Sony, HTC, Samsung, Huawei, OPPO, etc.) | Declared by bundled libraries (notification badge counts across device manufacturers); not otherwise exercised by App features — see the compliance note in Section 7/8 about verifying unused permissions before submission |
iOS
| Permission (Info.plist key) | Why it's needed |
|---|---|
Location When In Use (NSLocationWhenInUseUsageDescription) | Show your live position and statistics on screen while the App is open, and record GPS track points |
Location Always (NSLocationAlwaysAndWhenInUseUsageDescription, NSLocationAlwaysUsageDescription) | Continue recording your track in the background while the App is minimized or the screen is locked, e.g. during a hike or bike ride. iOS asks for this as a separate, second permission step after "When In Use" is already granted |
Camera (NSCameraUsageDescription) | Take a new photo or video to attach to a track point |
Microphone (NSMicrophoneUsageDescription) | Record audio as part of a video attached to a track point |
Photo Library (NSPhotoLibraryUsageDescription) | Select an existing photo or video from your library to attach to a track point |
Background Modes — Location (UIBackgroundModes: location) | Keep recording GPS points while the App is backgrounded during an active, user-started recording — not a runtime prompt, a capability declaration |
Background Modes — Background Fetch (UIBackgroundModes: fetch) | Allow iOS to periodically wake the App in the background to maintain recording state reliably; not used to fetch or transmit any data about you |
The App does not request Contacts, Calendars, Reminders, HealthKit, Bluetooth, Local Network, Face ID, or Tracking (IDFA/App Tracking Transparency) permissions on iOS, and does not request SMS, Call Log, or Contacts permissions on Android.
10Data sharing
We do not sell your data. We do not share your location history, photos, or videos with any third party. The only data that leaves your device is:
- Anonymous crash/diagnostic data sent to Firebase (Google), as described above.
- Purchase verification, handled directly between your device and Google Play / the App Store.
- Anything you explicitly choose to share or export (e.g. tapping "Share" or "Export Package" sends the file only to the destination/app you pick).
11Data retention & deletion
Tracks, photos, videos and settings remain on your device until you delete them in the App or uninstall geo3bit. Deleting a track in the App permanently removes its GPX file and attached media from your device. Uninstalling the App removes all locally stored data. Anonymous crash/analytics data sent to Firebase follows Google's own retention periods and cannot be individually attributed back to you.
12Children's privacy
geo3bit is not directed at children under 13 (or the relevant minimum age in your country) and we do not knowingly collect personal data from children. The App does not require an account, and location data stays on-device, but parents/guardians should supervise use of any location-based app.
13Security
Your track data is stored in the App's private storage area, sandboxed by the operating system from other apps. Network requests (map tiles, crash reporting, purchase verification) use standard encrypted (HTTPS/TLS) connections.
14Your rights
Because geo3bit stores your data locally rather than on a server, you are always in direct control of it: you can view, export, or permanently delete any track or photo at any time from within the App, or erase everything at once by uninstalling the App. If you have questions about the limited diagnostic data sent to Firebase, see Google's own Privacy Policy.
15Changes to this policy
We may update this Privacy Policy from time to time, for example to reflect new features. The "Last updated" date at the top of this page will always indicate the latest revision. Continued use of geo3bit after a change constitutes acceptance of the revised policy.