Child Safety Standards

Jamia is committed to creating a safe environment for all users and to the absolute protection of children from exploitation and harm. This page describes our child safety standards, age restrictions, enforcement mechanisms, and how to report concerns.

1. Our Commitment

Jamia has a zero-tolerance policy toward child sexual abuse material (CSAM) and any form of child exploitation or grooming. Any content of this nature discovered on our platform will be:

• Immediately removed.
• Reported to the National Center for Missing and Exploited Children (NCMEC) as required by 18 U.S.C. § 2258A.
• Reported to relevant law enforcement authorities in the UK (Internet Watch Foundation / National Crime Agency), in the EU (the national authority of the member state concerned, and INHOPE hotlines such as jugendschutz.net in Germany and Point de Contact in France), and any other applicable jurisdiction.
• Subject to permanent account termination with no appeal.

2. Age Restrictions

3. Age Verification & Enforcement

General app access (13+):

• Mandatory date-of-birth entry, every account must enter a date of birth during onboarding, using a native date picker, before it can proceed. This step cannot be skipped.
• Account-level block, an account that self-declares an age under 13 is blocked from continuing onboarding and cannot use the app.
• Database-level backstop, in addition to the app-side check, our database rejects any date of birth implying an age under 13 at the moment it is written, independent of which app version or client made the request.

Features restricted to 18+ (nikah requests, booking a sick visit):

• Date-of-birth check, these features check the date of birth on the user's profile and block anyone under 18. A nikah request must also state an age of 18 or over, which our database enforces independently of the app.
• Server-side enforcement, booking a sick visit, and receiving the host's address and contact details, is checked against the user's date of birth on our servers, independent of which app version or client made the request.
• No circumvention, accounts found to have provided false age information will be permanently terminated.

As with virtually every consumer app, none of the above is government-ID age verification — it relies on a user's own honest self-declaration, backed by account-level and database-level enforcement of whatever age they declare.

4. Design Safeguards

Jamia is designed to minimise risk of harm to minors through structural choices:

• No direct messaging, Jamia does not have a direct messaging feature, so users cannot privately message one another through the app.
• Address privacy for sick visits, a sick-visit request shows only an approximate area; the exact address is revealed only to a visitor who has booked a visit and whose date of birth shows they are 18 or older.
• Community verification, users must be verified by a registered masjid to access most features, providing an accountability layer for community members.

5. Reporting Mechanisms

Every user profile and piece of user-generated content in the app includes a built-in report button. Reports are:

• Submitted directly to our platform admin team.
• Reviewed within 48 hours of receipt.
• Acted upon with options including content removal, user warning, or account suspension.
• Escalated to law enforcement where required by law or where risk of harm to a minor is identified.

To report a concern about a child's safety, email support@jamiaapp.com immediately. Urgent concerns involving imminent danger should be reported directly to your local emergency services.

6. Safety Contact

Our designated safety point of contact for child safety concerns:

7. Staff Awareness

All personnel with access to user data or content moderation tools are trained on:

• Recognising indicators of child exploitation and grooming.
• The mandatory reporting obligations under applicable law.
• Proper handling and escalation of reports involving potential harm to minors.

8. Policy Review

This Child Safety Standards policy is reviewed at least annually and updated as necessary to reflect changes in law, platform features, or best practices. The "Last updated" date at the top of this page reflects the most recent review.