Privacy Policy

This policy describes the current behavior of the Furqanly web app as reflected in this codebase. It should be updated whenever synced accounts, public analytics, new support channels, or additional data flows are introduced.

If the running product ever differs from what is written here, the product behavior should be corrected or this page should be revised immediately.

• Reading progress and last-read position.
• Bookmarks and bookmark notes.
• Reader preferences such as translation and transliteration settings.
• Recent search history used to improve local search suggestions.
• Cached Quran data used to make repeated reading faster.
• Local auth mode and a cached local profile snapshot when sign-in is used.

• Firebase Authentication is used when you choose Google or Apple sign-in.
• Quran text and related content are fetched through the project’s Quran data client, which wraps Quran.com API resources.
• Umami can be enabled as the project’s privacy-focused analytics layer using environment-based configuration.

The current web experience primarily uses local browser storage to remember your reading state and preferences so the app feels continuous between visits. Optional sign-in is used to identify your account session through Firebase when auth is enabled.

The project goal is to support focused reading and learning, not to build an advertising profile. When Umami analytics is enabled, it should be used for product health, discovery, and reliability reporting without storing search query text in analytics URLs.

As synced settings, cross-device progress, analytics, or support workflows are introduced, this policy should expand with clear detail about what is collected, why it is collected, and which systems handle it.