Version api-terms-1.0

KitabGrid Developer API Terms

Working legal draft. This text is designed for the current KitabGrid API architecture but should be reviewed and completed by a qualified Polish/EU legal professional before public launch, together with the site Privacy Policy and source-specific licences.

1. Scope and agreement

These terms govern access to KitabGrid’s external Developer API. By applying for, claiming or using an API credential, the applicant agrees to these terms and to any source-specific licence or attribution conditions returned with the content.

2. Credentials and domain binding

Access is granted to a specific approved project and host. Server credentials are confidential and must remain backend-only. Browser credentials may be exposed to the browser but are restricted to the approved Origin and remain subject to rate limits and revocation. Credentials may not be sold, shared with unrelated parties, embedded on unapproved domains or published in public repositories.

3. Permitted use

The API may be used only for the use case and scopes approved by KitabGrid. Integrators may present eligible Quran, Hadith, translations and audio on their approved service, subject to the licences attached to those sources. Approval of an API account does not itself grant copyright or reuse rights beyond those source licences.

4. Religious-source integrity and attribution

Content must not be altered, selectively edited, relabelled or presented in a way that falsely attributes a modified statement to the Quran, a Hadith source, a translator, reciter or KitabGrid. Required source, translator, edition, licence and attribution information must be retained wherever the applicable source requires it.

5. Caching and stored copies

Reasonable technical caching is allowed only to the extent permitted by the applicable source licence and the approved integration. Cached data must not be used to bypass rate limits, continue distributing content after the relevant licence/approval is withdrawn, or create an unapproved bulk mirror. KitabGrid may require refresh or deletion of affected cached records after a source correction, rights change or revocation.

6. Rate limits and fair use

Each client has assigned request limits and quotas. Attempts to bypass limits through multiple keys, rotating origins, automated account creation, scraping outside the API, or other evasion are prohibited. KitabGrid may reduce limits or temporarily block abusive traffic to protect availability.

7. Prohibited activity

• unauthorised access, malware, denial-of-service behaviour or security testing without written permission;
• misrepresenting source text, grading, translation status, licensing or KitabGrid endorsement;
• redistributing content where the relevant source licence does not permit that use;
• reselling API access or transferring credentials without written approval;
• using credentials on domains or applications that were not approved.

8. Application data and privacy

KitabGrid processes contact, domain, optional WhatsApp, consent and operational/security records to review and run API access. The site Privacy Policy applies. Optional marketing consent is separate from transactional verification, approval and security messages.

9. Suspension, rotation and termination

KitabGrid may suspend, rotate or revoke credentials where reasonably necessary for security, abuse prevention, licensing, legal compliance, source integrity, maintenance or material breach of these terms. Where practical, the contact email will be used for service notices.

10. Availability and changes

The API is provided on an as-available basis. Endpoints may evolve through versioning, and eligible source records can change as review or licensing status changes. No service-level guarantee is created unless KitabGrid expressly agrees otherwise in writing.

11. Source-specific terms prevail

If an individual translation, recitation, dataset or other source has stricter reuse conditions than these platform terms, the stricter source-specific condition governs that material. If a source becomes ineligible for external reuse, the API may stop returning it without creating a right to continued access.

12. Contact and policy changes

Material changes should be versioned in the Developer API settings and communicated to active clients when appropriate. Legal entity/contact placeholders must be completed in KitabGrid’s main legal documents before launch.