Editorial policy
- We rely on the stores' official sources and show the date information was checked.
- Stores can't buy rankings or reviews; commission never changes what we write about a code.
- We correct mistakes as soon as we find them, update the modified date, and list the change on the corrections log.
- We may use AI tools for drafting, and a human editor reviews content before it is published.
Who adds a code, and who sets the evidence level
Every test is performed and signed off under the Kobonak editorial team (Mudrek LLC). Each record carries a test-session ID. A stored screenshot carries the SHA-256 of that file. Content is overseen by editor Rami Hakim. He lives in Egypt, has a finance background, and is passionate about saving and shopping.
A code appears when it is written into the offer file in this repository and the site is rebuilt. Mudrek LLC’s editorial team edits that file.
The evidence level is not typed in. The build computes it from the record: the test date, the test result, the written benefit, the basket, and a completed-order or paid-cashback field when one exists. The build does not read affiliate status or a network name when it computes the level. A network-supplied offer is not raised by that fact.
What leaves the active lists
If an offer has a recorded end date before the Dubai day of the build, it leaves the active lists. A checkout-tested label stays for at most 14 days after the test. The next Gulf day the card says the test is stale and the code stays listed.
Corrections
When a page disagrees with the record, we change the page and add a dated entry to the corrections log: what was wrong, what changed, and which pages. Entries are not deleted. We aim to review reports within 3 business days. That is a target, not a measured response time.