Database trust
Trust the operator.
If we wanted to alter or hide a donation, we could. You'd have no way to tell.
Money never touches the platform. Every donation's hash is permanently anchored on a public ledger that anyone can audit.
What actually happens when someone donates.
Donor visits a campaign on Charity-IQ
Clicks Donate — redirects to the charity's own Zain Cash merchant page
Pays via Zain Cash. Money goes donor → ZC → charity wallet. Charity-IQ never touches the funds.
Donor returns to a receipt page on Charity-IQ
The donation hash is anchored to Polygon mainnet within seconds
Donor can verify the donation on polygonscan.com — no Charity-IQ involvement needed
Two models of trust. We picked the one that doesn't ask you to trust us.
Database trust
Trust the operator.
If we wanted to alter or hide a donation, we could. You'd have no way to tell.
On-chain trust
Trust the math.
The Merkle root of every batch is published on Polygon. Tampering with the database would not match the on-chain proof. Anyone can verify.
This is a real anchor from Polygon mainnet. Click to verify it yourself.
0x5ecb08bcc78f56d52241ce7422a56a5d2689234b28f64be9680e3b6bc098426bThis batch contains real donations from charities on the platform. Click to verify on Polygon.
View on polygonscan.comNo. Money flows donor → Zain Cash → charity wallet. We are a directory and trust layer, not a payment aggregator.
Charities keep their Zain Cash merchant accounts. On-chain anchor records persist on Polygon forever. Donor receipts remain verifiable.
A fraction of a cent per donation. We absorb the cost via the subscription model — donors pay nothing extra.
No. The Merkle proof is generated from the actual donation data; tampering would not match the on-chain hash.