Privacy Policy

Hamza is a macOS prayer-time and reminder app. The app and this website are provided by Taqib Ibrahim (“we”, “us”, and “our”). This policy explains how the app and this website handle information.

Hamza calculates prayer times on your Mac and stores your app preferences locally. The app does not require an account, include advertising or analytics, or send your saved preferences or prayer activity to a developer-operated backend. Location lookup and city search use Apple services, as explained below.

Location and city search

You can allow Hamza to use your current location or choose a city manually. When you request your current location, Hamza uses macOS Location Services to obtain a location fix. It stops requesting updates after resolving your location; it does not maintain a history of your movements or continuously track you in the background.

Hamza uses Apple Maps services to turn coordinates into a city and time zone, suggest cities while you type, and resolve your selected city. These features may send location or search information to Apple. Choosing a city manually avoids granting Hamza access to your device’s current location, but the city search still uses Apple Maps services.

Apple handles those services under its own policies. See Apple Maps & Privacy and Location Services & Privacy.

Once a location is saved, prayer times are calculated locally using its coordinates, time zone, and your calculation settings. Hamza does not request your prayer times from a remote prayer-time service.

Information stored on your Mac

Hamza stores the information needed to restore your settings and schedule reminders:

• Your selected city or location name, coordinates, and time zone.
• Your prayer calculation method, Asr calculation choice, and high-latitude setting.
• Your reminder preferences, selected prayers, and early-reminder choices.
• Your onboarding state, display preferences, and menu-bar preference.

Settings are saved in Hamza’s local Application Support folder and macOS preferences. Hamza does not provide an account or cloud-sync service for this information. Your Mac’s backups may retain copies according to your own backup settings.

Permissions, notifications, and diagnostics

Hamza requests location access only for its current-location feature. You can decline it and select a city instead. Hamza also requests permission to display macOS notifications. Prayer notifications are scheduled locally on your Mac; they are not remote push messages sent by a Hamza server.

The app uses macOS diagnostic logging for notification scheduling and errors. These local records can include prayer identifiers, scheduled dates, and error descriptions. Hamza does not automatically upload those logs or include a third-party crash-reporting service. macOS manages the retention of its diagnostic records.

You can change location access in System Settings → Privacy & Security → Location Services, and notification permissions in System Settings → Notifications. The visual reminder and launch-at-login options are controlled through Hamza’s settings and the relevant macOS controls.

Resetting your local information

To clear Hamza’s saved location and preferences, open Settings → General → Reset preferences, choose Reset…, and confirm Reset and Quit. This restores the app’s settings to their defaults and removes its pending and delivered notifications.

Resetting Hamza does not reset macOS location or notification permissions, remove system diagnostic logs, or erase copies in your backups. Manage those separately through macOS and your backup tools. Removing the app alone may leave its saved preferences on your Mac.

This website

We use Databuddy to understand visits to this website and improve its performance and reliability. It collects page views, session activity, referrers and campaign information, browser and device details, approximate location derived from your IP address, performance measurements, JavaScript errors, outgoing-link clicks, and interaction measurements such as rage clicks, dead clicks, and form engagement.

Databuddy uses a random visitor identifier in localStorage and session information in sessionStorage instead of analytics cookies. We do not send names, email addresses, or account profiles through its identification feature. The tracker honors browser Do Not Track and Global Privacy Control signals. See Databuddy’s Privacy Policy for details about its processing and storage.

This website does not use advertising trackers. Its fonts are served with the website rather than loaded from Google when you visit.

Your browser sends ordinary connection information, such as your IP address, requested page, and browser information, to the service delivering the website. That service may process routine access and security logs to serve pages, maintain reliability, and prevent abuse.

Contacting us and visiting other services

If you email [email protected], we receive your email address, message, and any information or attachments you choose to include. The app’s feedback link opens an email draft with the app version in the subject; it does not automatically attach logs or send a message.

We use correspondence to respond to your request and retain it as needed to handle that request and any applicable legal obligations. Please include only the information needed for your question. Email providers process messages under their own privacy policies.

Links to external services, such as Qur’an references or social profiles, open only when you choose them. Those services handle your visit under their own privacy policies.

We do not sell personal information or share it for advertising. You can contact us to request access to, correction of, or deletion of information from your website visits or information you have supplied directly, subject to any applicable legal requirements. Locating website analytics records depends on the identifiers and information available. We cannot access your locally stored Hamza settings to delete them remotely.

Changes and questions

We may update this policy when Hamza or its data practices change. The current version and its last-updated date will be published on this page.

For privacy questions or requests, contact us at [email protected].