Navi Privacy Policy

1. About Navi

Navi is a local-first journal and activity logging app published by Navi Journal ("we", "us"). This policy explains how Navi handles information when you use the app and its optional services.

Most journal content stays on your device. Optional services—including Google Sign-In, purchases, and AI transcription—use third-party providers as described below.

2. Journal information stored on your device

Depending on the features you use, Navi may access and save notes, to-do items, reminders, recordings, photos, location coordinates, dates and times, and app settings on your device. These items are stored as part of your local journal.

Navi does not currently offer journal cloud sync and does not automatically upload ordinary journal entries, photos, recordings, or saved coordinates to a Navi journal database. You can choose to export a backup; where you save or share that exported file is up to you.

3. Microphone and AI transcription

With your permission, Navi accesses your microphone when you choose to record audio. Ordinary recordings are saved locally and are not automatically uploaded.

If you select Transcribe to text, Navi sends the selected recording over an encrypted connection to our backend on Google Cloud Run, which authenticates the request with Firebase Authentication and submits the recording to Google Gemini to generate text. The text is returned to your app. Your original recording remains in the journal unless you remove it.

Transcription is optional. We do not send unrelated journal entries, photos, or locations to Gemini for this feature. Google processes transcription inputs and associated technical data according to the terms applicable to its services. Navi’s backend is not intended as long-term storage for your recordings; however, service providers may retain operational data according to their policies.

4. Sign-in and authentication

Google Sign-In is optional and handled on your device. If you choose it, Google may provide Navi with your Google account identifier and basic profile information such as name, email address, and profile image. Navi may store a profile locally to display that information. Signing out of Navi does not delete your Google account.

Google Sign-In is not currently linked to Navi’s Firebase Authentication identity. The Firebase identity is anonymous and is created only when you first choose to use the optional AI transcription service. Firebase Authentication manages the identity and its authentication tokens so the backend can check requests. An anonymous Firebase identity can remain after uninstalling the app unless it is deleted or subsequently removed by a provider cleanup process.

Navi does not currently store journal entries in Firebase Firestore or offer journal cloud synchronization.

5. Photos, location, and notifications

Photos: When you choose to attach a photo, Navi accesses the selected image or camera feature as needed and stores the attachment locally. Journal photos are not automatically uploaded to Navi servers.

Location: When you choose to attach a location, Navi may access latitude, longitude, accuracy, and associated time. That information is stored locally in your entry. Navi does not automatically send your coordinates to a reverse-geocoding service. If you choose to open a location in Google Maps, the location is provided to Google Maps to perform that action.

Notifications: If you enable reminder notifications, Navi uses the notification permission to show reminders you create. Navi does not use reminders for third-party advertising.

6. Google Play purchases and RevenueCat

Optional paid features are provided through Google Play, which processes payments. Navi does not receive your complete payment card number. RevenueCat manages purchase entitlements and may process an app-specific customer identifier, product and purchase history, and technical details needed to verify or restore purchases.

Deleting your Firebase authentication identity or signing out locally does not cancel a subscription, refund a purchase, or automatically erase Google Play or RevenueCat purchase records. You can manage subscriptions in Google Play and request deletion of a RevenueCat-linked customer record through our data deletion process, subject to verification and legitimate retention obligations. Restoring eligible purchases may re-create an entitlement record.

7. Who receives information

Information may be processed by the following providers when relevant to the feature you use: Google Play (app distribution and payments), Google Sign-In (optional login), Firebase Authentication (authentication), Google Cloud Run (Navi backend), Google Gemini (only when you request AI transcription), RevenueCat (purchase entitlements), and Google Maps (only when you open a location there).

These services may process technical data such as IP addresses, authentication identifiers, app details, and operational logs as needed to deliver the service and protect against misuse. Processing may take place outside your country, subject to the providers’ applicable safeguards.

8. Advertising and selling data

Navi does not currently display third-party advertising. We do not sell your journal entries, voice recordings, photos, location information, or Google account information.

9. Retention, account deletion and your choices

Local journal content: Entries, attached photos, voice notes, reminders, saved coordinates, and other journal material generally remain on your phone until you remove them or clear the app’s local data. Exported backups remain wherever you choose to save them and must be deleted separately. We cannot remotely erase offline journal content from a phone we do not control.

Anonymous Firebase account: If you use AI transcription, Firebase Authentication creates an anonymous user identifier. That account can be removed using Navi’s in-app account-deletion flow when available and functional, or by requesting deletion through our public deletion page. Signing out and uninstalling do not necessarily erase the Firebase account. We do not currently promise automatic anonymous-account cleanup.

Backend metadata: Navi’s backend holds short-lived per-identifier rate-limit counters in memory, expiring within approximately 24 hours, and removes the user counter when a successful server-side account deletion is processed. Operational request and infrastructure logs may be retained under the applicable service-provider logging and retention settings; the backend is not designed to retain uploaded audio as journal files.

AI transcription: Recordings are transmitted only when you expressly request transcription. Navi does not store a permanent server-side copy of the journal recording. Google Cloud and Gemini may process or retain technical information under their applicable terms and policies; their exact retention periods are not controlled by your local journal settings.

Purchases: RevenueCat maintains purchase-entitlement/customer records until they are removed through an applicable verified request or under its own retention practices. Google Play may retain orders, payments, and related records as required for transactions, fraud prevention or legal compliance. Deleting your account does not automatically delete these records.

Requests and applicable rights: To request deletion of an authentication identity or other account-linked records we control, use Account & data deletion or email navijournal.support@gmail.com. We may request information needed to verify your authority before performing destructive actions. Some information may be retained where a legitimate or legal obligation applies; we will explain relevant exceptions when responding.

10. Security

We use HTTPS for communication with Navi’s backend and authentication for server-side transcription requests. The Gemini service credential is stored on server infrastructure rather than intentionally bundled into the Android app. No system is guaranteed to be completely secure, and you should protect access to your device and any exported backups.

11. Children

Navi is not specifically directed to children. If you believe a child has provided personal information in circumstances that require deletion, contact us so we can review the request.

12. Your rights

Depending on applicable law, including privacy laws in the European Economic Area, you may be able to request access, correction, deletion, restriction, objection, or portability of personal information that Navi Journal controls. You may also have the right to complain to your local data protection authority. Because most journal content exists only on your device, we generally cannot access or retrieve it for you.

13. Changes to this policy

We may update this policy to reflect changes to Navi or legal requirements. We will publish the current version here and update its effective date.

14. Contact

App: Navi
Developer: Navi Journal
Privacy and support: navijournal.support@gmail.com

Please do not email passwords, private keys, or sensitive journal content unless necessary for your request.