Cookies and browser storage

This page is a draft under legal review: it describes the service as it works today, and the reviewed wording will replace it.

This page lists what Jumaah’s website and apps keep in your browser, and why. None of it is used for advertising, and none of it is sold.

The worshippers’ page and mosque screens

The page worshippers open on their phones sets no cookies, asks for no name or number, and loads no analytics or third-party scripts. It keeps two things in the browser’s local storage: a random device code used only for the live connection, which is not linked to any person, and a copy of the latest khutbah shown, so the page can show it again straight away when it reloads.

A mosque screen keeps its screen link and the same kind of copy. These identify the screen, not a person.

The mosque team’s apps

The admin and imam apps use one cookie, jumaah_rt, to keep you signed in. It is HttpOnly, so page scripts cannot read it; it is sent only to the service’s sign-in address, and it is used for nothing else. Signing out removes it.

The apps also keep in local storage who is signed in and which mosque is selected (never the sign-in tokens themselves), your language choice, Arabic or English, and a device code so that the live khutbah is driven from one device at a time.

This website

The Jumaah website sets no cookies of its own. Cloudflare Web Analytics is enabled on it and counts visits; we do not use it for advertising or to build profiles of visitors. The forms are protected by Cloudflare Turnstile, which may keep what it needs in your browser to tell people from bots; that storage is Cloudflare’s own.

Clearing them

You can remove all of this at any time by clearing this site’s cookies and site data in your browser’s settings. On the worshippers’ page, clearing it only means the page starts afresh next time. If we add anything to this list, this page will be updated first.