This is a summary of how Jamaat Cloud works today. The full privacy policy is being finalised and will replace this page. Questions: salaam@jamaatcloud.com.
Whose data it is
Each Jamaat’s records — members, dues, receipts, requests — belong to that Jamaat. Every read and write is scoped on our servers to the Jamaat the record belongs to; one Jamaat’s office cannot see another’s.
What a Mumin can see
In GoMumin a Mumin sees their own records and their household’s dues. Other members appear only through a directory view (name, handle, photo, Mohalla) — never their phone, address or personal records.
Passwords
Passwords are stored only as one-way hashes. Nobody — including the Jamaat office and our staff — can read a password back; a forgotten password is reset, not revealed.
Cookies
We use one sign-in cookie per area (Jamaat office, Console, GoMumin). They are HTTP-only, so page scripts cannot read them, and each is limited to its own address. We do not use advertising or tracking cookies.
Website analytics
On this public website only, we count page views, page speed and clicks on buttons such as “Request a Demo” using Vercel Web Analytics and Speed Insights. They set no cookies and collect no names, ITS numbers or contact details; visits are counted in aggregate. The Jamaat office, Console and GoMumin are not measured.
Your browser
To load quickly, the app keeps a small cache of public reference data (prayer timings, menus, the list of Jamaats) in your browser. Personal records are not stored on your device, and signing out clears the cache.
Sign-in records
Sign-in attempts are logged with time and IP address to protect accounts from password guessing, and kept for 180 days.
Enquiries
If you write to us through the contact form, we keep what you send so we can reply.