Trusted infrastructure
++ Build faster on comprehensive APIs and scholarly verified Quran data, + without maintaining fragile source pipelines on your own. +
++ Policy version: 1.0 Last updated: 2026-06-30{' '} + Effective date: 2026-06-30 +
+ +Partner and developer guide
++ Connected Apps is the path for developers and app owners who want their + product to appear on Quran.com/apps, + use Quran Foundation APIs, or request selected visibility across Quran + Foundation surfaces. This guide explains what to prepare, how review works, + what users must be able to understand, and what a listing or label does + and does not mean. +
++ Build faster on comprehensive APIs and scholarly verified Quran data, + without maintaining fragile source pipelines on your own. +
++ Connected Apps is more than an API program. It helps users move between + Quran.com and participating apps without starting over. +
++ With OAuth2 and approved User APIs, bookmarks, progress, goals, notes, and + preferences can follow the user where continuity is appropriate. +
++ Qualified apps can be listed on Quran.com/apps within a trusted directory + without treating discovery as paid placement. +
++ Get guidance from Quran Foundation and a mission-aligned network of + builders during access, OAuth, listing, and review decisions. +
++ You want to use Quran Foundation APIs, SDKs, or OAuth2 to build a Quran + reading, listening, study, memorization, reflection, or community product. +
++ You want your independent app to be discoverable through Quran.com/apps + with clear ownership, support, privacy, and platform information. +
++ You want a stronger relationship such as OAuth account continuity, a + reviewed label, or selected editorial visibility. +
+Build
++ Start with Request Access. Use the{' '} + Developer Journey to choose APIs + and plan OAuth clients, redirect URIs, and user-data scopes before + production review. +
+Submit
++ A listing package gives reviewers enough information to understand the + product, verify ownership and support routes, check content and data use, + and decide whether the app is ready for Quran.com/apps. +
+Review
++ Quran Foundation reviews the app in context: usefulness, content handling, + data and consent, product quality, support readiness, commercial model, + AI features, and alignment with user trust. +
+Discover
++ Approved apps may appear in the Connected Apps directory. Labels, + connected-account flows, and featured placements are additional decisions + with their own requirements. +
+| Gate | +Minimum requirement | +Examples of evidence | +If not met | +
|---|---|---|---|
| Content integrity and updates | +Quran Foundation-provided Quranic content must be accessed through approved Quran Foundation endpoints or a written license. External Quranic, scholarly, or supporting content must have verifiable rights, accurate attribution, and any category-specific approval required by Quran Foundation. All content must remain current where corrections, removals, restrictions, or source updates apply. | +API usage, release notes, update cadence, in-app attribution, and license or rights records. | +Unlisted or delisted until corrected. | +
| Security and privacy baseline | +A publicly available privacy notice, a reasonable security posture, no harmful or deceptive data practices, and a security or incident contact. | +Privacy link, security contact, data minimization, and incident-response route. | +Unlisted or delisted. | +
| API and platform compliance | +Respects API terms, usage rules, branding rules, and licensing or attribution terms. | +Accepted partner terms, compliance acknowledgement, and monitored usage. | +Unlisted or delisted. | +
| Maintenance and responsiveness | +A named technical contact who can respond to breaking changes within agreed timelines. | +Support route, issue responsiveness, and maintenance commitment. | +Unlisted or delisted. | +
| Path | +What Quran Foundation reviews | +What the app may say | +What the app must not imply | +
|---|---|---|---|
| Listed | +Complete listing package, working destination links, ownership and support contacts, lawful product, clear purpose, and basic quality fit. | +The app is listed in the Quran.com Connected Apps directory. | +Quran Foundation ownership, guaranteed traffic, homepage exposure, or endorsement of every feature. | +
| Verified Listing | +Eligibility gates, approved content sources, clear attribution, and reliable basic UX. | +The app has completed the checks required for a verified directory listing. | +A broad guarantee that every product area, future release, or partner claim is approved. | +
| Aligned App | +Verified listing checks plus mission alignment and readiness to coordinate on content, API, or deprecation changes. | +The app has completed the checks described for mission-aligned visibility. | +Permanent status, exclusive relationship, or Quran Foundation ownership. | +
| Connected App | +OAuth readiness, OAuth consent copy, redirect URIs, proportionate scopes, privacy information, data security, incident contact, and support route. | +The app can connect to approved Quran Foundation account or user-data features. | +Permission to request unnecessary scopes, bypass consent, or reuse data outside the approved purpose. | +
| Featured App | +User value, quality, timing, audience fit, support readiness, current availability, and suitability for the placement. | +The app is featured in a specific Quran Foundation surface or campaign while that placement is active. | +Permanent status, paid advertising, ranking guarantees, or an ownership relationship. | +
| Tier | +Who it is for | +Incremental requirements | +What it grants | +
|---|---|---|---|
| Verified Listing Tier 1 |
+ Listed apps seeking confirmation of deeper content and operational readiness. | +Listed baseline plus confirmed content provenance: approved Quran Foundation APIs or a written license where Quran Foundation content is used, and verifiable rights for approved external content where it is used; clear attribution; verified update and maintenance arrangements; reliable basic UX. | +Verified label in the directory and eligibility for enhanced discovery opportunities. | +
| Aligned App Tier 2 |
+ Mission-aligned apps that want a closer relationship but are not yet deeply integrated. | +Tier 1 plus demonstrated mission alignment and clear user value; responsible-use standards; participation in change management for material updates, deprecations, and content corrections. | +Directory listing plus eligibility for curated ecosystem roundups, relevant partner showcases, and enhanced discovery opportunities. | +
| Connected App Tier 3 |
+ Apps integrating deeply enough to support account continuity across the ecosystem. | +Tier 2 plus OAuth2 integration and use of user-related APIs for continuity where relevant to the product's user journey. OAuth2 should be implemented where continuity is meaningful, such as carrying bookmarks, progress, notes, goals, or preferences across participating apps; it is not expected where the app has no meaningful account-based experience to connect. | +Eligibility for enhanced placement and Featured consideration, subject to editorial discretion and current ecosystem priorities. | +
| Featured App Tier 4, time-boxed |
+ Best-in-class, high-impact apps advancing ecosystem goals. | +Tier 3 plus demonstrated user value, active collaboration cadence, current availability, and support readiness. | +Time-boxed Featured placement, at Quran Foundation's editorial discretion, re-evaluated each cycle. | +
| Integration | +Recommended flow | +
|---|---|
| User APIs Signed-in, per-user data |
+ Authorization Code with PKCE and OpenID Connect; backend token exchange for confidential clients. | +
| Content APIs Content only, no per-user data |
+ Backend Client Credentials, or the official SDK. | +
| Field | +Required | +Format or limit | +Notes | +
|---|---|---|---|
| App name | +Yes | +40 characters maximum | +Exactly as it should appear publicly. Shorter names work better because the card title is one line. | +
| Short descriptor / tagline | +Yes | +60 characters maximum | +A few words; descriptive, not promotional. The Quran.com/apps card displays this on one line. | +
| Short description | +Yes | +1 to 2 sentences, 160 characters maximum | +Explain what the app does and who it helps. Avoid hype, unverifiable claims, and repeated tagline text. | +
| Icon / logo | +Yes | +Square asset, minimum 512 x 512 px, PNG, SVG, or WebP | +The card renders icons at approximately 52 x 52 px on desktop and 48 x 48 px on mobile. Use safe contrast, clean edges, and confirmed source rights. | +
| Primary category | +Yes | +One approved category | +Drives filtering and discovery. | +
| Secondary tags | +Optional | +Approved taxonomy terms | +Used for filtering where helpful. | +
| CTA links | +Yes | +Valid web, iOS, and/or Android destinations | +Only working, official links should be submitted. | +
| Support contact and public support route | +Yes | +Publicly accessible support email or URL | +Operational accountability. | +
| Privacy policy link | +Yes | +Public URL | +Required for review readiness. | +
| Attribution / content-source declaration | +Yes | +Required where Quranic, scholarly, or supporting content is used | +See Attribution And Content Sources. | +
| Technical contact / update owner | +Yes | +Named operational contact, supplied privately where not suitable for public display | +For change management and breaking-change response. | +
| Badge / tier | +If displayed | +Verified Listing, Aligned App, Connected App, or Featured App | +Set by review, not self-assigned. | +
+ Does the product solve a real user need and support Quran reading, + listening, understanding, memorization, reflection, or continuity? +
++ Are Quranic text, translations, tafsir, recitations, and derived content + sourced, represented, kept current, and attributed accurately? +
++ Are requested scopes proportionate, explained clearly, secured + appropriately, and limited to the product function? +
++ Does the product work reliably, avoid avoidable confusion, and provide a + support route for users who need help? +
++ Are charges, ads, donations, sponsorships, or affiliate models + transparent, proportionate, and compatible with content obligations? +
++ Can the app owner keep listing details current, respond to issues, and + cooperate with reasonable review or corrective action? +
++ New owner, major repositioning, discontinued support, broken destination + links, or a change in the primary user experience. +
++ New OAuth scopes, expanded user-data use, changed consent copy, new + processors, or security and incident-response changes. +
++ New Quranic sources, generated religious content, AI explanations, model + or provider changes where user data is processed, attribution changes, or + mixing reviewed sources with unreviewed output. +
++ New ads, subscriptions, purchases, donations, sponsorships, affiliate + links, or paid access around Quranic content or user features. +
++ New claims, screenshots, categories, platform links, app descriptions, or + relationship statements shown to Quran.com users. +
++ Quran Foundation may update, pause, or remove directory visibility, + labels, connected access, or featured placement when requirements are no + longer met. +
+| Question | +Connected Apps directory | +Quran.com homepage | +
|---|---|---|
| Purpose | +Help users browse and evaluate relevant Quran-related apps. | +Introduce a broad audience to a selected, high-confidence experience. | +
| Default expectation | +Eligible reviewed apps can be listed with categories and platform links. | +Placement is selective, time-sensitive, and not guaranteed by listing approval. | +
| Data shape | +Directory cards can include title, tagline, description, icon, categories, relationship type, and platform links. | +Homepage cards should be fewer, concise, current, and appropriate for broad Quran.com traffic. | +
| Change control | +Listing details should stay current and may be paused when required. | +Placement can change based on review, quality, editorial priorities, timing, or product status. | +
New integration
+Get credentials, redirect URI review, and scope guidance before implementation.
+ Open Request Access +Choosing APIs
+Choose Content APIs, Search APIs, User APIs, OAuth2, or SDK docs by app shape.
+ Open Developer Journey +Signed-in apps
+Build OAuth-backed bookmarks, notes, reading sessions, goals, and preferences.
+ Open User APIs Quickstart ++ Potentially. Monetization is evaluated in context. The product should + provide genuine user value, describe charges honestly, respect content + obligations, and avoid using Quranic material as a superficial marketing + vehicle. Commercial content use may require separate written permission. +
++ Possible models should be transparent, proportionate, and respectful of the + user experience. Intrusive, deceptive, or contextually inappropriate + promotion can affect eligibility or visibility. +
++ No. OAuth is most important where Quran Foundation account continuity, + personal user data, or signed-in user actions are central. Where OAuth is + used, the app should request only the permissions it truly needs and explain + the benefit before consent. +
++ No. A listing helps users discover an independent product. It does not mean + Quran Foundation owns the app, provides its support, or endorses every + current and future feature. A badge or label applies only to the checks + described for that badge or label. +
++ App partners build user-facing experiences and are reviewed for product, + data, support, and ecosystem fit. Content partners can have additional + source, rights, attribution, licensing, and usage considerations. The review + tracks should be distinct when those obligations differ. +
+