Privacy Policy for al-Firqah an-Naajiyah

Privacy Policy for al-Firqah an-Naajiyah

Effective date: July 29, 2026

English

1. About this policy

Al-Firqah an-Naajiyah provides Islamic educational articles, lectures, audio files, and PDF books. This policy explains what information the mobile app and the firqatunnajia.com notification service process, why it is used, and the choices available to you.

2. Information we process

• No user account is required. You do not need to provide a name, email address, phone number, or login to use the app.
• Automatic Android messaging identifiers. On Android, Firebase Cloud Messaging and Firebase Installations automatically generate and process a Firebase Installation ID (FID), an FCM registration token, the app version, and technical app/device metadata used to initialise and deliver messages. This can happen when FCM starts, before you choose to enable Firqat notifications. These identifiers do not uniquely identify a person or physical device.
• Optional notification information. Only after you choose to enable notifications, the app sends a random installation identifier, an installation authentication credential, an Expo push token, device platform, selected language, app version, notification status, and last registration time to firqatunnajia.com. The server stores a protected hash of the authentication credential.
• Notification operations. The service records delivery state, timestamps, limited error information, and administrative actions needed to send, secure, troubleshoot, and audit notifications. Raw push tokens and complete installation identifiers are not displayed in the WordPress dashboard.
• Server connection information. Like most internet services, our hosting and security systems may process an IP address, request time, and basic request details when the app connects to firqatunnajia.com.
• Data kept on your device. Reading history, favorites, downloaded files, and cached content are stored locally for app features. They are not uploaded to our notification service.

3. How we use information

We use this information to deliver notifications you requested, open the relevant article or book when you tap a notification, respect your language and notification settings, protect the registration service from abuse, diagnose delivery failures, and maintain service reliability. We do not sell this information or use it for third-party advertising.

4. Services involved

• firqatunnajia.com stores opted-in installation registrations and controls notification content and delivery.
• Expo Push Service routes notification requests to the platform delivery services.
• Apple Push Notification service (APNs) delivers notifications to Apple devices.
• Google Firebase Cloud Messaging (FCM) and Firebase Installations initialise Android messaging, generate the FID and registration token, and deliver notifications to Android devices.
• Internet Archive may host specific media files uploaded and controlled by the Firqatunnajia content owner. The app does not provide access to Internet Archive’s general catalog.

These providers may process data in countries other than your own under their respective privacy and security terms. Articles may also contain links to external websites. Opening an external link is governed by that site’s policy.

5. Notification choice and control

Notifications are off by default. The app first explains the feature and requests system permission only after you choose to enable it. You can turn notifications off in the app’s Settings screen or in your device settings. When you turn them off in the app, it asks our server to disable that installation. If the device is temporarily offline, the app keeps the choice locally and retries the disable request. Disabled installations are excluded from future notification audiences.

6. Retention

• An active installation registration is retained while notifications remain enabled and the registration is needed to provide the service.
• Completed notification events, delivery records, and delivery attempts are normally removed after 90 days.
• Disabled, replaced, or invalid installation registrations are eligible for removal after 90 days when no retained delivery record still depends on them.
• Administrative audit entries are retained for security, accountability, and abuse investigation. Hosting and security logs follow the operational retention practices of our service providers.
• Firebase controls retention and deletion of its automatically generated FID and related installation data under Google’s published retention practices. Turning off Firqat notifications does not immediately delete this Firebase-managed identifier.

7. Security

Registration requests use HTTPS. Each installation uses a random identifier and a separate authentication credential. Administrative screens mask installation identifiers and never display raw push tokens. No internet service can guarantee absolute security, but we use access controls, request limits, protected credentials, and operational monitoring to reduce risk.

8. Children

The app provides general educational content and does not require an account. We do not knowingly collect a child’s name, email address, phone number, or other direct contact information. Android messaging and optional notification registration use the technical identifiers described above.

9. Changes to this policy

We may update this policy when the app or its service providers change. The effective date at the top of this page shows the latest revision.

10. Contact

For privacy questions or requests, use our support page: https://firqatunnajia.com/wasiliana-nasi/.

Kiswahili

1. Kuhusu sera hii

Al-Firqah an-Naajiyah hutoa makala za elimu ya Kiislamu, mihadhara, sauti, na vitabu vya PDF. Sera hii inaeleza taarifa zinazochakatwa na programu ya simu pamoja na huduma ya arifa ya firqatunnajia.com, sababu za matumizi yake, na chaguo ulizo nazo.

2. Taarifa tunazochakata

• Huhitaji akaunti. Huhitaji kutoa jina, barua pepe, namba ya simu, au taarifa za kuingia ili kutumia programu.
• Vitambulisho vya ujumbe vya Android vinavyotengenezwa moja kwa moja. Kwenye Android, Firebase Cloud Messaging na Firebase Installations hutengeneza na kuchakata moja kwa moja Firebase Installation ID (FID), tokeni ya usajili wa FCM, toleo la programu, na taarifa za kiufundi za programu/kifaa zinazotumiwa kuanzisha na kuwasilisha ujumbe. Hii inaweza kutokea FCM inapoanza, kabla ya kuchagua kuwasha arifa za Firqat. Vitambulisho hivi havimtambulishi kipekee mtu au kifaa halisi.
• Taarifa za hiari za arifa. Baada tu ya kuchagua kuwasha arifa, programu hutuma kitambulisho cha nasibu cha usakinishaji, taarifa ya uthibitishaji wa usakinishaji, tokeni ya Expo, aina ya kifaa, lugha uliyochagua, toleo la programu, hali ya arifa, na muda wa mwisho wa usajili kwenda firqatunnajia.com. Seva huhifadhi hash iliyolindwa ya taarifa ya uthibitishaji.
• Uendeshaji wa arifa. Huduma huhifadhi hali ya uwasilishaji, muda, taarifa chache za hitilafu, na vitendo vya msimamizi vinavyohitajika kutuma, kulinda, kutatua matatizo, na kukagua arifa. Tokeni kamili za arifa na vitambulisho kamili vya usakinishaji havionyeshwi kwenye dashibodi ya WordPress.
• Taarifa za muunganisho wa seva. Kama huduma nyingi za mtandao, mifumo yetu ya hosting na usalama inaweza kuchakata anwani ya IP, muda wa ombi, na maelezo ya msingi ya ombi wakati programu inaunganisha na firqatunnajia.com.
• Taarifa zinazobaki kwenye kifaa. Historia ya kusoma, vipendwa, faili ulizopakua, na maudhui ya akiba huhifadhiwa kwenye kifaa chako kwa vipengele vya programu. Hazipakwi kwenye huduma yetu ya arifa.

3. Jinsi tunavyotumia taarifa

Tunatumia taarifa hizi kuwasilisha arifa ulizoomba, kufungua makala au kitabu husika unapogusa arifa, kuheshimu lugha na mipangilio yako, kuzuia matumizi mabaya ya huduma ya usajili, kuchunguza hitilafu za uwasilishaji, na kudumisha uaminifu wa huduma. Hatuuzi taarifa hizi wala kuzitumia kwa matangazo ya watu wengine.

4. Huduma zinazohusika

• firqatunnajia.com huhifadhi usajili wa usakinishaji uliochagua arifa na hudhibiti maudhui na utumaji wa arifa.
• Expo Push Service hupeleka maombi ya arifa kwenye huduma za mfumo wa kifaa.
• Apple Push Notification service (APNs) huwasilisha arifa kwenye vifaa vya Apple.
• Google Firebase Cloud Messaging (FCM) na Firebase Installations huanzisha ujumbe wa Android, hutengeneza FID na tokeni ya usajili, na huwasilisha arifa kwenye vifaa vya Android.
• Internet Archive inaweza kuhifadhi faili maalum za sauti zilizopakiwa na kudhibitiwa na mmiliki wa maudhui ya Firqatunnajia. Programu haitoi ufikiaji wa katalogi ya jumla ya Internet Archive.

Watoa huduma hawa wanaweza kuchakata taarifa katika nchi nyingine chini ya masharti yao ya faragha na usalama. Makala yanaweza pia kuwa na viungo vya tovuti za nje. Ukifungua kiungo cha nje, sera ya tovuti hiyo ndiyo inayotumika.

5. Chaguo na udhibiti wa arifa

Arifa zimezimwa kwa hali ya kawaida. Programu hueleza kwanza kipengele hiki na huomba ruhusa ya mfumo baada tu ya kuchagua kukiwasha. Unaweza kuzima arifa kwenye ukurasa wa Mipangilio wa programu au kwenye mipangilio ya kifaa. Ukizima kwenye programu, programu huomba seva yetu kuzima usakinishaji huo. Ikiwa kifaa hakina mtandao kwa muda, programu huhifadhi chaguo hilo kwenye kifaa na hujaribu tena ombi la kuzima. Usakinishaji uliozimwa hautajumuishwa kwenye arifa za baadaye.

6. Muda wa kuhifadhi

• Usajili unaofanya kazi huhifadhiwa wakati arifa zimewashwa na usajili unahitajika kutoa huduma.
• Matukio ya arifa yaliyokamilika, rekodi za uwasilishaji, na majaribio ya uwasilishaji kwa kawaida huondolewa baada ya siku 90.
• Usajili uliozimwa, kubadilishwa, au kuwa batili unaweza kuondolewa baada ya siku 90 wakati hakuna rekodi ya uwasilishaji inayoutegemea.
• Rekodi za ukaguzi wa vitendo vya wasimamizi huhifadhiwa kwa usalama, uwajibikaji, na uchunguzi wa matumizi mabaya. Rekodi za hosting na usalama hufuata taratibu za uendeshaji za watoa huduma wetu.
• Firebase hudhibiti muda wa kuhifadhi na ufutaji wa FID inayotengenezwa moja kwa moja pamoja na taarifa zake za usakinishaji kwa kufuata taratibu za Google zilizochapishwa. Kuzima arifa za Firqat hakuondoi mara moja kitambulisho hiki kinachosimamiwa na Firebase.

7. Usalama

Maombi ya usajili hutumia HTTPS. Kila usakinishaji hutumia kitambulisho cha nasibu na taarifa tofauti ya uthibitishaji. Kurasa za wasimamizi huficha sehemu ya vitambulisho na hazionyeshi tokeni halisi za arifa. Hakuna huduma ya mtandao inayoweza kuhakikisha usalama kamili, lakini tunatumia udhibiti wa ufikiaji, mipaka ya maombi, taarifa zilizolindwa, na ufuatiliaji wa uendeshaji ili kupunguza hatari.

8. Watoto

Programu hutoa elimu ya jumla na haihitaji akaunti. Hatukusanyi kwa makusudi jina, barua pepe, namba ya simu, au taarifa nyingine za mawasiliano ya moja kwa moja za mtoto. Ujumbe wa Android na usajili wa hiari wa arifa hutumia vitambulisho vya kiufundi vilivyoelezwa hapo juu.

9. Mabadiliko ya sera

Tunaweza kusasisha sera hii programu au watoa huduma wanapobadilika. Tarehe iliyo juu ya ukurasa huu inaonyesha toleo la mwisho.

10. Mawasiliano

Kwa maswali au maombi kuhusu faragha, tumia ukurasa wetu wa msaada: https://firqatunnajia.com/wasiliana-nasi/.