Please read this Privacy Policy carefully. It explains how Uhud Labs LLC (“Uhud Labs,” “we,” “our,” or “us”), a Texas limited liability company, collects, uses, shares, and protects information when you visit uhudlabs.com or khutbahapp.com (the “Sites”), or use our mobile applications Sabiq, Heemu, and Zeir (together with the Sites, the “Services”). If you do not agree, please do not use the Services.
1. Information we collect
We collect only what we need to operate the Services.
Account information
When you create an account or sign in through Google or Quran.com, we may receive your name, email address, and profile picture. Sabiq also supports Sign in with Apple on iOS, which may provide your name and email address, including an Apple private relay address if you choose one. We do not receive your sign-in provider’s password. You may choose a display name that is not your real name. Our apps do not allow profile photo uploads or access your photo library. Sabiq’s optional Qibla camera preview is described below.
Activity and progress
- Sabiq: Quran recitation progress and reading-mode preference (Mushaf full-page vs Ayah-by-ayah), country and gender (both required at onboarding; gender is used to tailor duas and reminders because some azkar differ between men and women), dhikr and adhkar completion counts, Seeds and reward balances, Akhirah Account totals, streaks, and causes you direct in the app.
- Heemu: reminder settings and reminder-event counts, duration, response, and Quran reading completed. Selected and triggering app names remain on your device; we receive only counts and durations.
- Zeir: titles played, playback position, listening history, and saved titles. Offline audio remains on your device.
Referrals, permissions, and device data
Sabiq records referral relationships when a new account uses an invitation code, but does not access your contacts. Heemu uses device permissions to detect a selected foreground app and display a reminder; it does not read screen content, messages, or typed input. You can revoke these permissions at any time.
Sabiq stores device brand and model, timezone, device type, and app language to deliver reminders and diagnose issues. Sabiq requires you to provide your country during onboarding; this account information is separate from the device-local location used for prayers.
Sabiq prayer times, Qibla, and camera
You can optionally allow location access while using Sabiq to set prayer times and support the Qibla compass. You can instead select a city from the app’s built-in city list for prayer calculations. On iOS, opening the Qibla compass may still request location permission to determine true north, even if you selected a city. Prayer times and the Qibla bearing are calculated on your device. The selected city or coordinates, timezone, and calculation settings are stored on your device and are not sent to Sabiq’s backend by these features. Sabiq does not track your location in the background; Qibla sensor updates stop when you leave the screen or the app becomes inactive. Update your prayer location when you travel.
If you choose Qibla camera mode and allow camera access, Sabiq displays the direction over a live camera preview. It does not take, save, or upload photos or videos from this preview. Microphone capture is disabled. You can use the compass without camera access and can revoke camera or location permission in device settings.
Sabiq prayer checkmarks, reminders, and widget
Your prayed or missed checkmarks and prayer reward receipts are stored locally, separately for each Sabiq account on that device. Individual prayer checkmarks are not uploaded. Prayer Seeds contribute to your pending Seeds balance; when you seal, Sabiq sends the combined Seeds amount, a request identifier, and timezone to its backend under your account, rather than sending individual prayer records. The backend also receives combined expired Seeds totals and the date of expiry.
Prayer reminders are off by default. If enabled with notification permission, they are scheduled on your device using your prayer settings. The prayer widget receives a locally calculated timetable, a city label (or “current location”), timezone, language, and display settings through shared storage on the device, including an iOS App Group. This widget data does not include your prayer checkmarks or raw coordinates and is not a server upload.
Sabiq reflections and community interactions
Where reflection features are enabled, unpublished reflection and comment drafts are saved on your device. Sabiq may also keep a local copy of your published reflection for the optional QuranReflect sharing step. When you publish a Sabiq reflection or comment, our backend stores its text, your account identifier, the relevant verse or post, timestamps, and, for reflections, the selected language. Likes are linked to your account and the post. Reports contain the reported post or comment, your account identifier, the reason you submit, and a timestamp. These records support community features and handling abuse reports. Public visibility and deletion are explained below.
When enabled, Sabiq also displays reflections from QuranReflect through Quran Foundation services. Publishing to Sabiq does not automatically publish to QuranReflect. If you choose to connect your Quran.com account and share or interact with QuranReflect, the authorized text, verse or post identifiers, likes, comments, or reports are sent through Sabiq’s backend to that service. Account credentials and access tokens needed for these requests are processed by our backend; connection tokens are held in secure storage on your device. We keep account-linked delivery receipts with identifiers, content hashes, timestamps, and delivery results to prevent duplicate submissions and resolve uncertain delivery. These receipt records do not store the submitted text or OAuth tokens. Quran.com connections also support account access, two-way bookmark synchronization, and sending the chapter, verse, and duration of reading sessions to Quran.com for reading progress. Reading public QuranReflect material sends the selected verse, language, and page through our backend to the content service.
Notifications, communications, and Sites
Where enabled, we collect a push token, timezone, device type, and language. Sabiq uses Firebase Cloud Messaging for push notifications, separately from its local prayer reminders; Zeir uses OneSignal; Heemu does not collect a push token. If you contact us, we receive your contact details and message. Vercel processes standard server logs, such as IP address, browser type, and pages visited, to deliver and protect the Sites.
Product analytics
Our apps do not contain advertising, attribution, third-party analytics, or crash-reporting software. Sabiq’s first-party analytics include account-linked records, as well as aggregate reports. They include device information, last activity, session duration, Quran and dhikr activity counts and time, reading preferences, and Seeds activity. When a signed-in user deliberately opens the reflections panel, Sabiq records an event identifier, the opening time, and the local UTC offset, and sends them with the user’s account identifier. The backend stores the opening time, derived local date, and receipt time. This event does not contain reflection text or establish that a reflection was read, and it does not award Seeds.
We use these records to provide progress features, understand feature use, diagnose issues, and improve Sabiq; administrative reports summarize this activity. App stores may separately provide aggregated crash and performance reports. Requesting an on-device camera or location permission is separate from sending data to us: the Qibla preview and prayer coordinates described above are not uploaded by those features. We do not collect your contacts, health data, or payment-card details.
2. How we use information
- Create, maintain, secure, and manage accounts.
- Provide progress, listening, reminder, Seeds, reward, and history features.
- Deliver notifications you enable and optional progress emails; every optional email includes an unsubscribe link.
- Respond to support, prevent abuse, diagnose problems, improve the Services, and comply with law.
We do not use personal data for third-party advertising and do not sell or rent it.
3. Legal bases for EEA and UK users
- Contract: account creation, progress tracking, core features, and support.
- Legitimate interests: security, abuse prevention, troubleshooting, and expected improvements.
- Consent: optional notifications and progress emails, which you may disable at any time.
- Legal obligation: required retention or disclosure.
4. Information visible to other users
If you participate in Sabiq’s leaderboard, others may see your display name, initials-based color avatar, country, XP, level, and streaks. The leaderboard does not show your photo, email, reading history, or the activity behind totals. Reports of offensive or impersonating names are tied to the reporter’s account so we can investigate misuse. We may reset names or suspend accounts that breach our Terms.
Sabiq community reflections and comments are public, including to readers who are not signed in. Public responses include the text, display name, an author identifier linked to the Sabiq account, verse context, and comment timestamps. Like and comment counts are visible; Sabiq’s public interaction responses do not list individual likers or report reasons. Do not include information you want to keep private in public content. QuranReflect content is displayed with the author information supplied by that service and is subject to its own visibility rules.
6. International transfers and retention
We are based in the United States, and providers may process data in the United States and other countries. Where required, EEA and UK transfers use safeguards such as Standard Contractual Clauses or an applicable Data Privacy Framework certification.
We retain personal data while your account is active or as needed to provide Services. Sabiq’s account-linked reflection-open events and delivery receipts do not have an automatic time-based deletion schedule. The device’s pending reflection-open queue is limited to 500 events; events older than 90 days are discarded when the queue is processed, and successfully sent events are removed from that queue. This is an upload-queue limit, not a 90-day retention limit for server records.
Deleting a Sabiq reflection or comment in the app hides it from public responses but retains its text and associated records in our database. Removing a like deletes that like record. Deleting the Sabiq account removes the account-linked reflection posts, comments, likes, reports, delivery receipts, and reflection-open events from the active database through account deletion. Sabiq account deletion does not delete your separate Quran.com or QuranReflect account or content held by those services. Disconnecting a QuranReflect connection removes the local connection, not already published content; use that service’s controls or support for its account and content deletion.
Local prayer settings, checkmarks, widget data, reflection drafts and saved publication copies, hidden-author preferences, and pending analytics can remain on the device after Sabiq account deletion; the account-deletion action does not clear these stores. Provider logs and backups are separate from the active database, and this policy does not promise a fixed deletion period for them. Contact us about retained information or an erasure request. Information required by law or needed to resolve disputes may also be retained.
7. Your rights and choices
Depending on where you live, you may have rights to access, correct, delete, or receive a copy of personal data; object to or restrict processing; withdraw consent; and appeal or complain to a regulator. We do not discriminate against anyone exercising applicable rights. Email us to submit a request; we may verify your identity.
You can disable notifications in device settings and unsubscribe from optional emails using the email link. In Sabiq’s reflection controls, you can report a post or comment and hide an author’s posts and comments on that device; this hiding preference is stored locally and is separate from leaderboard blocking. You can also turn prayer reminders off, select a city instead of using GPS for prayer calculations, and revoke location or camera access in device settings.
8. How to delete your account
You may request permanent account deletion from the applicable app’s Settings. For Sabiq, the scope and limits of deletion, including local data and connected services, are described in section 6. Sabiq users—including users who no longer have access to the app—can follow the public instructions on our Sabiq account deletion page.
You may also request deletion by emailing support@uhudlabs.com from the address associated with your account.
9. Children’s privacy
The Services are not directed to children under 13 or the higher minimum age required locally, which may be up to 16 in parts of the EEA. We do not knowingly collect their data. Contact us if you believe a child has registered; we will delete the account promptly.
10. Security
We use reasonable technical and organizational safeguards, including encrypted connections, access controls, and database row-level security. No system is perfectly secure. We will provide legally required breach notices.
11. Changes to this policy
We may update this Policy and will post the new version and date. We will provide additional in-app or email notice of material changes. Continued use after an update takes effect means you accept the revised Policy.
12. Contact us
Uhud Labs LLC
Email: support@uhudlabs.com
10723 Lighthouse Peak Trce
Richmond, TX 77406
United States