Editorial Policy

1. Calculation Method Integrity

Prayer schedules are derived from Aladhan API methods aligned to our coverage area:

• Pakistan: University of Islamic Sciences, Karachi (Aladhan method 1) with Hanafi Asr.
• UAE: Gulf Region method (Aladhan method 8).
• Fallback: Local Adhan JS library if the API is unreachable.

Details and disclaimers: Sources & Methodology.

2. Fact-Checking and Expert Review

Our educational content, calculations, and mathematical models undergo a multi-layered review process:

1. Scientific Peer-Review:Our calculation engine and timezone libraries are audited against NASA Jet Propulsion Laboratory (JPL) solar data to ensure the sun's altitude calculations are mathematically sound.
2. Theological Alignment: We reference authentic classical and contemporary Fiqh sources (such as Hanafi, Shafi, Maliki, and Hanbali rulings) to ensure descriptions of twilight angles and shadow lengths are representative of traditional Islamic jurisprudential consensus.
3. Review Dates: All calculators and explanatory texts are reviewed quarterly to adjust for timezone database updates (e.g., changes to Daylight Saving Time policies).

3. Transparent Disclosures

Because local mosques and Islamic centers must often adjust times for congregational convenience (Jamaat offsets) or adopt specialized local methods (such as the 18-degree vs 15-degree rule or seasonal rules), we explicitly state:

“All astronomical calculations are estimates. While they are highly accurate, worshippers are encouraged to consult their neighborhood mosque for official, locally approved Jamaat times.”

4. Editorial team & review cadence

• PrayersTimes.com Editorial Team — Prayer-time methodology & content review. Reviews Aladhan method alignment, Pakistan Hanafi / UAE Gulf defaults, and trust-page accuracy.

Methodology last aligned with Aladhan API defaults: July 2026. Trust documentation: Sources · llms.txt.

5. Corrections and Error Reporting

We are committed to instant corrections if any astronomical discrepancy or typo is detected. If you spot a calculation mismatch or have feedback regarding local calculation methods, please reach out to our team immediately through our contact form. We log and process correction reports within 48 business hours.