A clear view of
where your data lives.

Facebook records stay on your device.

You manually sign in to Facebook inside Navori. Facebook cookies, browsing storage, and the signed-in browsing session live in the app’s private device storage.

Your verified Facebook name and avatar, cached group list, favorites, and automation History are also kept in app-private storage. History retains the latest 30 records. Comment text used for History actions is not saved in those records.

These Facebook browsing and automation records are not uploaded as part of ordinary scanning, posting, or History actions. An explicit payment submission is a separate data flow described below.

Uninstalling Navori or clearing its app data removes the local records and Facebook session. These records are not a cloud backup.

Your Navori account uses Firebase.

Navori offers email/password and Google sign-in through Firebase Authentication. That is separate from manually signing in to Facebook. Firebase handles Navori authentication and restores your authenticated app session.

A Firebase account can claim one trial. Firestore stores the trial claim and access status used to check whether trial or paid access is active.

Payment proof is sent only when you submit it.

The app’s payment screen lets you select and review a proof image. Explicit submission sends the selected image and the disclosed Navori account and payment information to a Discord review channel for manual review.

The disclosed information can include your Navori account identity/email, verified Facebook name, selected plan, and submission details. Check the disclosure inside the app before submitting, and review the selected image for unrelated personal information.

Firestore separately stores bounded payment metadata, such as submission references, plan, review status, and access expiry. This payment flow does not upload your Facebook browsing history, group list, or automation History.

Submitted proof is no longer only on your device. Discord holds the submitted proof and review information; Firebase services handle the relevant account and access metadata. Clearing app data does not delete an already submitted payment record from those services.

Paid access requires manual approval. Uploading proof alone does not activate access, and payments do not renew automatically.

You confirm Android updates.

Navori checks fixed public GitHub update endpoints for release information. An update check does not send your Navori account or Facebook browsing state. GitHub receives the network request and handles it under its own policies.

You explicitly download updates and confirm installation using Android. Some app versions require an update before you can continue. Updating in place preserves app-private records.

This website is a static companion.

This website has no registration, sign-in, payment upload, checkout, or Facebook connection. It does not use analytics, advertising trackers, cookies, local storage, or session storage. The preview uses fictional sample data and does not connect to Facebook.

Fonts, styles, scripts, and images are served with the website. There are no third-party embeds or remote font requests. Menu and preview controls only change the current page; FAQ controls use your browser’s built-in disclosure behavior.

Your browser requests pages and assets from the hosting provider. The host may process normal connection information such as IP address, request time, and requested URL in operational logs. A production host and its log-retention settings have not yet been configured in this repository.

Following a release link opens GitHub, where that service’s own privacy practices apply. This website does not transmit Navori credentials, Facebook account details, or payment proof.