IMS · provided by Muslim Welfare House
Data processing agreement
Last updated 31 October 2026
This agreement is between each madrasah that uses IMS (the controller) and Muslim Welfare House, 174 Welford Road, Leicester, LE2 6BD (the processor, “we”). It forms part of the terms of service and meets the requirements of Article 28 of the UK General Data Protection Regulation and the Data Protection Act 2018.
1. What is processed
- Subject and purpose: providing IMS to the madrasah — storing, displaying and sending the information the madrasah records, so it can run its classes, keep families informed, manage fees and staff, and keep children safe.
- Duration: for as long as the madrasah uses IMS, and until its information is deleted under section 9.
- People: students, parents and guardians, staff and volunteers, and payers into the madrasah’s bank account where the bank feed is used.
- Information: names, dates of birth, contact details, addresses, school details, attendance, learning and Qur’an/Hifz progress, assessments, reports, behaviour notes, messages, fees and payments, staff and pay details, consents, and bank transactions received.
- Special category information: health and medical details and learning needs; safeguarding records; and, by the nature of a madrasah, information that may indicate religious belief.
2. Instructions
We process the information only on the madrasah’s documented instructions — these terms, and what the madrasah does in IMS — unless the law requires otherwise, in which case we will tell the madrasah first unless the law forbids it. We will tell the madrasah if we think an instruction breaks data protection law.
3. Confidentiality
Everyone we allow to access the information is bound by a duty of confidentiality, and accesses it only as needed to run, support or fix IMS.
4. Security
We keep appropriate technical and organisational measures in place, including:
- encryption of every connection, and further encryption in the database of the most sensitive fields (medical needs, addresses, safeguarding notes, bank details and bank payment references);
- passwords stored only as one-way hashes, and limits on repeated sign-in attempts;
- server-side checks on every request, so each person reaches only what their role and the madrasah allow, and one madrasah can never reach another’s information;
- a log of important changes and of every view of a safeguarding record;
- nightly backups, kept for 14 days.
5. Sub-processors
The madrasah authorises us to use these sub-processors:
- Supabase — database hosting (European Union);
- Hetzner Online — server hosting (European Union);
- Resend — sending email (United States, under safeguards recognised in UK law);
- TrueLayer — read-only access to the madrasah's own bank account, only if the madrasah turns the bank feed on (United Kingdom).
Each is bound by a written contract with data protection obligations equivalent to these. We will give the madrasah at least 30 days’ notice before adding or replacing a sub-processor, so it can object; if it does and we cannot resolve it, the madrasah may end the agreement. We remain responsible for our sub-processors.
6. International transfers
Information is stored in the UK or European Union, which the UK recognises as adequate. Where a sub-processor is elsewhere, we transfer information only under safeguards recognised in UK law, such as the UK–US data bridge or the UK International Data Transfer Agreement or Addendum.
7. Helping the madrasah
IMS lets the madrasah view, correct, export and remove the information it holds, so it can answer requests from its families and staff. Where it cannot do something itself, we will help, taking into account the nature of the processing. We will also help with security, breach notification, data protection impact assessments and consultation with the ICO, so far as they concern IMS. If a request comes to us directly, we will pass it to the madrasah without delay.
8. Personal data breaches
If we become aware of a breach affecting the madrasah’s information, we will tell the madrasah without undue delay, and in any case within 48 hours, with what we know of its nature, likely effects and the steps taken — so the madrasah can meet its own 72-hour duty to report to the ICO where required.
9. At the end
When the madrasah stops using IMS, it can take a copy of its information. We then delete it within 90 days, and backups containing it expire within a further 14 days, unless the law requires us to keep it.
10. Showing compliance
We will give the madrasah the information it reasonably needs to show that these obligations are met, and allow and contribute to reasonable audits, on reasonable notice.
11. Contact
Questions about this agreement, or to report a concern: iqra.administrator@gmail.com.