These terms apply to all work undertaken by Yellow Box Software Ltd (“Yellow Box”) unless otherwise agreed in writing. Last updated: 1st June 2025
1. Intellectual Property (IP) Ownership
All intellectual property created specifically for your business as part of a paid project — including source code, databases, documentation, and assets — is your property upon full payment of invoices. Yellow Box does not retain ownership of client deliverables. You are free to host, maintain, and modify your system as you wish.
2. Use of Proprietary Components
Yellow Box may, where appropriate, use internal frameworks, utilities, or routines to accelerate delivery. These components remain the intellectual property of Yellow Box. Where such components are embedded into your project, they will be licensed to you on a royalty-free, perpetual, non-exclusive basis for use only within your system.
We may remove or replace any Yellow Box IP whose disclosure would compromise the security of other Yellow Box clients or systems — for example, internal authentication or encryption routines. Equivalent functionality will be maintained wherever reasonably possible to ensure your system continues to operate as expected.
3. Licensing and Resale
You may use, extend, or modify your system for your own business purposes, including across subsidiaries or internal teams. However, resale or sublicensing of the system or its components to third parties may require prior written consent from Yellow Box. Yellow Box agrees not to resell or reuse the project-specific elements of your system for other clients.
4. MVP vs. Production-Ready Systems
Unless explicitly stated otherwise, projects are delivered as Minimum Viable Products (MVPs). An MVP is designed to meet immediate needs and validate functionality but may not be hardened for long-term use, high volumes, or regulatory compliance.
Systems may degrade, become incompatible, or pose security risks over time if not actively maintained. Yellow Box is not responsible for issues arising from future technical debt, platform deprecations, or lack of updates to the MVP after handover. Ongoing support, updates, and scaling plans are strongly recommended and can be quoted separately.
5. Third-Party Platforms
If your system integrates with third-party platforms (e.g. Apple App Store, Google Play, or APIs from services like Stripe, Google Maps, etc.), Yellow Box will work to meet the platform’s requirements at time of submission. However, we are not liable for future changes in those platforms’ policies, technical standards, or enforcement actions, including the removal or suspension of your app, service, or listing.
6. Hosting, Data, and Responsibility
Unless agreed otherwise, Yellow Box systems are hosted via third-party infrastructure providers such as Amazon Web Services (AWS), Google Cloud, or Azure. Hosting charges may be billed separately, or clients may be invited into a shared hosting account.
Yellow Box will take reasonable steps to ensure the security and uptime of your hosted environment. However, hosting environments operate under a shared responsibility model. While Yellow Box manages infrastructure and deployment pipelines, you remain responsible for your data, including its accuracy, retention, and lawful use under applicable regulations (e.g. GDPR).
If Yellow Box provides admin-level access to hosting or data, the client assumes responsibility for any changes made outside of agreed support.
7. Service Level Agreements (SLAs)
Yellow Box offers optional Service Level Agreements for projects requiring defined response times, hosting uptime guarantees, or escalation paths. SLAs are created on a bespoke basis, tailored to the needs of each client and system.
8. Project Transfer and Exit
If you decide to move to another development provider, Yellow Box will supply the full source code, database, and available documentation in a suitable format. We will offer a reasonable level of support (subject to hourly rates) to facilitate a smooth transition.
As outlined above, Yellow Box reserves the right to remove or obfuscate proprietary components where required to protect the integrity and security of other systems.