Ark Technologies

Islamopedia Privacy Policy

Effective date: September 18, 2026

This Privacy Policy explains how the Islamopedia mobile application, its widgets, and its Apple Watch and Wear OS companions (together, “Islamopedia”) process information. Islamopedia is developed and published by Ark Technologies.

1. Information stored on your device

Islamopedia stores app settings and activity needed to provide its features. This may include Quran bookmarks and reading position, Khatmah plans and progress, Quran study notes and tags, listening progress, favorites and playlists, prayer and reminder settings, private Salah and Ramadan fasting records, Hijri-calendar preferences, Tasbeeh phrases and counts, language and theme preferences, downloaded-content records, temporary application data, and local mosque profiles you create. A mosque profile can contain its name, saved location label and coordinates, timezone, Iqamah and Jumuah rules, and weekday or date overrides.

2. Location

When you allow location access, Islamopedia uses precise location to calculate prayer times and Qibla direction. You may instead choose a location manually. Device or platform geocoding services may process coordinates or address searches. A current automatic location may be cached locally. A manually selected prayer location, including coordinates and its label, may be included in a backup because it is part of your chosen prayer configuration. If you choose to save a location with a mosque profile, its label, coordinates, and timezone are stored with that profile so Islamopedia can calculate relative-to-Athan Iqamah times, and they may be included in an optional backup.

3. Optional Google Drive backup

Google Drive backup is optional and remains off until you choose to connect a Google account and enable backup. Islamopedia requests only the Google Drive https://www.googleapis.com/auth/drive.appdata scope. This permits Islamopedia to create, list, download, update, and delete its own files in the hidden, app-private Google Drive application-data folder. It does not permit Islamopedia to browse your ordinary Google Drive documents.

A portable backup may include:

• Quran bookmarks, last reading position, reader preferences, Khatmah plans and progress, and Quran study notes and tags;
• listening progress, completed-audio identifiers, recent content, favorites, playlists, repeat preferences, and playback speed;
• prayer, Athan, reminder, calculation, and manual-location settings, including custom reminder text;
• private Salah-tracker history and settings, Ramadan fasting records, and Hijri-calendar preferences;
• mosque profile names, saved location labels and coordinates, timezones, Iqamah and Jumuah rules, and weekday or date overrides;
• Tasbeeh phrases and counts; and
• language, theme, Easy Mode, and selected navigation preferences.

Downloaded audio files, artwork, caches, live playback queues, Google authorization tokens, and transient notification data are excluded. Islamopedia keeps up to two recent backup snapshots per app installation and may remove older snapshots created by that installation. Backups remain in Google Drive until replaced, pruned, or deleted. Disconnecting Google Drive does not automatically delete existing backups; use Delete cloud backups in Islamopedia first if you want them removed.

Backup documents contain an integrity checksum, but are not additionally end-to-end encrypted by Islamopedia. They are transmitted over HTTPS and protected by Google Drive’s security. Islamopedia does not persist Google OAuth access or refresh tokens in its backup data.

Google Sign-In and Google Drive may also process account and service metadata under Google’s policies, including identity, device, coarse-location, usage, and diagnostic information. Islamopedia itself uses the Google account identifier, display name, email address, and Drive authorization only to authenticate backup operations and show the connected account. This account information is not placed inside the Islamopedia backup document.

4. Google Firebase services

Islamopedia uses the following Google Firebase services:

• Firebase Analytics to understand app screens, feature usage, app and session lifecycle, general platform and language information, Quran and content interactions, prayer-configuration choices, permission status, and notification interactions. Analytics assigns an app-instance identifier and may derive a general region from a masked IP address. App-defined events may include content identifiers, a manually selected location label, or an inferred country code.
• Firebase Crashlytics and Firebase Sessions in release builds to receive crash reports, stack traces, relevant application state, app/build and device/operating-system information, locale, network/session metadata, diagnostic context, developer-defined configuration keys, and Analytics breadcrumbs immediately preceding a crash.
• Firebase Cloud Messaging to deliver announcements when notifications are allowed. Google associates the Apple or Android notification token with an app-installation identifier and may process device model, language, timezone, operating-system version, app identifier and version, topic subscriptions, and notification interactions.
• Firebase Remote Config to retrieve application-update and configuration information. Google may process country, language, timezone, operating-system, app and SDK identifiers, first-open time, and Analytics user properties needed to provide and evaluate configuration.

Ark Technologies does not use Firebase data for advertising or cross-company tracking. These services are provided by Google and are governed by Google’s applicable privacy and security terms.

Islamopedia does not send mosque profile names, mosque coordinates, Iqamah or Jumuah schedules, Quran study notes, Salah history, fasting records, or search text to Firebase Analytics or intentionally include them in Crashlytics reports.

5. Content delivery and server logs

Islamopedia connects to its content services to retrieve reciter and lesson catalogs, Athkar content, images, audio, and application data. The servers may receive normal technical request information such as IP address, request time, device network information, requested URLs, and error details. Islamopedia does not upload your Quran bookmarks, listening progress, prayer settings, or Google account details to Ark Technologies’ content servers as part of the backup feature.

6. Apple Watch, Wear OS, and device features

When a compatible Apple Watch or Wear OS watch is paired, Islamopedia can transfer a privacy-minimized prayer snapshot through the platform’s paired-device service. The snapshot contains prayer times, location label and coordinates, timezone, language, calculation and reminder settings, and—when enabled by you—a current-day Salah summary containing only the date and identifiers of prayers marked complete. During Ramadan it can also contain upcoming Suhoor-end and Iftar timestamps. Historical Salah records, fasting-log entries, Quran notes, mosque profiles, and backup documents are not transferred to the watch. The watch stores the latest accepted snapshot locally so its app, Tiles, or complications can remain useful offline.

If you allow location on Apple Watch, its Qibla feature may request one current location to improve true-north heading. Islamopedia does not retain that Watch location. Paired-device transfers occur through Apple or Google platform services, and Ark Technologies does not receive them.

Phone widgets store a local snapshot; on iOS it is kept in shared app-group storage. The snapshot contains prayer schedules, location label, timezone and, when enabled, the current-day Salah summary and Ramadan countdowns described above. A local Live Activity receives the next-prayer schedule, location label and timezone needed to show its status. These snapshots remain on the device except for normal operating-system backup or synchronization behavior.

Siri and App Shortcuts use fixed navigation actions, such as opening Next Prayer, Qibla, Quran, or the Salah tracker. CarPlay and system media voice searches may provide query text to Islamopedia through operating-system services; Islamopedia matches that text locally and does not intentionally send the query text to Firebase Analytics or Crashlytics. Apple, Google, vehicle, and voice-keyboard services process their own input under their respective policies.

Local mosque profiles and their Iqamah and Jumuah schedules are a phone feature in version 5.2. They are not transferred to phone widgets, Live Activities, Apple Watch, or Wear OS.

On iOS, the Google Cast sender SDK is initialized when the app starts so it can restore an existing Cast session, while local-network discovery is deferred until the first Cast-button interaction. The Cast SDK declares collection of unlinked device identifiers, product-interaction data, and diagnostic data for analytics and app functionality, without tracking. When you select a Cast device, Islamopedia sends audio stream URLs and playback metadata—such as title, reciter or speaker, artwork, queue, sleep-timer presentation state, and playback controls—to that device and Google’s Cast services. Quran notes, worship records, mosque profiles, and Google Drive backups are not sent to a Cast receiver.

Android Auto Backup may preserve the validated portable backup snapshot, while iOS and watchOS device or cloud backups may preserve application-container and UserDefaults data according to the operating system and your device-account settings. Downloaded or regenerable media is excluded where the platform allows.

7. How information is shared

Islamopedia does not sell personal information and contains no advertising SDK. Information is disclosed only as needed to provide the services described above, including Google Drive, Firebase, Google Cast, device location/geocoding services, operating-system backup services, paired-device services, and Islamopedia content hosting.

8. Retention and your choices

• You can remove locally stored app data by clearing application data or uninstalling Islamopedia, subject to operating-system backup and restore behavior.
• You can enable or disable location, notifications, exact reminders, and other permissions in device settings.
• You can disconnect Google Drive from Islamopedia. To remove stored Drive backups, use Delete cloud backups before disconnecting.
• You can also revoke Islamopedia’s Google access from your Google Account security settings.
• You may use manual backup-file export and import without connecting Google Drive.

Firebase, Google Sign-In, Google Drive, and Google Cast retain service metadata according to their configurations and Google’s applicable policies. You may contact Ark Technologies using the address below regarding information available to us. Google account connections and device permissions can be managed through the corresponding Google, Apple, or device-account controls.

9. Security

We use reasonable technical measures appropriate to the service, including HTTPS in transit, platform-provided secure authorization, strict backup-field allowlists, integrity checks, and limited Google Drive permissions. No security method can guarantee absolute protection.

10. Children

Islamopedia provides general Islamic educational and worship content. We do not knowingly use the app to request a child’s name, address, phone number, or other direct contact information. Parents and guardians should supervise children’s device and account settings, including location, notifications, and cloud backup.

11. Google API Services User Data Policy

Islamopedia’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

12. Updates to this policy

We may update this policy when Islamopedia’s features, service providers, or legal obligations change. The effective date above will be updated, and material changes may also be communicated in the app or store listing.

13. Contact

Questions or privacy requests can be sent to hello@islamopedia.app.