Master Services Agreement

The contract under which the Bank licenses Ijarah OS. Each pilot or live period is a SOW under this MSA. Fees buy access and services. They do not buy the platform.

• Non-exclusive, non-transferable right to a private bank environment.
• Customer journey under the Bank’s brand.
• Policy Studio configuration. Configuration is Bank content, not Bank software.
• Ijarah OS may license other banks. Data and packs stay isolated.

Source code, orchestration logic, source-ranking weights, and helper engines stay with Ijarah OS. Delivery of source requires a separate escrow agreement. Phase 1 and Phase 2 do not include on-prem source.

For 36 months from the later of last disclosure or termination, the Bank will not use Confidential Information obtained in demos, scoping, or the pilot to design, build, or commission a competing multi-party origination orchestration system for Islamic home finance.

This does not stop the Bank running its own credit policy, Shariah board, or core banking. It stops cloning the rails from what we showed.

• The customer
• Credit decision
• Shariah control
• Final say on every file

Nothing funds without the Bank’s last confirm. That is a product rule and a contract rule.

• Bank is controller of personal data where applicable (UAE PDPL).
• Ijarah OS processes to run the service. DPA as schedule.
• On exit: export of policy content and case data for 30 days in standard formats. Then access ends.

Workflow schemas, API shapes, package-drop payloads, Policy Studio internals, and commercial terms are Confidential Information. Stamp: Patent Pending once the provisional is filed.

Caps, exclusions, and governing law to be completed by counsel. Default working position: UAE law, DIFC or onshore as agreed, liability capped at fees paid in the prior 12 months, no indirect loss.

MSA → SOW → brand pack. If they clash, the SOW wins for that period only.