Privacy Policy

Effective date: {{EFFECTIVE_DATE}}
Operator: {{OPERATOR_NAME}}, {{OPERATOR_ADDRESS}}, {{OPERATOR_COUNTRY}}
Privacy contact and Data Protection Officer: {{PRIVACY_EMAIL}}

In short

Your mosque decides what it records about you, and it is in charge of that data. We run My Mosque for the mosque and keep that data safe. We are in charge only of your account (email and sign-in), your support messages and billing contacts. Data is stored in the EU and encrypted on its way to and from our servers. On your phone it sits in an encrypted database. We show no ads, use no analytics or tracking tools, and never sell or share your data. You can see, fix, export or delete your data. Ask your mosque for mosque records, and ask us for your account.

1. Who is responsible for your data

My Mosque has two kinds of "responsible party". This matters because it tells you who to ask.

What this means for you: For questions about what your mosque records, who in the mosque can see it, or to change or delete it, ask your mosque first. We will help the mosque answer. For your account or support tickets, ask us at {{PRIVACY_EMAIL}}.

Each mosque signs our Data Processing Addendum, which sets out how we process data for it.

2. What we collect

2.1 Account data (we are controller)

• Email address and the sign-in method (email and password, or Google).
• If you sign in with Google: your Google account ID, name and email, as shared by Google with your permission.
• Your password, stored only as a one-way hash by our sign-in provider (Supabase Auth). We never see it.
• Security records: sign-in times and the device's app version, used to keep accounts safe. CHECK exactly what Supabase Auth logs (for example IP address).

2.2 Mosque data (the mosque is controller)

The mosque chooses which of these it uses. Many are optional.

• Profile: name, email, phone, address, date of birth, photo, profile code and member number.
• Member registration (if the mosque turns it on): the details the mosque asks for; copies of an ID card, passport or driving licence; proof of address; signatures on forms such as a membership declaration, data consent, Gift Aid declaration (UK) or SEPA direct debit mandate (euro area, which includes bank account details).
• Finance: donations, zakat, fitrah, dues and chanda, "I paid" reports, receipts, expenses, staff pay and payslips, petty cash, bank accounts and reconciliation.
• Governance: meetings, attendance, minutes, motions, elections and nominations. Ballots are secret: the server counts them, and how a person voted is not shown to anyone.
• Community: announcements, events, questions on finance entries and answers, documents and files.
• Groups of mosques: if a mosque joins a group, the group's staff can see the mosque's data that their group role allows.
• Audit log: who did what and when in the mosque's records, so the mosque can check its books. It does not keep ballots, registration answers, signatures or reset reasons.

2.3 Support data (we are controller)

When you use the in-app contact form, your message, your email, your mosque's name and any details you include go to our help desk at {{WEBSITE}}.

2.4 Billing data (we are controller)

When a mosque buys a plan on {{WEBSITE}}, Stripe collects the payment. We receive the billing contact's name and email, the organisation's name and address, the plan, invoices and payment status. We never receive or store card numbers.

2.5 What we do not collect

• No advertising IDs, no analytics, no tracking SDKs, no cookies for tracking.
• No crash-reporting tools at present. CHECK before each release; if one is added, this policy will be updated first.
• Your app passcode and the keys that encrypt the database on your phone stay on your device. They are never sent to us.
• Prayer times are calculated on your phone. CHECK whether the app uses the device's location; if it does, say whether the location leaves the phone (it should not).

3. Why we use data and our legal bases

3.1 As the mosque's processor

We use mosque data only to provide the Service to the mosque: store it, sync it between devices, show it to the people the mosque allows, make reports and receipts, send notifications, back it up and keep it secure. The mosque's legal basis covers this. See section 6 for religious data.

3.2 As controller

We do not send marketing emails unless you ask for them. We never make decisions about you by automated means that have legal or similarly important effects.

4. Who can see your data inside your mosque

• Members see what the mosque's transparency settings allow, plus their own payments, receipts and records.
• Officers see what their role allows. Permissions are enforced on our server (Postgres row-level security), not just hidden in the app.
• ID papers (ID card, passport, licence) are seen only by you and the officers who approve members. Each time an officer opens one, it is logged. They go only to the mosque you register with.
• Salaries are seen only by the staff member, payroll and the finance committee, unless the mosque chooses otherwise.
• Bank details are visible to members only, not the public.

5. Who we share data with

We never sell your data and never share it for advertising. We use a small number of service providers ("subprocessors") who process data for us under contract:

We may also disclose data if the law requires it (for example a valid court order). Where we can, we will tell the mosque first. If {{OPERATOR_NAME}} is reorganised or the Service is transferred, data would move to the new operator under this policy, and we would tell you.

6. Religious data and special care

Being a member of a mosque can reveal a person's religion. Data protection laws treat religious belief as special-category or sensitive data.

What the mosque must do: have a lawful basis to process it. Under GDPR and UK GDPR, the usual basis is Article 9(2)(d): a not-for-profit body with a religious aim may process data about its own members, former members and people in regular contact with it, in the course of its legitimate activities, with safeguards, and without disclosing it outside the body without consent. Where that does not fit (for example for non-members), the mosque may need explicit consent (Art. 9(2)(a)). Other countries have similar rules (see section 13).

What we do to protect it:

• Each mosque's data is kept apart from every other mosque's by server rules.
• Only people the mosque approves can see member lists. Members nominate candidates by profile code, so lists cannot be scraped.
• ID papers are restricted and every officer view is logged.
• Data is encrypted in transit and at rest, and encrypted on the phone.
• The phone app has a passcode lock, blocks backups and device transfer, and hides its screen in the recent-apps view.
• We never use the data for ads, profiling or anything other than running the Service.
• A mosque's data is never shown to another mosque, unless the mosque chooses to join a group.

7. How long we keep data

When a mosque closes its space, we delete its data within 90 days after giving its officers a chance to export it (CHECK period), except billing records we must keep.

8. Deleting your account

You can delete your account in the app (Settings) and on {{WEBSITE}}.

When you do:

• Your sign-in and account are deleted.
• Your profile is removed from your mosques. CHECK that registration papers (ID copies) are deleted at the same time, unless a mosque must keep them by law.
• Financial records stay with the mosque, because mosques must usually keep their books by law (for example donations, Gift Aid claims, payroll). Where possible your name is removed or replaced, so the record no longer points to you.
• Secret ballots were never linked to you, and stay as counted totals.
• Audit log entries stay with the mosque's books, linked to an anonymised identity where possible.
• Copies in backups disappear on the normal backup cycle.

If you only want to leave a mosque, you can do that in the app. Your account stays.

9. Security

We protect data with:

• Encryption in transit (TLS) for all traffic to our servers.
• Encryption at rest in the cloud database and file storage.
• Row-level security on every table, per mosque and per role, enforced by the server.
• Append-only ledger and audit log: posted entries cannot be edited or deleted.
• An encrypted database on Android (SQLCipher, key in the Android Keystore). CHECK the equivalent on iOS, web and Windows.
• A required app passcode for people who run a mosque, kept only on the device. Five wrong tries signs out and wipes the phone's copy.
• Private file storage with short-lived links and file type and size limits.
• Server functions that run with the least privilege needed; internal functions cannot be called from outside, and nothing can be called without signing in.
• Secrets kept out of the code, and security checks before each release.

No system is perfect. If a breach affects your data, we will tell the mosque without undue delay (and within 72 hours of becoming aware), and tell you and the authorities where the law requires.

10. International transfers

We store Service data in Supabase's EU region. Some providers (for example Stripe, Google and email delivery) may process data in other countries, including the US. When data leaves the EU, EEA or UK, we rely on an adequacy decision (such as the EU-US Data Privacy Framework, where the provider is certified) or on the European Commission's Standard Contractual Clauses (with the UK Addendum for UK data), plus extra safeguards where needed. You can ask us for a copy of the relevant safeguards at {{PRIVACY_EMAIL}}.

If you live outside the EU, your data is transferred to the EU when you use the Service. Section 13 explains what this means in your country.

11. Your rights

Depending on where you live, you have the right to:

• Access your data and get a copy.
• Correct wrong data. (Some profile details lock once saved; you ask an officer to correct them in the app.)
• Delete your data.
• Export your data in a common format (portability).
• Object to or restrict some uses.
• Withdraw consent at any time, where we or your mosque rely on consent.
• Complain to your data protection authority.

How to use them:

• For mosque records, contact your mosque. We will help the mosque respond.
• For your account, support tickets or billing, email {{PRIVACY_EMAIL}}.
• If you contact us about mosque records, we will pass your request to the mosque and let you know.

We reply within one month (or the time your law sets). We may ask you to confirm your identity. Using your rights is free.

12. Children

My Mosque is meant for mosques and adults. Children under 16 (or the age your law sets) do not create their own accounts. A mosque may record a child (for example as a family member or student) only with a parent's or guardian's consent, and the mosque is responsible for that consent. We do not knowingly collect data from children for any other purpose. If you think a child's data was added without consent, contact the mosque or {{PRIVACY_EMAIL}}.

13. Country summaries

These summaries add to the rest of this policy. If your law gives you more rights, you have them.

European Union and EEA (GDPR)

All of this policy applies. You may complain to your local supervisory authority. CHECK: if {{OPERATOR_NAME}} is not established in the EU, appoint and name an EU representative (Art. 27).

Germany

GDPR and the Federal Data Protection Act (BDSG) apply. Mosque associations are usually not covered by church data protection rules (Art. 91 GDPR), so GDPR applies in full. Payroll and staff data are employee data, with extra limits on use. We store or read nothing on your device beyond what is strictly needed for the Service (TDDDG, section 25). Liability rules for Germany are in the Terms of Service, section 16.

France

GDPR and the French Data Protection Act (Loi Informatique et Libertés) apply. You may give instructions about what should happen to your data after your death. You may complain to the CNIL (cnil.fr).

United Kingdom (UK GDPR)

UK GDPR and the Data Protection Act 2018 apply, including the Art. 9(2)(d) basis for religious not-for-profit bodies. Gift Aid declarations are kept by the mosque to meet HMRC rules. You may complain to the ICO (ico.org.uk). CHECK: appoint a UK representative if needed.

United States (CCPA/CPRA and state laws)

• We do not sell or share personal information for cross-context behavioural advertising, and we do not use it for targeted ads.
• California law (CCPA/CPRA) applies mainly to for-profit businesses, and may not apply to us or to mosques. We still honour the rights to know, delete, correct and not be discriminated against.
• Several state laws (for example Colorado, Oregon, Virginia, Connecticut, Texas) treat religious beliefs as sensitive data. Some of these laws cover nonprofits. We process sensitive data only to provide the Service the mosque asked for.
• Children under 13: no account of their own; records only through a mosque with parental consent (COPPA).
• Ask at {{PRIVACY_EMAIL}}. You may use an authorised agent. You may appeal a refusal by replying to our answer.

Canada (PIPEDA)

Your consent covers storing data in the EU, where it is protected by our contracts. Ask our privacy officer at {{PRIVACY_EMAIL}}. You may complain to the Office of the Privacy Commissioner of Canada. In Quebec (Law 25), you may also ask about automated decisions (we make none) and about transfers outside Quebec.

Australia (Privacy Act 1988)

Religious beliefs are "sensitive information" under the Australian Privacy Principles. Mosques should collect them only with consent or another allowed basis. Data is held overseas (EU) under contracts that protect it. We follow the Notifiable Data Breaches scheme where it applies. You may complain to the OAIC.

Pakistan

At the time of writing, Pakistan has no comprehensive data protection law in force; the Personal Data Protection Bill is in draft (CHECK current status). The Prevention of Electronic Crimes Act 2016 protects against unlawful access. We apply this policy's full protections to users in Pakistan.

India (Digital Personal Data Protection Act 2023)

The mosque is the Data Fiduciary and we are its Data Processor. For our own account data, we are the Data Fiduciary. You may ask for a summary of your data, correction, erasure, and nominate someone to act for you after death or incapacity. Data of children under 18 needs verifiable consent from a parent or guardian, which the mosque must obtain. Grievances: {{PRIVACY_EMAIL}}; you may then go to the Data Protection Board of India. CHECK the timing of the DPDP Rules phases.

Bangladesh

CHECK the status of Bangladesh's personal data protection law (a Personal Data Protection Ordinance was under consideration in 2025). Until in force, we apply this policy's protections. The mosque should get consent for registration papers.

Indonesia (PDP Law No. 27 of 2022)

The mosque is the personal data controller and we are its processor. Children's data and personal financial data are "specific" personal data that need extra care; children's data needs parental consent. You may access, correct, delete, withdraw consent and object. We notify the mosque of a breach so it can tell you and the authority within 3 x 24 hours.

Malaysia (PDPA 2010, as amended 2024)

Religious beliefs are "sensitive personal data" and need explicit consent or another allowed basis. As a data processor we must keep data secure and notify breaches. You may access and correct your data, and (where it applies) port it. Data is transferred to the EU under safeguards.

Saudi Arabia (PDPL)

Religious belief is sensitive data. The mosque must have a lawful basis, usually consent. Data is transferred outside the Kingdom to the EU under the PDPL transfer rules and appropriate safeguards (CHECK transfer conditions and any registration with SDAIA). You may access, correct, delete and request a copy of your data.

United Arab Emirates (PDPL, Federal Decree-Law 45 of 2021)

Religious belief is sensitive data. The mosque needs a lawful basis, usually consent. Transfers to the EU rely on adequate protection or contract safeguards. Users in DIFC or ADGM are covered by those zones' own laws. CHECK the status of the executive regulations.

Türkiye (KVKK, Law No. 6698)

Religion is special-category data that needs explicit consent or another basis under Article 6. Transfers abroad use standard contracts notified to the Authority (Article 9, as amended in 2024) (CHECK notification duty). You may apply to the mosque (data controller) and then to the KVKK Board. The mosque may need to register with VERBIS.

South Korea (PIPA)

Beliefs are sensitive information and need separate consent. Children under 14 need a legal guardian's consent. Data is transferred to the EU (Supabase) and to the other providers in section 5, for the purposes in section 3, kept as in section 7; you may refuse, but then the Service cannot be used. You may access, correct, delete and suspend processing. CHECK whether a domestic representative is required.

Nigeria (NDPA 2023)

Religious beliefs are sensitive personal data and need explicit consent or another allowed basis. Transfers to the EU rely on adequate protection or contract safeguards. You may complain to the Nigeria Data Protection Commission. CHECK whether registration with the NDPC is required.

14. Changes to this policy

We will post any change here with a new effective date. If a change is important, we will tell you in the app or by email at least 30 days before it applies.

15. Contact

Privacy and Data Protection Officer: {{PRIVACY_EMAIL}} Support: {{SUPPORT_EMAIL}} Post: {{OPERATOR_NAME}}, {{OPERATOR_ADDRESS}}, {{OPERATOR_COUNTRY}} Website: {{WEBSITE}}