How Kadim protects volunteers’ privacy

You don’t need an account

To claim a slot you open a link and prove your number with a one-time code by text. There is no account and no password, so there is no password to steal and nothing for you to remember. If you never sign up, you serve exactly the same way, forever.

We store two things about you

Your first name and your UK mobile number. That is what a coordinator needs to know who’s coming, and what we need to send your reminder. Nothing about you is collected for advertising, because we don’t advertise and we don’t sell data.

Other volunteers see your first name, and only if you allow it

On a shared roster and to the rest of your crew, you appear by first name only. Nobody’s full name is shown to other volunteers or to anyone opening a shared link.

If you would rather not be named at all, tap Don’t show my name to the crew. From then on your slot reads 1 more volunteer, so the rota still looks honestly covered without naming you. Your coordinators still see who’s coming, because they need to, and you can turn your name back on the same way at any time.

There is no volunteer directory, and no messaging

You only ever see the crew of a rota you claimed yourself. There is nothing to browse, no profiles to search, no phone numbers on show, and no way for anyone to message you through Kadim. Kadim is not a social network and does not have a volunteer directory.

You can stop the texts, and it takes one ask

Kadim’s texts come from the name Kadim rather than from a phone number, so replying to one reaches nobody. To stop them, ask a coordinator at your mosque to take you off the team and to release any slots you are still holding: that ends the reminders, the gap alerts, the rota shares and the thank-yous. A sign-in code is only ever sent when you ask to sign in yourself. The how-to is Stop the texts .

Your safeguarding record belongs to one mosque

If a role needs a DBS check, Kadim stores five facts and no more: the check’s status, the certificate number, the issue date, the level, and the workforce. The certificate itself is never stored. The certificate number is encrypted, and every time anyone views, changes or exports a safeguarding record, Kadim writes an entry to an append-only audit log. Your record stays with the one mosque that holds it and is never shared with another. If you serve somewhere new, carrying your status across is your choice, done with your consent through the DBS Update Service, never by moving one mosque’s records to another.

What runs in the background: nothing that tracks you

Kadim sets only the cookies it needs to work. There is no analytics, no advertising, and no third-party tracking. Your data is held in the UK.

In short

You give a name and a number, to one mosque, for as long as they need you. You can be un-named to the crew in a tap, and un-subscribed from texts in a word. Everything sensitive is encrypted, audited, and never shared across mosques. That’s the deal, and it doesn’t change.