The Amanah Pledge
Amanah (أمانة) — the trust. This is Ahillah’s contract with you, and every technical decision in the codebase must be checkable against it. It is not a privacy policy written by lawyers to protect a company; it is a pledge written by builders to protect worship.
- 01
No ads
Worship is not ad inventory. There will never be an ad in Ahillah.
- 02
No trackers
No analytics SDKs, no advertising identifiers, no fingerprinting.
- 03
No data sale
Never sold, shared, brokered, or “partnered” — under any name.
- 04
Location stays on your device
Prayer times, Qibla, and the hijri calendar are computed on-device. Coordinates are never transmitted.
- 05
No phone number, no email
Your account is a username. We cannot leak what we never had.
- 06
Private conversations
Messages and calls are end-to-end encrypted. Push notifications carry an opaque ID, never content.
- 07
Honest exceptions, stated up-front
Scholar Q&A tickets are readable by the service so they can be routed and answered — the app says so on the ask screen, and you can ask anonymously.
- 08
Funded by the community
A waqf/donation model with optional supporter perks. Revenue never comes from attention or data.
- 09
Verifiable
The client is open source. Anyone can audit that this pledge is enforced in code.
The honest exception
One feature requires the service to read what you write: questions sent to verified scholars, so they can be routed, moderated, and — only with your explicit consent — published in the public answers library. The app states this on the ask screen itself, offers an anonymous-ask toggle, and links the fully private alternative: an end-to-end encrypted DM to a verified scholar. A pledge that hid this would not be worth the name.
The pledge is enforced in code, in the open. If we ever break it, don’t take our word for anything again — take the diff.
docs/amanah-pledge.md ↗