Stuck somewhere? We'll get you unstuck.

Sadd needs Screen Time / Family Controls permission. iOS treats this as a sensitive permission and only asks once.

• Go to Settings → Screen Time → See All App & Website Activity and make sure Screen Time is on.
• Open Sadd and tap Settings → Blocking → Re-authorize Screen Time.
• You'll see Apple's system dialog. Tap Allow.

If you denied it earlier, you may need to enable it manually under Settings → Screen Time → Sadd.

This is almost always a connectivity issue, not your account.

• Make sure you're on a stable network. Cellular hotspots and captive Wi-Fi often block Apple's auth endpoints.
• Quit the app fully (swipe up to close) and reopen.
• If it persists, check Apple System Status — Apple ID auth occasionally has outages.

If none of that works, email salam@sadd.app with your iOS version and we'll dig in.

Sadd uses the Muslim World League calculation method by default. You can change this under Settings → Prayer → Calculation method. Options include MWL, ISNA, Egyptian, Karachi, Umm al-Qura (Makkah), and a few others.

If the times still seem off, check that Settings → Privacy → Location Services → Sadd is set to While Using. Times are computed locally — your location is never transmitted.

You can't, actually. The shield runs as a system extension — even if Sadd is closed, iOS keeps the shield active. What you can do is:

• Disable Screen Time entirely from iOS Settings (this is intentional — Apple won't let an app lock you out of your own phone).
• Remove apps from your Sadd block list inside Sadd.

If you genuinely cannot keep the shield on, that's a discipline problem, not a software problem. Sadd's design assumes you want the barrier — the friction is the point.

When you tap a blocked app, Sadd doesn't open it — it asks you to write 60+ characters explaining why. Then it asks you to pick a duration (2, 5, or 15 minutes). Then it lets the app through for that window.

It's a forcing function. Most slips happen on autopilot — making you stop and articulate the intention breaks the loop. The text you write stays on your device.

Apple's Family Controls framework gives apps opaque tokens for the apps you've selected — meaning we can't see the real bundle ID, name, or icon. The generic name is iOS's behavior, not ours.

You set up a card once. Every time you bypass a shield (open a blocked app via the niyyah gate), an amount you pre-set is charged and routed to a charity you picked.

• Charity is selected during onboarding (or in Settings → Sadaqah).
• Amount is configurable per bypass.
• Payments are processed by Stripe — Sadd never sees your card number.
• Charges are batched weekly, not instant, to keep transaction fees from eating the donation.

Yes — go to Settings → Sadaqah → History for a full ledger. Each row links to the Stripe receipt. For year-end tax purposes (if your jurisdiction recognizes Islamic charity as tax-deductible), the charity will issue you a separate receipt directly.

At launch we support: Islamic Relief, Penny Appeal, LaunchGood, and a few region-specific partners. The full list is in Settings → Sadaqah → Recipient. We're adding more — if you'd like to nominate one, email us. Charities must have a Stripe Connected Account to receive payouts.

Only aggregate weekly totals: total minutes reclaimed, total bypass count, total sadaqah committed. They never see:

• Which specific apps you blocked or bypassed
• The text of your niyyahs
• Timestamps (when in the day you bypassed)
• Which charity you donated to

The Friday digest is intentionally low-resolution — accountability without surveillance.

Open the halaqa → tap the three dots → Leave circle. Your historical contributions stay in the aggregate stats for that circle (so the totals stay accurate for the other members), but no new data flows in after you leave.

From the Halaqa tab tap Create halaqa, name it, then share the 6-letter invite code with members. There's no member limit, but the Friday digest gets noisy past ~25 people — we suggest splitting larger groups.

Cancellations happen in Apple's Settings, not in our app (Apple's rules):

• iPhone: Settings → [your name] → Subscriptions → Sadd → Cancel
• You'll keep Pro until the end of the current billing period, then drop to the free tier.

Refund requests go through Apple: reportaproblem.apple.com.

Inside the app: Settings → Danger Zone → Delete account. This is irreversible and removes all your data within 30 days. See the Privacy Policy §5 for full details.

Apple Sign In is keyed to your Apple ID, so unfortunately if you lose access to that ID we cannot recover the Sadd account on a different ID — there's no password we can reset on our side.

If this happens, email us at salam@sadd.app. With proof of the old Apple ID we can manually migrate halaqa memberships and Pro status to your new account.

Sadd caches the full Quran offline after the first load. The first time you open the Quran tab it may take 5-10 seconds on a slow connection. After that, all 6,236 ayat load instantly from your device — no internet required.

If it's stuck, pull down to refresh, or restart the app. The cache rebuilds automatically.

Yes — Settings → Audio → Reciter. We support 8 reciters from the alquran.cloud public API: Alafasy, Abdul Basit, Sudais, Maher al-Muaiqly, Minshawi, Husary, Hudhaifi, and Shatri. Audio streams over HTTPS and respects your cellular data preferences.

See the Privacy Policy for the full table. The short version: your Apple ID identifier, a count of bypass events, halaqa memberships, sadaqah commitments. We do not see which apps you block, the text of your niyyahs, your contacts, your photos, your browsing history, or your location.

Email salam@sadd.app from the email tied to your Apple ID, requesting a data export. We send a JSON file with everything we store on you within 30 days.