Applies to version 2.0. Last updated: 25 October 2026.
Zād Journey works without a Zād account, advertising, third-party analytics SDKs or cross-app tracking. We do not sell personal information or operate a server that receives your app records. Some features contact external services directly from your device, as explained below.
This policy covers the iPhone and iPad app, its widgets, and the companion Apple Watch app, widgets and complications.
The app stores the information needed to provide the features you use:
Prayer history and some Qadha answers can reveal religious practice or health-related information. Zakat entries contain financial information. These entries are not uploaded to the developer, Ummah API or ExchangeRate-API. Selected records and summaries are shared with your widgets and paired Apple Watch as described below. Zād records payments you enter; it does not transfer money or process Zakat payments.
If you grant access, the app uses your location to resolve your city or area, obtain prayer times, determine the horizon background, support Qibla direction and update information for your current location. Background location monitoring is off by default and starts only if you enable it in Settings and grant the required system permission.
You can use the app, including Zād+, without granting location access by searching for and saving a place manually. Opening Qibla does not automatically request location access. Without it, the compass can use magnetic north with an approximate direction; optional access supports true-north correction without changing your selected prayer location.
Place searches, search suggestions and resolving a city from coordinates use Apple MapKit services. Search text and relevant location information are sent to Apple to provide those results.
These requests use HTTPS and go directly to the service provider:
ummahapi.com/api/prayer-times/month. Coordinates can come from device location or a place you select manually. The settings may indicate calculation preferences. Denying device location access does not prevent requests for manually selected places.ummahapi.com/api/zakat/prices to obtain gold and silver prices. Your assets, debts, metal holdings, valuation records, payments and result are not sent. Zakat calculations take place on your device.open.er-api.com/v6/latest/USD. Conversion takes place on your device. Neither your entered amounts nor your selected source and target currencies are sent to this provider.The app does not require you to register for an API key or supply an email address to these providers.
External services receive your IP address and technical request information when your device connects. Local storage of your records does not mean that API requests are anonymous or never logged.
Ummah API’s privacy policy states that it logs the endpoint, request time, IP address and user-agent for rate limiting, abuse prevention and aggregate usage counts. It describes aggregate retention but gives no fixed individual-log retention period or explicit treatment of coordinate query parameters. It lists Cloudflare, Vercel and Supabase among its service providers. Its website analytics are separate from the native app’s API requests.
ExchangeRate-API’s privacy terms describe processing in Ireland, South Africa and Germany and the use of infrastructure providers. They do not specify a retention period for this app’s open-endpoint requests.
Provider processing is governed by their applicable privacy terms. We cannot delete their logs by removing data from your device. Their policies explain available contact and deletion-request routes.
The app uses Apple App Groups to share data with its widgets on the same device and WatchConnectivity to exchange information with your paired Apple Watch. Shared information includes selected location names and coordinates, time zones, prayer schedules, calendar and Ramadan information, appearance and Zād+ access status.
Daily prayer statuses are shared with the relevant widgets. The paired Watch also receives recent daily registrations, Qadha remaining totals and recent make-up counts, and saved Zakat summaries including valuation dates, amounts due, paid and remaining, and payment dates and amounts. Daily and Qadha registrations made on the Watch are sent back to the paired iPhone. The Watch summaries do not include your Qadha setup birthdate, menstrual-day estimates or Zakat payment descriptions.
These are Apple-provided device and extension services, not a Zād account-based cloud-sync service. The app does not provide general record synchronisation between iPhone and iPad. Information displayed in a widget or complication may be visible to someone who can see your screen, subject to your device’s privacy settings.
Zād+ is offered as an optional one-time in-app purchase through Apple StoreKit. Apple handles payment and purchase history under its own terms. The app reads verified transactions to determine and restore access, including eligible earlier subscriptions. A local access-status snapshot is shared with widgets and the paired Watch. The developer does not receive your payment-card details through the app or send transaction information to the prayer-times or price providers.
See Apple’s Privacy Policy for Apple’s processing of location, purchase, device and backup information, and Apple Maps & Privacy for information about its maps services.
Saved records and preferences remain locally until you change or delete them using the available controls, or remove the app’s data through the operating system. There is no automatic expiry for daily, Qadha or saved Zakat records.
Prayer-schedule caches are checked for refresh after 30 days. This is a refresh interval, not a deletion deadline; older schedules may remain for offline use. Widget and Watch copies can remain until replaced by an update or removed with the corresponding app. Delivery and refresh are controlled by Apple.
You can revoke location access in system Settings and switch off background location inside the app. Doing so stops further access to device location; it does not erase previously saved places or schedules.
App data may be included in device backups, including iCloud backups if enabled. Backups and restoration are controlled by your Apple settings. Removing app data from a device does not automatically remove existing backups, paired-device copies, provider logs or Apple purchase history. Deleting the app, rather than offloading it, removes its local app data according to the operating system’s behaviour.
Links to sources, support pages and provider websites open services with their own privacy practices. Data you choose to submit to support is separate from your local app records. Do not post prayer history, financial records, birthdates, precise locations or other sensitive information in public support issues.
For privacy questions or requests, use the support contact shown on the App Store product page. Support information is available on the Zād Journey support page. The developer cannot retrieve local records from your device. Where applicable, you may have rights to access, correct or delete personal data, restrict or object to processing, and complain to your data-protection authority. For data held by a service provider, its privacy policy gives its contact route.
Zād Journey is a general prayer reference and calculation tool. It does not require a child’s account or upload their prayer, Qadha or Zakat records to the developer. External requests described above can still occur when these features are used.
We may update this policy when features or data practices change. The date above identifies this revision. The current policy is available through the privacy-policy link in the app and on its App Store product page.