Privacy

Account information

Clerk provides sign-in for the beta. ForeNav receives verified identity claims and maps them to an internal account identifier. ForeNav's application database does not store your email address or other mutable Clerk profile fields. Clerk processes sign-in information under its own terms and privacy practices.

Journey information

ForeNav processes the places, times, vehicle setup, weather-comfort preference, and journey actions you submit. It stores canonical journey decisions, lifecycle status, and compact evidence and route references so that the beta can show, watch, replay, and audit the same journey.

Retained route payloads have an absolute 30-day ceiling and are deleted sooner when a journey completes, is cancelled, or expires. After route payload deletion, ForeNav may retain minimal journey, decision, support, replay, and audit records, including compact route identifiers and fingerprints, for as long as they are required to operate and evaluate the beta or address a support request.

Route and weather providers

To answer a journey check, ForeNav sends the origin and destination you typed, or a point you chose, to Google, and receives a resolved place and an estimated driving route. Route data © Google.

ForeNav then requests a forecast for that route from Open-Meteo. Weather data by Open-Meteo.com (CC BY 4.0). ForeNav sends route coordinates and times to these providers; it does not send your account identifier, email address, or device push token to them. Each provider processes that request under its own terms and privacy practices.

ForeNav has no official road-authority or road-notice source in this beta. Where official coverage would be required, ForeNav reports that coverage is incomplete rather than treating its absence as an all-clear.

Guardian and background location

Guardian requests Android location access only while it is running on this device for a journey you chose to protect. During this private beta, Guardian keeps a small status summary on the device, such as the journey identifier, start time, sample count, last sample time, and rounded accuracy. It does not store or upload latitude, longitude, or a continuous route history. You can stop Guardian on this device from the Protection screen, and signing out also stops Guardian. Stopping Guardian does not end the server-side Protection record for the journey.

Notifications

If you enable notifications, ForeNav registers a device push token so it can deliver a generic notice when a watched journey's canonical decision materially changes. The lock-screen payload contains a journey identifier, not a destination, departure time, weather detail, or recommended action. Expo and Firebase Cloud Messaging help deliver Android push notifications.

When automatic checks are enabled, ForeNav rechecks watched journeys before departure. Notification delivery is separate: the app shows when checks or notifications are paused. Ordinary unchanged rechecks stay quiet. Opening a watched trip does not trigger a new assessment; choosing Check again does. Treat the absence of a notice as no information, not as an all-clear.

Sharing and sale

ForeNav uses service providers where needed for sign-in, hosting, storage, and push delivery. ForeNav does not sell personal information. The beta does not use journey or Guardian information for advertising.

Your choices

• You can stop Guardian on this device from the Protection screen.
• You can disable location or notification permissions in Android settings.
• You can sign out of ForeNav.
• You can request account or data deletion through the support channel provided with your private-beta invitation.

A deletion request may require identity verification. Some minimal records may remain where needed to complete the request, preserve a required audit or replay record, or meet an applicable obligation.

Questions

Use the support channel provided with your beta invitation, or visit ForeNav Support for what to include in a request.