How we source and verify
This page describes where our text comes from, the checks it passes before it is published, and the things we will not do. It is a description of process, not a statement of authority.
Sourced, never generated
Three rules govern everything on this site. They are constraints on what may be published, not aspirations.
A Qur'anic verse, a hadith, or a statement about either is shown with the reference it comes from — or it is not shown at all. There is no third option where something appears without provenance.
No fatwas, no verdicts, no declarations that a thing is permitted or forbidden. We present sourced text and say what our sources say. Questions of ruling belong with a qualified scholar who knows your circumstances.
Where our sources do not record something — a grading, a narrator, a chain — the page says so. A plausible-sounding answer supplied in place of a missing one is the specific failure this rule exists to prevent.
What we never do
These are not editorial preferences. Content that would breach any of them is withheld instead.
The three gates
Every supplication in our dua library must pass all three before it is published. They are applied to each record individually, and a record that fails any one of them is held back rather than corrected by guesswork.
Scripture quotes a great deal of speech in order to report or condemn it — the words of Iblis, the pleas of the damned, statements and questions that are not petitions at all. Presented as a dua, such a passage would be read as something to recite. Gate 1 identifies those records and routes them out of the library entirely. A page whose title alone would mislead is not fixed by a note in its body, because the title is what reaches the reader first.
Where a page carries a transliteration, that transliteration must come from a named source and must cover the whole of the Arabic shown beside it. Machine-generated romanisation is not accepted. A partial transliteration is treated as a failure, not a partial success: a reader following it would silently skip a line of the Arabic in front of them, and would never know.
Compiled datasets carry defects: a narrator's framing left inside the supplication, a chain of transmission bled into the Arabic, a truncated line, a translation that has absorbed part of the surrounding narration. Gate 3 is a deliberate scan of every record for these, rather than a reaction to the ones that happen to be noticed. Its findings are treated as a floor rather than a complete list, because a defect class found by accident has not been bounded.
From source to page
Publication is the last step, not the default state.
Arabic, translation and reference are read from an established compilation or collection. Nothing is composed at this stage or any later one.
Each record is tested individually. Automated checks find candidates; they do not clear them. A record that fails is held, and the reason is recorded against it.
Where a page carries notes on meaning or timing, they explain the wording already shown on that page. They introduce no history, no reward claim and no ruling. Pages carrying such notes say so on the page.
Nothing reaches the site automatically. A page that has not been approved is not published — it is absent from the site and from our sitemap, rather than quietly live. Approval is recorded per page.
Where our text comes from
Our supplications are drawn from established compilations and collections. The English is quoted from those sources; it is not our own rendering, and each page names the source it was taken from.
Where a compilation quotes an underlying collection, the page shows that collection's reference. Where our record carries no reference beyond the compilation itself, the page names the compilation and claims nothing further.
If we have it wrong
Compiled sources contain errors, and so will our reproduction of them. If you find a misattributed reference, a defective transliteration, a passage presented as a supplication that is not one, or a translation that does not match the Arabic beside it, please tell us. Reports that identify the specific page and the specific line are the ones we can act on fastest.