About this policy
This policy describes Nuralo, its current app features and this website. Contact cheny1119@icloud.com for privacy questions. Copyright attribution: CHEN YANG.
What the app stores
The app saves confirmed cities, coordinates, time zones, available location accuracy and source, calculation choices, prayer plans, display and scene settings, compass theme and alignment-haptic preference on your device. The app and Widget share a saved prayer plan through their App Group.
Local scheduling records may contain city names, dates, notification or alarm identifiers, rule fingerprints, permission status and recent results. They help reconcile future requests. There is no Nuralo account, developer-operated cloud sync, advertising SDK, analytics upload or automatic support-report upload in this build.
Location and Apple services
You can choose a city manually without location access. Search first uses a bundled catalogue. When no local match exists, the submitted search text goes to Apple’s Maps service. Choosing Use current location requests foreground location and sends obtained coordinates to Apple’s geocoding service before you confirm saving a city.
Opening Qibla automatically starts foreground location and heading updates to establish reliable true north near your saved city. Leaving Qibla or putting the app in the background stops them. The app does not request always-on background location. You can revoke access in device Settings and keep using manual cities.
Apple operates these services under its own controls. Read Apple’s privacy information and Location Services information. Local calculation does not mean data can never leave the device: service requests, system diagnostics, backups and device management have separate handling.
Notifications, alarms and Widgets
Optional prayer and fasting notifications share system notification permission but have separate switches. Optional Fajr wake-up uses separate AlarmKit permission on iOS/iPadOS 26+. The operating system stores requests needed for these features. Schedules have finite coverage; open the app regularly to prepare upcoming days.
Notifications, alarms and Widgets may expose prayer names, city names and times while your device is locked. Review notification previews and Lock Screen settings. Other people using your unlocked device may see saved choices.
Retention and your controls
Local files persist across app restarts; unreadable files may be retained for recovery. Turning a feature off cancels its future requests when cancellation succeeds, but does not erase settings or history. This build has no in-app erase-all or export control. App removal, shared containers, backups and system records follow device rules; removing the app does not guarantee erasure of every backup or system record.
You can change feature switches, revoke permissions or manage app data and backups using your device. There is no developer account or app cloud database to delete. Contact us for questions about information you have separately sent to support.
This website and external links
This static website is hosted on Cloudflare Pages. Cloudflare processes normal connection information, such as IP address and request metadata, to deliver and protect the site, under Cloudflare’s privacy policy. We have not added analytics scripts, advertising trackers, sign-in, contact forms or nonessential cookies to this website.
If you choose an external reference link, your browser connects to that site under its own policy. Opening bundled app help does not upload a report.
If you email support
Email is voluntary and separate from the app. Your address, message and attachments are handled by support and the email providers. Include only what is needed; avoid precise coordinates, full local files and screenshots of private notifications. We use correspondence to respond to your request and keep it while needed for resolution, follow-up and applicable obligations. Ask us to delete support correspondence using the address below; provider backups and required records may have separate retention.
Changes
If our features, dependencies or support practices change, we will review this policy and the store disclosures. The effective date above identifies the published policy version.