Privacy Policy

Napigation · Last updated: October 20, 2026

1. Introduction

Welcome to Napigation ("the App", "we", "us"). Your privacy matters to us. This Privacy Policy explains how we collect, use, store, and protect your information.

2. Information We Collect

2.1 Information You Provide

Saved locations: Names, descriptions, addresses, coordinates, and radii of locations you choose to save — on your device only
Routes: Saved route details and route paths you create — on your device only. Alarm records may include a technical route reference and route progress, but not the destination details or route path (see section 2.2).

2.2 Information Collected Automatically

Geographic location: When you activate proximity alerts, GPS is processed on your device for up to 10 hours or until arrival. We do not store raw GPS coordinates on our servers. Address searches send a rounded approximate region to geocoding providers; reverse geocoding may send the exact coordinates of a map point you select to LocationIQ to return an address. These requests are not stored by Me-Kum.
Usage analytics and error reporting:
- Address searches send the search text and a rounded approximate region (about 1.1 km precision) to geocoding providers to rank results. Me-Kum does not store these request coordinates.
- Map point selection (reverse geocoding) sends the selected point's exact coordinates to LocationIQ to return an address. Me-Kum does not store these request coordinates.
- In-app actions (such as creating a location, activating an alarm, and changing settings) may be used for product analytics. Amplitude events use a random per-install identifier; they do not use your name or contact details, and address-search tracking omits the search text and selected address. When an alarm is activated, a technical session record linked to a pseudonymous installation ID is stored in Supabase. It may include the outcome, alarm/route type, a technical route reference and route progress, app version, language/country, subscription status and system permissions, as well as battery, duration, speed, and GPS quality/continuity metrics. The record does not include raw GPS coordinates, destination names/addresses, or the route path.
- Detailed alarm-reliability checkpoints are not collected in the current app version.
- Error and trace reports are sent to Sentry with a stable pseudonymous installation ID so recurring technical issues can be analyzed. Default PII collection is disabled. Before reports are sent, request query strings, headers, cookies, and bodies are removed; the reported user IP field is replaced with a placeholder. Sentry may still process network metadata needed to receive a report. Session Replay is captured only for sessions with an error, not ordinary sessions, and text, images, and vector content are configured to be masked. This data is used to diagnose technical issues and improve reliability, not for advertising or marketing.

2.3 Permissions

Background Location: For proximity alerts even when the app is closed
Notifications: To send alerts when you arrive at a destination
Display Over Other Apps: So the arrival screen appears immediately, even if another app is open
Do Not Disturb Management: To allow the arrival sound to play even when DND is active
Volume Control: To temporarily boost volume on arrival, then restore it
Boot Receiver: To restore active alarms when the device restarts
Battery Optimization Exemption: For reliable background operation (the app asks for your approval)
Billing: To process subscriptions through Apple App Store or Google Play, depending on your platform
Internet: For address search, station loading, and analytics

3. How We Use Your Information

Proximity alerts: Track your location to alert you when approaching a saved location
Saving preferences: Storing locations, routes, and personal settings
Service improvement: Usage analytics and error reports to improve reliability
Technical support: Debugging and issue resolution

4. Data Storage and Security

4.1 Where Data Is Stored

Local (on your device): Saved destinations, routes, their coordinates, and personal settings are stored on your device and are not stored on our servers.
Cloud (Supabase): Aggregate action counts, service data, and technical alarm-session records linked to a pseudonymous installation ID, as described in section 2.2. These records do not store raw GPS coordinates, destination names/addresses, or the route path. Detailed alarm-reliability checkpoints are not collected in the current app version.
Sentry: Receives pseudonymous error/trace reports and masked Session Replay only for sessions with an error. Default PII collection is disabled and request query strings, headers, cookies, and bodies are removed before reporting; Sentry may process network metadata needed to receive reports.

4.2 Security Measures

Encryption: All server communication is encrypted (SSL/TLS)
Pseudonymous identifiers: Analytics and error reports may use an installation ID that links events from the same installation; they are not fully anonymous.
No server-side storage of destination details or route paths: We do not store raw GPS coordinates, saved destination names/addresses, or route paths on our servers. Alarm records may include a technical route reference and route progress, as described in section 2.2. Geocoding requests may transmit an approximate search region or selected map-point coordinates to the providers listed above.
No data selling: We will never sell your personal data

5. Third-Party Data Sharing

5.1 Services We Use

LocationIQ + OpenStreetMap Nominatim: Geocoding services
Google Maps Platform: Geocoding fallback — subject to Google's Privacy Policy
Amplitude: Product analytics using a random per-install identifier; address-search events omit the search text and selected address
Sentry: Error/trace reporting with a stable pseudonymous installation ID, plus masked Session Replay only for sessions with an error. Default PII collection is disabled and request query strings, headers, cookies, and bodies are removed before reporting.
RevenueCat: Subscription management. Billing is handled by Apple App Store or Google Play, depending on your platform
Supabase: Cloud infrastructure for analytics and server features, including technical alarm-session records linked to a pseudonymous installation ID
Expo / EAS: App distribution infrastructure

5.2 What We Won't Share

We will never sell your data to third parties
We share data with the service providers listed above to operate app features such as geocoding, analytics, error reporting, and subscriptions
We will not send spam or unsolicited advertisements

6. Your Rights

View: See all your data through the app
Edit and delete: Edit or delete locations and routes at any time
Delete local data: Settings → Delete all data
Contact us: me.kum.support@gmail.com

7. Data Retention

Alarm diagnostics: Detailed alarm-reliability checkpoints are not collected in the current app version.
Sentry reports and session replays: Retention is governed by Sentry's service settings and policies.
Local user data: Stored on your device. Uninstalling removes local app data, but does not guarantee deletion of information already transferred to third-party services.

8. Children's Privacy

The app is not intended for children under 13. We do not knowingly collect information from children.

9. GDPR and CCPA

If you are in the EU or California, you have additional rights to access, correct, delete, and port your data. Contact us: me.kum.support@gmail.com

10. Changes to This Policy

We will update this policy if there are significant changes and notify you through the app.

11. Contact

Email: me.kum.support@gmail.com

12. Governing Law

This policy is governed by the laws of the State of Israel.