MASJID FUTA NJ

Privacy policy

Effective October 30, 2026

MASJID FUTA NJ is operated by Alpha Diallo. This policy covers the MASJID FUTA NJ iPhone and Android apps, their public reading interface and app support services. The app provides prayer times, Adhkar, Quran reading and community announcements and class information. You do not need an account to use these core features.

Privacy questions or requests
masjidfutanj.support@icloud.com

Information stored on your device

Reading progress, bookmarks, Dhikr counts, appearance and language preferences, downloaded text and audio, and prayer and class reminder settings are stored on your device. Imported Adhan recordings stay in the app’s private storage. We do not upload these items to an app account or provide account-based synchronization. On iPhone, device backups are controlled by Apple and your device settings. The Android app disables cloud backup and device-to-device transfer of its local app data.

Class reminders and Home Screen widgets

Class reminders are optional local notifications for the class occurrence you select. The selected public class details, reminder time and status are stored on your device, not uploaded to an app account. Notification permission is requested when needed. You can review or remove saved reminders in Community. Opening Community while online checks published schedule changes; device settings and connectivity can affect reminder delivery and these checks.

Home Screen widgets display public prayer times, class details and fundraising updates. Widgets keep a local cache of this public information and use the device language for their labels. Widget refreshes request public information from our hosting and involve the normal network information described below. Widgets do not read your calendars or upload your reminder choices.

Calendar and counter feedback

Adding a class or event opens your device’s calendar editor with the selected public event details. You decide whether to save it. The app does not read your calendars or upload calendar contents. A saved calendar copy does not automatically follow later changes to the masjid schedule. Optional counter vibration is processed on your device.

iPhone prayer reminders and permissions

If you enable native prayer alarms, the app requests Apple’s alarm permission. Simple prayer notifications, vibrate-only alerts and optional reminders about saved alarm coverage request notification permission. Vibration depends on system settings. The app uses the masjid’s Newark prayer times; it does not request your location, contacts, camera or microphone. Selecting an audio file gives the app access to that file for local playback. You can change reminder choices in the app and permissions in iPhone Settings.

Android prayer reminders

If you enable daily Adhan, Android may ask for notification permission and permission to schedule exact alarms. The app stores your reminder modes, published dated prayer times, recent alarm identifiers and recordings locally. It uses a visible playback service with a Stop action, and keeps the device awake during playback. Vibrate-only uses a notification category with no sound; Android settings can suppress its vibration. You can mute individual prayers or turn off daily reminders.

The Android scheduler requests the masjid’s public timetable directly from Masjidal/AthanPlus. That provider receives normal network-request information. Refresh is requested approximately every six hours and after alerts; Android and connectivity control when it runs. The scheduler does not upload your reminder choices or imported recordings. Reboot, app-update and clock-change handling restores future dated alarms. No location, contacts, camera, microphone or broad media-library permission is requested. The system file picker provides access to the recording you choose.

Optional masjid announcements

In updated app versions, you may opt in to public masjid announcement notifications separately from Adhan. We use Google Firebase Cloud Messaging and, on iPhone, Apple Push Notification service to deliver them. These services process an app installation identifier and notification registration information; Apple notification tokens are associated with the installation for iPhone delivery. Device and app information, such as model, language, time zone, operating system and app version, and normal network information are also processed to operate the service.

Our announcement server sends public notices to a shared topic. It does not maintain a list of recipients, link notification identifiers to your name or reading history, or collect your notification opens for analytics. Firebase Analytics and delivery-metrics export are not enabled. Announcement delivery records contain a public notice ID, send status, attempt count and time; they do not confirm that a particular person received or read a message.

You can turn announcements off in Settings. Once connected, the app unsubscribes and requests deletion of its messaging registration and Firebase installation identifier. If the connection fails, the app shows that turning off is pending and retries when reopened. You can also block notifications immediately in your phone settings. Firebase states that deletion from its live and backup systems can take up to 180 days after an installation-ID deletion request. Provider records follow their own policies. Public announcements remain readable without notification permission.

See Firebase’s privacy information. Notifications may be delayed or suppressed by connectivity and phone settings; do not rely on them for emergencies.

Online content and technical information

Online requests send network information, such as your IP address, requested resource, request time and browser or device information, to the service receiving the request. This is necessary to deliver content. Our hosting uses Cloudflare. Prayer data comes from Masjidal through our service, with Android’s native scheduler also requesting the public Masjidal/AthanPlus timetable directly; class and fundraising updates are published by authorized masjid staff. Quran text and streamed recitation use Al Quran Cloud and its Islamic Network audio CDN. Downloaded Quran audio can pass through our hosting. The Adhkar text and recordings and printed Mushaf artwork are served from our app hosting.

We use hosting request logs, error reports and technical diagnostics to operate, secure and troubleshoot the app. Cloudflare Workers logs are retained for up to seven days under its platform retention limits. Query strings are redacted in our configured Worker logging. Providers may also process network information for their own service operation under their policies. We do not use advertising SDKs, sell personal information, or use app information for cross-app advertising tracking. We do not build profiles of religious beliefs from reading activity.

See Cloudflare’s privacy policy, Al Quran Cloud’s service terms, Apple’s privacy policy, and Google’s privacy policy.

Support, feedback and testing

If you email us, we receive your email address, any name you provide, your message and attachments. We use them to respond and resolve issues. The support mailbox is hosted by iCloud Mail. Please avoid sending passwords, payment card details or other information that is not needed to resolve your request.

We delete resolved support requests from our support mailbox after 90 days, unless they are needed for an ongoing issue or a legal obligation. This is our mailbox handling policy; provider backups and service logs follow the provider’s own policies. During TestFlight testing, Apple may make your submitted feedback and test diagnostics available to us. We use them to improve reliability; Apple controls information retained in its testing service. During Google Play testing, Google may provide submitted feedback and app-quality or crash information according to its platform services and device settings. We use that information to troubleshoot the app; Google controls its testing-service records. The native Android project includes no advertising or analytics SDK.

Donations and registration

In the native iPhone and Android apps, Sadaqah and Zakat open Masjidal’s secure checkout in the device’s browser (Safari on iPhone). Payment information is entered with Masjidal and its payment providers, not stored by this app. Browser versions may display an embedded Masjidal checkout, which contacts that provider when loaded. Class registration links open the external registration provider. Information you choose to submit is handled by the receiving service and the masjid for the purpose shown on its form. Review that service’s privacy information before submitting. Donation or registration is not required to read the Quran or Adhkar.

Earlier browser reminder pilot

New browser reminder enrollment is paused. Previously enrolled staff testers may still have a browser push subscription. This separate service uses Cloudflare Access sign-in and stores a hashed account identifier, push subscription endpoint and keys, and reminder choices. Subscriptions are removed when unsubscribed or when the push provider reports expiration; delivery history is removed after seven days. Contact support to request removal if you no longer have access to the enrolled browser. Native iPhone and Android alarms do not require this browser subscription or sign-in.

Your choices and deletion

Children and families

The app is intended for teens ages 13 and older and adults. It provides religious reading and community information, including class information for families. It does not require children to create profiles or submit personal information. Parents or guardians should handle class registration and donations. If you believe a child has sent us personal information that should be removed, contact support.

Changes to this policy

We will update this page and its effective date when our practices change. Material changes will be explained in the app or its release information as appropriate.