NNavi Journal
Privacy & trust

Navi Privacy Policy

How Navi handles your journal content, app permissions, optional sign-in, purchases, and AI transcription.

Effective date: November 3, 2026

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. If you choose it, Google may provide Navi with your Google account identifier and basic profile details such as name, email address, and profile image. Navi uses this information for sign-in and account-related functionality; your device journal remains separate from your Google account.

Navi also uses Firebase Authentication to create an anonymous identity and authentication token when certain server features, such as transcription, need to verify a request. These services and their providers may process technical data (such as identifiers, network information, and service logs) to operate securely. Navi does not store your journal entries in Firebase Firestore.

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 sold through Google Play, which handles payment processing. Navi does not receive your full payment card number. RevenueCat helps Navi verify and manage subscription or lifetime-purchase entitlements.

Google Play and RevenueCat may process purchase information, product identifiers, an app-specific customer identifier, and technical app or device information needed to deliver and restore purchases. Their respective privacy terms govern their processing.

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 and deletion

Journal data stored locally generally remains on your device until you delete entries, remove the app’s data, or uninstall the app, subject to device and backup behavior. Files that you have exported separately must be deleted wherever you stored them.

Authentication records, purchase records, technical logs, and information processed by service providers may have separate retention periods based on operational, security, and legal requirements. Signing out of Google is not the same as deleting all related service records.

For a request concerning information controlled by Navi Journal, including a request to delete an associated account or authentication identity, visit our account and data deletion page or email navijournal.support@gmail.com. We will review and respond to applicable requests. Some information, such as records Google Play is legally required to keep, is controlled by the relevant provider.

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.