Terms and Conditions

Last updated: 1 June 2026

These Terms and Conditions constitute the standard contractual framework governing the provision of services by MIJIRA LTD to its clients. MIJIRA LTD is a company registered in the United Kingdom with its registered office at 2/3, 6 Banner Drive, Glasgow, United Kingdom, G13 2HP. Contact: general@mijira.site, +447446968169, mijira.site.

These Terms and Conditions apply to all service agreements unless expressly varied in a signed statement of work, order form, or master services agreement. By executing a proposal, purchase order, or statement of work referencing these Terms and Conditions, or by accessing paid services, the Client agrees to be bound. Website use is also governed by our Terms of Service. Personal data processing is described in our Privacy Policy.

MIJIRA LTD operates in publishing industries including telecommunications, computing infrastructure, data processing, web hosting, media streaming, social networks, motion picture and video publishing, newspapers and periodicals, radio and television broadcasting, satellite telecommunications, and sound recording. Services are described on Services and may be illustrated in our Portfolio.

1. Definitions and Interpretation

In these Terms and Conditions, unless context requires otherwise:

• Agreement means these Terms and Conditions together with the applicable statement of work, order form, service schedule, and data processing agreement.
• Client means the entity entering into the Agreement with MIJIRA LTD.
• Client Content means data, media, text, software, metadata, and materials supplied by or on behalf of the Client for processing, hosting, publication, or distribution.
• Confidential Information means non-public information disclosed by either party, including technical specifications, pricing, security reports, and unreleased media assets.
• Deliverables means tangible or intangible outputs expressly identified in the statement of work.
• Documentation means operational guides, API references, and runbooks provided for service use.
• Fees means charges payable for services as set out in the statement of work or pricing schedule.
• Force Majeure Event means events beyond reasonable control including natural disasters, war, terrorism, widespread network failures not attributable to the affected party's negligence, governmental actions, and pandemics.
• Intellectual Property Rights means patents, copyrights, moral rights, trade marks, database rights, design rights, trade secrets, and similar protections worldwide.
• MIJIRA Platform means proprietary and licensed software, hardware, and network resources operated by MIJIRA LTD to deliver services.
• Services means professional, managed, hosting, streaming, broadcast support, data processing, and related services described in the Agreement.
• Service Levels means measurable performance commitments where expressly attached.
• Statement of Work means a document specifying scope, deliverables, timelines, Fees, and service-specific terms.
• Third-Party Services means external platforms or connectivity not owned by MIJIRA LTD but integrated at Client request.

Headings are for convenience only. Words importing the singular include the plural. References to statutes include amendments and re-enactments. A person includes natural and legal persons. Obligations on a party bind its successors and permitted assigns.

2. Agreement Formation and Order of Precedence

An Agreement is formed when MIJIRA LTD accepts a Client purchase order or signs a statement of work, or when MIJIRA LTD commences provision of paid services with Client's knowledge and consent. Verbal commitments require written confirmation to bind MIJIRA LTD beyond preliminary discussions initiated through Contact.

In case of conflict, the following order of precedence applies unless the parties expressly agree otherwise in writing: (1) executed master services agreement; (2) data processing agreement for privacy matters; (3) statement of work; (4) service level schedule; (5) these Terms and Conditions; (6) Documentation. Marketing materials on mijira.site are non-contractual illustrations unless incorporated by reference.

3. Scope of Services

MIJIRA LTD provides services across publishing and media infrastructure domains. Specific scope, exclusions, assumptions, and dependencies are defined in each statement of work. Services may include:

3.1 Telecommunications and Network Infrastructure

Design, provisioning, and management of connectivity, peering arrangements, satellite uplink coordination, and broadcast contribution paths. Client is responsible for obtaining spectrum licences, Ofcom approvals, and third-party circuit contracts unless expressly included.

3.2 Computing and Data Processing

Virtualised compute, container orchestration, batch and stream processing pipelines, encoding farms, and analytics clusters. Client specifies workload characteristics including peak concurrency, codec requirements, and data residency preferences.

3.3 Web Hosting and Content Delivery

Managed hosting for publishing platforms, editorial tools, asset libraries, and static or dynamic web properties with optional CDN integration, DDoS mitigation, and TLS certificate management.

3.4 Media Streaming

Live and on-demand streaming stacks including packaging, DRM integration interfaces, adaptive bitrate delivery, origin shielding, and audience measurement hooks. Client supplies encoding profiles and rights management policies.

3.5 Social Network and Community Delivery

APIs, moderation tooling integration points, notification services, and scalable storage for user-generated content subject to acceptable use policies defined by Client.

3.6 Motion Picture and Video Publishing

Workflow support for screener distribution, review portals, transcoding ladders, subtitle handling, and archival storage with access controls suitable for pre-release materials.

3.7 Newspaper, Periodical, and Book Publishing

Digital edition hosting, subscription fulfilment integrations, e-reader format generation support, and print workflow data exchange where specified.

3.8 Radio and Television Broadcasting

Playout adjacency systems, catch-up TV infrastructure, electronic programme guide data ingestion, and monitoring for transmission chain components under Client operational control unless managed services are ordered.

3.9 Sound Recording

Audio asset management, loudness normalisation pipelines, metadata enrichment for ISRC and rights administration exports, and high-availability delivery for music catalogues.

Unless stated otherwise, professional services are delivered on a time-and-materials or fixed-fee basis with milestones. Managed services renew per the statement of work term.

4. Client Obligations

Client shall provide timely access to personnel, facilities, Client Content, approvals, and third-party vendor cooperation necessary for delivery. Client warrants that it has all rights, licences, and consents required for Client Content and intended distribution, including performance, mechanical, and synchronisation rights for musical works, performer consents, defamation review for journalistic material, and age-appropriate safeguards for youth-directed programming.

Client shall not use Services to transmit unlawful content, infringe intellectual property, distribute malware, conduct unauthorised surveillance, circumvent technical protection measures except as permitted by law, or exceed licensed capacity. Client maintains accurate administrative contact details for incident notification.

Client is responsible for end-user terms, privacy notices, and regulatory filings associated with public-facing services operated on MIJIRA infrastructure unless MIJIRA expressly undertakes such responsibilities in writing.

5. MIJIRA LTD Obligations

MIJIRA LTD shall perform Services with reasonable skill and care consistent with industry standards for publishing infrastructure providers. We assign suitably qualified personnel, maintain security controls described in the Agreement, and use commercially reasonable efforts to meet Service Levels where attached.

We provide incident communication channels and status updates during material outages affecting managed components within our control. We do not guarantee uninterrupted service where factors outside our control affect upstream carriers, client misconfiguration, or force majeure events.

6. Fees, Invoicing, and Payment

Client shall pay Fees in the currency and schedule specified in the statement of work. Unless otherwise stated, invoices are due within thirty days of issue. Late payments accrue interest at four percent per annum above the Bank of England base rate pursuant to the Late Payment of Commercial Debts (Interest) Act 1998.

Recurring Fees adjust annually by the greater of three percent or the UK Consumer Prices Index increase unless fixed pricing is agreed for the contract term. Usage-based charges reflect metered bandwidth, storage, compute hours, concurrent stream peaks, or other metrics defined in the pricing schedule. Client may dispute invoice line items in good faith within fourteen days of receipt; undisputed portions remain payable.

MIJIRA LTD may suspend Services for non-payment after fourteen days' written notice if amounts overdue exceed five hundred pounds sterling or two consecutive billing periods, without prejudice to other remedies.

7. Term, Suspension, and Termination

The Agreement commences on the effective date in the statement of work and continues for the initial term specified, renewing automatically for successive twelve-month periods unless either party gives ninety days' written notice of non-renewal before expiry.

Either party may terminate for material breach not remedied within thirty days of written notice. MIJIRA LTD may terminate immediately if Client insolvency events occur, Client Content creates unacceptable legal exposure after notice, or required third-party licences are revoked through Client fault.

Upon termination, Client shall pay accrued Fees. MIJIRA LTD shall provide data export assistance for thirty days subject to Fee payment and reasonable professional services rates for complex migrations. Thereafter Client Content may be deleted per retention policy unless legal hold applies.

8. Intellectual Property

MIJIRA LTD retains all Intellectual Property Rights in the MIJIRA Platform, Documentation, methodologies, and pre-existing materials. Client receives a non-exclusive, non-transferable licence to use the MIJIRA Platform during the term for internal business purposes in connection with Services.

Client retains all Intellectual Property Rights in Client Content. Client grants MIJIRA LTD a worldwide licence to host, reproduce, transmit, transcode, cache, and display Client Content solely to provide Services and prevent security threats.

Deliverables specifically commissioned as bespoke developments are governed by the statement of work. Unless Fees include full assignment, bespoke code remains MIJIRA LTD property with Client receiving a perpetual licence for internal use. Open-source components are licensed under their respective terms listed in bill of materials documentation.

9. Confidentiality

Each party shall protect the other's Confidential Information using at least the same degree of care as for its own confidential materials, and no less than reasonable care. Confidential Information may be disclosed to employees, contractors, and advisers with need to know under binding confidentiality obligations. Disclosure is permitted where required by law or court order with prompt notice where legally allowed.

Confidentiality obligations survive termination for five years, except trade secrets and unreleased media assets which remain protected for as long as they retain confidential status.

10. Data Protection

Parties shall comply with UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations, and applicable sector guidance. Roles are defined in the data processing agreement: typically Client is controller for end-user and editorial data; MIJIRA LTD is processor for hosting and processing activities.

MIJIRA LTD implements security measures in Annex descriptions where provided, assists with data subject requests, notifies Client of breaches without undue delay, and maintains sub-processor transparency. International transfers use approved mechanisms. Details align with our Privacy Policy and Cookie Policy where relevant to Client-facing sites we operate under instruction.

11. Warranties and Disclaimers

Each party warrants it has authority to enter the Agreement. MIJIRA LTD warrants Services will be performed with reasonable skill and care. Except as expressly stated, Services and the MIJIRA Platform are provided without implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

MIJIRA LTD does not warrant that Services will meet Client's regulatory approvals without Client fulfilling its compliance duties, that third-party networks will be error-free, or that every security threat can be prevented.

12. Limitation of Liability

Neither party excludes liability for death or personal injury caused by negligence, fraud, or any liability that cannot be limited under applicable law. Subject to the foregoing, neither party shall be liable for indirect, consequential, special, or punitive loss including loss of profits, revenue, audience, advertising income, goodwill, or anticipated savings.

Except for Client payment obligations, confidentiality breaches, indemnities, and liabilities arising from wilful misconduct, each party's aggregate liability arising in any twelve-month period is capped at the greater of one hundred thousand pounds sterling or one hundred twenty-five percent of Fees paid in that period.

Liability caps do not apply where limited liability would contravene mandatory telecommunications or consumer protection rules applicable to specific service components explicitly designated as regulated public electronic communications in the statement of work.

13. Indemnity

Client shall indemnify MIJIRA LTD against claims, damages, fines, and reasonable legal costs arising from Client Content, Client's breach of law or the Agreement, or allegations that Client materials infringe third-party rights, except to the extent caused by MIJIRA LTD's deliberate misconduct.

MIJIRA LTD shall indemnify Client against claims that the MIJIRA Platform, when used per Documentation, infringes UK intellectual property rights, provided Client notifies promptly, allows control of defence, and avoids prejudicial admissions. If infringement is established or likely, MIJIRA LTD may procure alternative rights, modify the platform, or terminate affected Services with pro-rata Fee refund.

14. Service Levels and Credits

Where a Service Level Schedule is attached, availability or performance commitments are measured against defined exclusions including scheduled maintenance notified forty-eight hours in advance, emergency maintenance, Client-induced outages, Force Majeure Events, and third-party carrier faults outside MIJIRA LTD's reasonable control.

Service credits, if any, are Client's sole monetary remedy for failure to meet stated Service Levels and are applied against future invoices upon validated claim submission within thirty days of the incident month. Credits do not exceed twenty-five percent of monthly recurring Fees for the affected service component.

15. Change Control

Material changes to scope, timelines, or Fees require a written change order signed by authorised representatives. MIJIRA LTD may implement non-material updates to the MIJIRA Platform that do not materially degrade contracted functionality. Material platform changes affecting APIs or security models will be notified with reasonable lead time and migration guidance.

16. Acceptable Use and Content Standards

Client shall ensure Client Content and use of Services comply with applicable laws including copyright, contempt of court, hate speech legislation where applicable, Ofcom codes for broadcast clients, and export controls for cryptographic features. Prohibited uses include distribution of non-consensual intimate imagery, unlawful harassment campaigns, and operation of services targeting sanctioned jurisdictions without compliance review.

MIJIRA LTD may remove or disable access to clearly unlawful material upon notice or court order and may suspend Services where continued operation poses imminent harm, with notice to Client where practicable.

17. Audit and Compliance

Upon reasonable notice and no more than once annually unless a data breach or regulatory inquiry necessitates otherwise, Client may audit MIJIRA LTD's compliance with data processing and security obligations through a mutually agreed third-party auditor bound by confidentiality. Client bears audit costs unless material non-compliance is identified.

MIJIRA LTD may provide SOC-style reports or certification summaries where available in lieu of onsite audits for standard hosted services.

18. Insurance

MIJIRA LTD maintains professional indemnity and cyber liability insurance at levels appropriate to contract value and service risk profile. Certificates are available on request. Insurance coverage is not a limit on liability except where expressly stated in a master services agreement.

19. Non-Solicitation

During the term and for twelve months thereafter, neither party shall solicit for employment key personnel directly involved in the Services who have specialised knowledge of the other party's confidential operations, without prior written consent. General recruitment advertising not targeted at specific individuals is excluded.

20. Publicity

MIJIRA LTD may identify Client as a customer and use non-confidential project descriptors in marketing materials and our Portfolio unless Client opts out in writing. Client shall not imply endorsement by MIJIRA LTD beyond factual service descriptions without approval.

21. Force Majeure

Neither party is liable for delay or failure to perform obligations, except payment, caused by a Force Majeure Event. The affected party shall notify the other promptly and use reasonable efforts to mitigate. If a Force Majeure Event continues beyond sixty days, either party may terminate affected Services without penalty except payment for services rendered before termination.

22. Assignment and Subcontracting

Client may not assign the Agreement without MIJIRA LTD's prior written consent except to a successor in a corporate reorganisation. MIJIRA LTD may subcontract technical operations provided subcontractors meet equivalent obligations. MIJIRA LTD remains responsible for subcontractor performance of core Services.

23. Notices

Notices shall be in writing and delivered by email to designated addresses with confirmation, or by recorded delivery post to registered offices. Notices to MIJIRA LTD: general@mijira.site and 2/3, 6 Banner Drive, Glasgow, G13 2HP. Notices are deemed received on the next business day for email sent before 5pm UK time, or two business days after posting.

24. Dispute Resolution and Governing Law

Parties shall attempt good faith resolution through operational escalation and then executive negotiation within twenty business days of a dispute notice. Unresolved disputes may proceed to mediation in Glasgow under CEDR rules before litigation, unless urgent injunctive relief is required.

The Agreement is governed by the laws of England and Wales. Courts of England and Wales have exclusive jurisdiction, without prejudice to rights to seek enforcement in other jurisdictions where assets are located.

25. General Provisions

Failure to enforce a provision is not a waiver. Invalid provisions are severed with remainder continuing in force. The Agreement constitutes the entire understanding regarding Services and supersedes prior discussions. Amendments must be in writing signed by authorised representatives. No third-party rights arise under the Contracts (Rights of Third Parties) Act 1999 except permitted assigns.

26. Service Schedules and Special Terms

The following subsections describe standard special terms that apply when corresponding services are ordered. Conflicting statement of work terms prevail.

26.1 Telecommunications Infrastructure

Circuit diversity, latency targets, and maintenance windows are specified per point of presence. Client provides accurate technical contacts for carrier coordination. MIJIRA LTD documents routing policies and change management procedures. Emergency maintenance may occur without forty-eight hour notice where network integrity is threatened.

Operational reviews for telecommunications infrastructure services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting telecommunications infrastructure workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for telecommunications infrastructure components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.2 Satellite Telecommunications

Uplink booking schedules, redundancy paths, and weather-related attenuation protocols are agreed in advance. Client holds necessary earth station licences. MIJIRA LTD supplies monitoring for signal quality and automated failover where hardware supports it.

Operational reviews for satellite telecommunications services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting satellite telecommunications workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for satellite telecommunications components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.3 Computing Infrastructure

Virtual machine specifications, Kubernetes cluster quotas, and snapshot retention follow the service schedule. Client workloads must not negatively impact multi-tenant neighbours; noisy neighbour mitigation may include throttling with notice.

Operational reviews for computing infrastructure services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting computing infrastructure workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for computing infrastructure components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.4 Data Processing Pipelines

Batch SLAs define maximum queue latency; stream processing SLAs define end-to-end processing windows. Client supplies schema documentation and test datasets. Data quality issues originating from Client sources are excluded from SLA credit calculations.

Operational reviews for data processing pipelines services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting data processing pipelines workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for data processing pipelines components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.5 Web Hosting

Shared hosting environments prohibit resource-intensive crypto mining and bulk unsolicited email. Dedicated instances allow custom modules subject to security review. TLS configurations follow industry best practices and are updated for deprecated cipher removal.

Operational reviews for web hosting services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting web hosting workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for web hosting components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.6 Media Streaming

Concurrent stream limits, geographic restrictions, and DRM vendor integrations are Client-configured. MIJIRA LTD measures origin-to-edge performance. Client is responsible for music and performance licences for streamed content.

Operational reviews for media streaming services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting media streaming workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for media streaming components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.7 Social Network Delivery

Moderation queues, rate limits, and abuse reporting APIs are provisioned per capacity plan. MIJIRA LTD does not assume editorial responsibility for user posts. Law enforcement requests for subscriber data are forwarded to Client unless MIJIRA LTD is legally compelled as processor.

Operational reviews for social network delivery services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting social network delivery workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for social network delivery components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.8 Motion Picture and Video Publishing

Screener links use expiring tokens and forensic watermarking where ordered. Client defines authorised viewer lists. Download suppression and geo-fencing are configurable. MIJIRA LTD logs access events for audit.

Operational reviews for motion picture and video publishing services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting motion picture and video publishing workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for motion picture and video publishing components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.9 Newspaper and Periodical Publishing

Edition cutover windows and subscription sync frequency are documented. Payment card data must not be stored on MIJIRA systems without PCI-compliant configuration. Client retains publisher liability for editorial content.

Operational reviews for newspaper and periodical publishing services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting newspaper and periodical publishing workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for newspaper and periodical publishing components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.10 Radio Broadcasting

Audio streaming bit rates, ad insertion cue points, and RDS metadata feeds require Client validation. Backup playout paths are Client-operated unless explicitly managed.

Operational reviews for radio broadcasting services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting radio broadcasting workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for radio broadcasting components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.11 Television Broadcasting

Catch-up retention periods, blackout rules, and regionalisation logic are Client-defined. MIJIRA LTD supports time-shifted delivery infrastructure but does not schedule programming.

Operational reviews for television broadcasting services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting television broadcasting workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for television broadcasting components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

26.12 Sound Recording

Catalogue ingestion formats, loudness standards such as EBU R128, and hi-resolution delivery options are specified. Royalty reporting exports are provided in agreed formats; calculation remains Client responsibility.

Operational reviews for sound recording services occur at least quarterly for enterprise clients, covering capacity forecasts, incident trends, and roadmap alignment. Change requests impacting sound recording workflows follow the change control procedure in Section 15. Client personnel participating in reviews must hold appropriate security clearance where Client Content includes embargoed releases.

Security testing for sound recording components includes annual vulnerability scanning and penetration testing scoped to MIJIRA-managed assets. Client may commission additional testing with fourteen days notice, bearing costs unless critical vulnerabilities attributable to MIJIRA LTD are discovered. Remediation timelines for critical findings target seventy-two hours for internet-facing streaming auth endpoints and ten business days for medium severity issues.

27. Operations, Maintenance, and Support

Support tiers, response targets, and communication channels are defined in the statement of work. Standard support hours are 09:00 to 18:00 UK time Monday to Friday excluding public holidays, with optional twenty-four-seven coverage for critical streaming or broadcast chains.

Client shall submit tickets with severity classification guidelines. Severity 1 incidents affecting production streaming or broadcast delivery receive continuous effort to restore service. Severity 2 incidents affecting non-critical functions receive response within four business hours. Severity 3 requests for information or minor defects receive response within two business days.

Planned maintenance windows for infrastructure upgrades are communicated with at least forty-eight hours notice. Emergency patches for zero-day vulnerabilities may be applied with shortened notice where delay would materially increase risk.

28. Security Operations

MIJIRA LTD maintains access control policies, logging, intrusion detection, and backup strategies proportionate to service classification. Client shall rotate API keys periodically, enforce multi-factor authentication for administrative interfaces, and promptly apply configuration changes recommended after security advisories.

Client must report suspected compromises immediately. MIJIRA LTD coordinates containment, forensic preservation, and regulatory notifications as defined in the data processing agreement. Post-incident reports summarise root cause, impact, and remedial actions within twenty business days for Severity 1 security incidents.

29. Migration and Exit Assistance

Upon Client request at termination, MIJIRA LTD provides reasonable export assistance including database dumps, media asset manifests, DNS cutover planning, and streaming origin configuration documentation. Complex migrations are billed at standard professional services rates. MIJIRA LTD has no obligation to assist migration to a direct competitor if information shared would breach confidentiality owed to other clients, but objective technical documentation will be provided.

30. Regulatory Compliance Cooperation

Client retains primary responsibility for regulatory compliance in its publishing activities. MIJIRA LTD cooperates with reasonable compliance evidence requests including configuration snapshots, log extracts, and witness statements for matters within our service scope. Fees for extensive regulatory production may be charged at agreed rates.

Schedule Supplement: Business continuity

MIJIRA LTD maintains business continuity and disaster recovery plans reviewed annually. Recovery time objectives and recovery point objectives for managed services are stated in service schedules. Client shall maintain independent backups for business-critical archives where contract specifies shared responsibility.

Schedule Supplement: Capacity planning

Clients with variable audiences such as live sports or election night coverage shall provide forecast peaks at least fourteen days in advance where possible. Burst capacity may be subject to availability and surge pricing defined in the statement of work.

Schedule Supplement: Open source compliance

The MIJIRA Platform incorporates open-source software. Attribution notices and licence texts are available on request. Client modifications to open-source components integrated in bespoke work remain subject to licence copyleft obligations where applicable.

Schedule Supplement: Ethical advertising

Clients monetising streams or publications through advertising shall ensure ad content complies with UK advertising standards and sector codes. MIJIRA LTD ad insertion infrastructure does not review creative content unless a managed compliance add-on is contracted.

Schedule Supplement: Accessibility obligations

Client is responsible for accessibility of public-facing players and websites to the extent required by the Equality Act 2010 and applicable regulations. MIJIRA LTD provides configurable player skins and caption delivery support.

Schedule Supplement: Export controls

Cryptographic services and certain satellite technologies may be subject to export control laws. Client represents it will not permit use in embargoed destinations contrary to UK export regulations.

Schedule Supplement: Taxes

Fees exclude VAT and applicable withholding taxes. Client shall pay VAT where charged and cooperate on tax documentation for cross-border services.

Schedule Supplement: Set-off

Each party shall pay amounts due in full without set-off or counterclaim except for undisputed amounts finally determined owed by the other party.

Schedule Supplement: Survival

Provisions relating to confidentiality, intellectual property, payment of accrued Fees, limitation of liability, indemnity, dispute resolution, and data return survive termination.

Schedule Supplement: Language

The Agreement is drafted in English. Translations provided for convenience do not override the English version in case of discrepancy.

31. Contact Information

For contractual notices, service management, or commercial enquiries, contact MIJIRA LTD at 2/3, 6 Banner Drive, Glasgow, G13 2HP, United Kingdom, general@mijira.site, or +447446968169. Visit About for corporate background or Contact to initiate new projects.

32. Appendix A — Service Level Framework

Where a Service Level Schedule is incorporated, the following framework applies unless the statement of work specifies alternative metrics. Availability is measured monthly as total minutes minus excluded downtime divided by total minutes in the calendar month. Excluded downtime includes scheduled maintenance performed within agreed windows, emergency maintenance for critical vulnerabilities, outages caused by Client configuration errors or third-party networks outside MIJIRA LTD control, and Force Majeure Events.

For managed streaming origin services, a standard enterprise tier targets 99.9 percent availability of the origin API endpoint monitored from three UK locations. CDN edge availability is measured separately through provider reports. For managed database clusters supporting publishing CMS platforms, a standard tier targets 99.95 percent availability with automatic failover within fifteen minutes for single-zone failures.

Service credits are calculated as a percentage of monthly recurring Fees for the affected component: 5 percent for availability between 99.0 and 99.9 percent where 99.9 is target; 10 percent between 98.0 and 99.0; 20 percent below 98.0. Credits require ticket reference, timestamps, and good faith cooperation on root cause analysis. Maximum aggregate credits per month are capped at twenty-five percent of monthly recurring Fees unless gross negligence is established.

33. Appendix B — Data Processing Annex Summary

When MIJIRA LTD processes personal data on behalf of Client, the data processing agreement includes: subject matter and duration mirroring the Agreement; nature and purpose limited to providing Services; types of personal data as described in Client content and user interactions; categories of data subjects including end users, subscribers, contributors, and Client personnel; obligations and rights of Client as controller; documented instructions through statements of work and support tickets within scope; confidentiality of personnel; security measures aligned with Annex technical standards; sub-processor notification with objection rights; assistance with data subject requests, DPIAs, and breach notifications; deletion or return upon termination; audit rights as per Section 17; and transfer mechanisms for international sub-processors.

Client shall not instruct processing that violates applicable law. MIJIRA LTD may suspend processing instructions that create manifest legal risk after written notice. Standard contractual clauses adopted by UK authorities are incorporated by reference where transfers occur.

34. Appendix C — Streaming Technical Requirements

Clients utilising media streaming Services shall provide encoding specifications including codec profiles, GOP structures, DRM systems supported, subtitle formats, and ad insertion signalling if applicable. MIJIRA LTD supplies recommended bitrate ladders for HLS and DASH packaging. Client is responsible for music performance rights, mechanical royalties, and geo-restrictions aligned with licensing agreements.

Concurrent stream peaks declared in statements of work establish baseline capacity. Exceeding peaks by more than twenty percent for sustained periods may incur surge Fees or require capacity upgrade change orders. Origin shield configurations reduce load on Client encoders; Client maintains encoder redundancy for live events unless managed encoder farms are contracted.

Low-latency modes for interactive broadcasts may trade off CDN caching efficiency; latency targets are documented separately and exclude last-mile consumer networks. Disaster recovery for streaming includes secondary origin paths and DNS failover playbooks tested annually.

35. Appendix D — Broadcast and Regulatory Cooperation

Clients operating radio or television broadcast chains using MIJIRA infrastructure retain Ofcom licensing obligations, content standards compliance, and accessibility requirements for programming. MIJIRA LTD provides logging and monitoring hooks but does not assume editorial control. Emergency alert system integrations, where configured, require Client testing and governmental authorisation.

Catch-up and on-demand windows must respect rights agreements uploaded by Client. Geo-blocking and device restriction policies are Client-configured. MIJIRA LTD assists with evidence packs for regulatory inquiries covering infrastructure uptime and transmission logs within Service scope.

36. Appendix E — Security Standards

MIJIRA LTD implements baseline controls including network firewalls, segmentation between tenant environments where multi-tenant architectures are used, encryption of data in transit via TLS 1.2 or higher, encryption at rest for designated storage classes, multi-factor authentication for administrative access, vulnerability scanning, patch management, and centralised logging with retention as per service schedules.

Clients must rotate API credentials quarterly, restrict administrative access by IP allow lists where feasible, and promptly apply configuration changes after security advisories tagged critical. Penetration testing by Client third parties requires fourteen days notice and scope approval to prevent service disruption.

Security incidents are classified P1 to P4. P1 indicates active exploitation or major data breach; P4 indicates informational findings. Response targets for P1 include containment initiation within one hour for managed security operations centre clients.

37. Appendix F — Professional Services

Professional services such as workflow design, custom integration development, migration planning, and training are scoped in statements of work with deliverables, milestones, and acceptance criteria. Acceptance is deemed given if Client does not reject with specific deficiency list within ten business days of deliverable submission. Rejection triggers remediation plan within five business days.

On-site work in Glasgow or client premises follows agreed health and safety rules. Travel and subsistence are reimbursable per statement of work or standard schedule. Knowledge transfer sessions are limited to eight hours per major deliverable unless extended.

38. Appendix G — Hardware and Colocation

Where MIJIRA LTD supplies or leases hardware, risk of loss transfers to Client upon delivery signature unless managed maintenance is included. Firmware updates are applied during maintenance windows. Colocation services include power and cooling within specified draw limits; exceeding limits requires facility upgrade fees.

Remote hands requests are billed per incident unless bundled in managed colocation tiers. Client equipment labelling and asset registers must remain current for insurance claims.

39. Appendix H — Licensing and Open Source

Client receives licences described in Section 8. Third-party software embedded in Deliverables is listed in bills of materials with licence types including MIT, Apache, and GPL family licences where applicable. Client responsibilities for copyleft compliance are highlighted for GPL components touching Client modifications.

MIJIRA LTD indemnity for platform infringement does not cover combinations with Client Content or third-party plugins not supplied by MIJIRA LTD.

40. Appendix I — Escalation Matrix

Operational issues escalate from support tier one to tier two engineering, then to service owner, then to executive sponsor for enterprise accounts. Client-side escalation contacts must be designated in onboarding documents. Executive reviews occur quarterly for accounts exceeding agreed revenue thresholds or carrying critical broadcast dependencies.

41. Appendix J — Change Management Records

Material infrastructure changes are logged with ticket identifiers, risk classification, rollback plans, and approval signatures. Client notification for changes affecting APIs occurs at least thirty days in advance except security emergencies. Change advisory board meetings for enterprise clients review upcoming maintenance monthly.

42.1 Telecommunications resiliency standards

Diverse path routing, automatic failover, and mean time to repair targets are documented per circuit. Client maintains current technical contacts for carrier coordination. MIJIRA LTD performs quarterly route optimisation reviews for multi-site publishers.

Implementation timelines for telecommunications resiliency standards are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for telecommunications resiliency standards deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.2 Satellite occasional use

Occasional use satellite bookings require forty-eight hour cancellation notice to avoid uplink fees. Weather diversity strategies and compressors for IP transport over satellite links are specified in technical appendices.

Implementation timelines for satellite occasional use are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for satellite occasional use deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.3 Edge computing for live events

Edge nodes may be deployed for stadium or festival streaming with local cache and upstream aggregation. Power and connectivity at venues remain Client responsibility unless expressly included.

Implementation timelines for edge computing for live events are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for edge computing for live events deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.4 Private cloud tenancy

Dedicated tenancy options isolate compute and storage for high-security newsroom workflows. Patch cycles may differ from shared cloud to accommodate Client change freezes during election periods.

Implementation timelines for private cloud tenancy are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for private cloud tenancy deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.5 Disaster recovery testing

Annual disaster recovery tests simulate origin loss and DNS failover. Client participation is required for application-level validation. Test reports summarise recovery times against objectives.

Implementation timelines for disaster recovery testing are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for disaster recovery testing deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.6 Content moderation SLAs

For social delivery services, moderation queue ingestion targets are defined in statements of work. Automated filtering integrates with Client policy engines; human review remains Client obligation unless managed moderation is purchased.

Implementation timelines for content moderation slas are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for content moderation slas deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.7 Screener forensic watermarking

Forensic watermark embedding for video screeners requires Client approval of watermark strength versus quality trade-offs. Leak tracing procedures are documented under confidentiality.

Implementation timelines for screener forensic watermarking are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for screener forensic watermarking deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.8 Print-digital hybrid workflows

Periodical clients combining print and digital editions may synchronise subscription entitlements via APIs. MIJIRA LTD supports webhook notifications for fulfilment status updates.

Implementation timelines for print-digital hybrid workflows are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for print-digital hybrid workflows deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.9 Podcast monetisation infrastructure

Dynamic ad insertion modules interface with Client ad servers. Latency budgets for ad decisioning are agreed to prevent listener drop-off.

Implementation timelines for podcast monetisation infrastructure are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for podcast monetisation infrastructure deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.10 Radio hybrid distribution

Simultaneous FM streaming and web streaming may share metadata pipelines. RDS and now-playing feeds require Client validation before public display.

Implementation timelines for radio hybrid distribution are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for radio hybrid distribution deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.11 TV catch-up rights windows

Catch-up retention defaults are Client-set per programme rights. Automated expiry jobs remove content when windows close unless manual holds apply for investigations.

Implementation timelines for tv catch-up rights windows are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for tv catch-up rights windows deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.12 Catalogue migration services

Sound recording catalogue migrations include metadata normalisation, duplicate detection, and royalty split validation tooling. Source files remain Client-owned throughout.

Implementation timelines for catalogue migration services are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for catalogue migration services deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.13 Subscriber authentication

Authentication integrations support SAML, OAuth, and magic links as configured. Client defines password policies and breach notification duties to subscribers.

Implementation timelines for subscriber authentication are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for subscriber authentication deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.14 Geo-compliance for sports rights

Sports streaming may require geo-fencing at county or postcode granularity. MIJIRA LTD implements IP and GPS-based checks as specified; VPN detection heuristics are optional add-ons.

Implementation timelines for geo-compliance for sports rights are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for geo-compliance for sports rights deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.15 Archive and long-term preservation

Cold storage tiers for motion picture archives use integrity checking and periodic media health reports. Retrieval times for glacier-tier objects are documented upfront.

Implementation timelines for archive and long-term preservation are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for archive and long-term preservation deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.16 API rate limiting fairness

Rate limits protect shared infrastructure. Enterprise clients receive dedicated quotas. Burst allowances apply for known live events with advance notice.

Implementation timelines for api rate limiting fairness are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for api rate limiting fairness deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.17 Environmental reporting

Power usage effectiveness metrics for colocation clients are available quarterly for corporate sustainability reporting.

Implementation timelines for environmental reporting are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for environmental reporting deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.18 Sanctions screening

Enterprise onboarding may include sanctions list screening for Client entities as required by law.

Implementation timelines for sanctions screening are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for sanctions screening deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.19 Insurance claims cooperation

MIJIRA LTD cooperates with Client insurance claims following incidents within our service scope, providing logs and witness statements subject to Fees for extensive production.

Implementation timelines for insurance claims cooperation are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for insurance claims cooperation deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

42.20 Training credits

Annual training credits for Client operations teams may be bundled in enterprise agreements, covering streaming operations and CMS administration basics.

Implementation timelines for training credits are agreed in onboarding plans with dependency tracking on Client content readiness, third-party licence approvals, and network provisioning lead times. MIJIRA LTD project managers coordinate weekly status during initial deployment phases and monthly thereafter for steady-state operations unless critical incidents demand ad hoc communication.

Risk registers maintained for training credits deployments capture identified technical, legal, and operational risks with mitigations and owners on both sides. High risks without agreed mitigation may delay go-live until resolved or accepted in writing by authorised Client representatives.

43. Detailed Payment and Credit Terms

Invoices are issued electronically to designated accounts payable contacts. Purchase order numbers must be supplied before invoicing where Client procurement rules require them. Disputed amounts do not excuse payment of undisputed portions. MIJIRA LTD may apply administrative fees for repeated late payments exceeding three instances in twelve months, notified in advance.

Direct debit and card payment options may be offered for recurring Fees under separate payment processor terms. Currency fluctuations for non-GBP invoices follow exchange rates published on invoice date unless fixed rates are contractually agreed.

44. Warranty Remedies

If Services fail to meet skill and care standards, Client shall notify within thirty days of discovery. MIJIRA LTD shall re-perform deficient Services or refund Fees attributable to deficient period at Client election, capped at one month recurring Fees for that component. Exclusive remedies for service quality claims are re-performance or refund unless mandatory law provides otherwise.

45. Third-Party Platform Dependencies

Integrations with DRM providers, ad servers, identity platforms, and social network APIs depend on third-party availability and policy changes. MIJIRA LTD is not liable for discontinuation of third-party features but will assist with reasonable workaround planning billed as professional services unless caused by MIJIRA misconfiguration.

46. Client Equipment and On-Premises Interfaces

Where Client equipment connects to MIJIRA networks, Client ensures patching, antivirus, and configuration meet minimum standards communicated during onboarding. MIJIRA LTD may disconnect non-compliant devices posing risk.

47. Publicity and Case Studies

Detailed case studies require Client approval of text and logos. MIJIRA LTD may reference generic industry sectors without naming Client where confidentiality agreements prohibit naming.

48. Ethical Conduct

Both parties shall conduct business ethically and comply with anti-bribery laws including the Bribery Act 2010. Gifts above nominal value require disclosure. Neither party shall offer improper inducements to public officials or broadcaster commissioning staff.

49. Modern Slavery

MIJIRA LTD maintains policies addressing modern slavery risks in supply chains and expects similar standards from Client where relevant to joint operations.

50. Records and Audit Trails

Operational records including change logs, access logs, and incident tickets are retained per service schedules. Clients may request extracts for compliance audits subject to reasonable Fees and scheduling.

51.1 Operational Detail: Managed hosting operational model

Routine patching, kernel updates, and middleware upgrades follow maintenance calendars published annually. Critical security patches may be expedited. Client custom configurations are documented before changes to enable rollback.

Service owners for managed hosting operational model conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for managed hosting operational model align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for managed hosting operational model is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.2 Operational Detail: Streaming analytics and audience measurement

Analytics dashboards present concurrent viewers, unique devices, average watch time, and geographic distribution at country or region granularity. Raw logs may be exported to Client data warehouses via secure pipelines. Data processing agreements govern personal data in analytics exports.

Service owners for streaming analytics and audience measurement conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for streaming analytics and audience measurement align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for streaming analytics and audience measurement is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.3 Operational Detail: Editorial CMS integrations

Publishing CMS platforms integrate with author directories, approval workflows, and embargo timers. Role-based editorial permissions mirror Client newsroom policies configured during implementation.

Service owners for editorial cms integrations conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for editorial cms integrations align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for editorial cms integrations is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.4 Operational Detail: Video transcoding farm operations

Transcoding queues prioritise live replay packaging over catalogue refresh jobs unless Client re-prioritises via API. Failed jobs retry with exponential backoff; persistent failures alert Client content operations.

Service owners for video transcoding farm operations conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for video transcoding farm operations align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for video transcoding farm operations is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.5 Operational Detail: Subtitle and caption pipelines

Supported caption formats include SRT, WebVTT, and broadcast-specific formats where specified. Automated speech-to-text may be integrated via third-party APIs with Client consent for training data use.

Service owners for subtitle and caption pipelines conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for subtitle and caption pipelines align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for subtitle and caption pipelines is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.6 Operational Detail: Digital rights management interfaces

DRM license servers remain Client-contracted unless MIJIRA provides managed interfaces. Key rotation schedules and device revocation lists are Client-managed with MIJIRA technical support.

Service owners for digital rights management interfaces conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for digital rights management interfaces align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for digital rights management interfaces is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.7 Operational Detail: Newspaper paywall integration

Metered paywall rules, subscription tiers, and corporate access lists sync via APIs. MIJIRA LTD does not store payment card data in CMS databases without PCI-compliant modules.

Service owners for newspaper paywall integration conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for newspaper paywall integration align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for newspaper paywall integration is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.8 Operational Detail: Periodical fulfilment data exchange

Print fulfilment partners receive export files on schedules defined in statements of work. Data quality validation reports highlight incomplete addresses before dispatch.

Service owners for periodical fulfilment data exchange conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for periodical fulfilment data exchange align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for periodical fulfilment data exchange is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.9 Operational Detail: Radio automation integration

Automation systems export now-playing metadata to streaming endpoints and smart speaker skills. Clock schedules remain Client-produced.

Service owners for radio automation integration conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for radio automation integration align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for radio automation integration is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.10 Operational Detail: TV electronic programme guide ingestion

EPG feeds ingest series identifiers, season metadata, and parental guidance labels. Corrections propagate within agreed latency for broadcast partners.

Service owners for tv electronic programme guide ingestion conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for tv electronic programme guide ingestion align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for tv electronic programme guide ingestion is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.11 Operational Detail: Satellite downlink monitoring

Signal quality metrics trigger alerts when thresholds breach. Failover to IP backup paths initiates automatically where configured.

Service owners for satellite downlink monitoring conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for satellite downlink monitoring align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for satellite downlink monitoring is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.12 Operational Detail: Sound recording mastering workflows

Master files upload through secure portals with checksum verification. Version history retains prior masters for rollback during remaster projects.

Service owners for sound recording mastering workflows conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for sound recording mastering workflows align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for sound recording mastering workflows is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.13 Operational Detail: Social community reporting tools

Users report content via in-player or in-app widgets creating tickets in Client moderation queues. SLA for ticket ingestion is sub-second under normal load.

Service owners for social community reporting tools conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for social community reporting tools align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for social community reporting tools is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.14 Operational Detail: Motion picture festival screening portals

Festival portals restrict playback to jury accounts with device limits. Watermark overlays display viewer identifiers for leak deterrence.

Service owners for motion picture festival screening portals conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for motion picture festival screening portals align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for motion picture festival screening portals is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.15 Operational Detail: Book publisher digital distribution

eBook files deliver through encrypted channels to retail partners as Client instructs. MIJIRA does not set retail pricing.

Service owners for book publisher digital distribution conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for book publisher digital distribution align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for book publisher digital distribution is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.16 Operational Detail: Telecoms billing reconciliation

Usage records for bandwidth and telephony interconnects reconcile monthly with variance thresholds triggering investigation.

Service owners for telecoms billing reconciliation conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for telecoms billing reconciliation align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for telecoms billing reconciliation is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.17 Operational Detail: Data processing batch windows

Overnight batch jobs process subscription renewals, royalty statements, and analytics rollups. Missed windows escalate automatically.

Service owners for data processing batch windows conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for data processing batch windows align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for data processing batch windows is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.18 Operational Detail: Web application firewall tuning

WAF rules balance security and false positives for editorial POST requests. Tuning sessions follow major CMS upgrades.

Service owners for web application firewall tuning conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for web application firewall tuning align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for web application firewall tuning is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.19 Operational Detail: DDoS mitigation playbooks

Volumetric attacks trigger upstream scrubbing centres. Client communication templates inform audiences during prolonged mitigation.

Service owners for ddos mitigation playbooks conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for ddos mitigation playbooks align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for ddos mitigation playbooks is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

51.20 Operational Detail: Identity federation for enterprise subscribers

Corporate SSO allows publisher subscribers to authenticate via Client IdP. Metadata refresh intervals and certificate expiry monitoring are configured jointly.

Service owners for identity federation for enterprise subscribers conduct post-incident reviews within ten business days of Severity 1 or 2 events affecting that component. Reviews document timeline, contributing factors, corrective actions, and Client communication effectiveness. Repeated incidents without remediation may trigger contractual performance discussions.

Capacity reviews for identity federation for enterprise subscribers align with Client editorial calendars including known peak events such as elections, sports tournaments, product launches, and seasonal programming. MIJIRA LTD recommends buffer capacity of at least fifteen percent above forecast peaks for live streaming workloads.

Documentation for identity federation for enterprise subscribers is updated within thirty days of material configuration changes. Client administrators receive notification when documentation versions change with summary of deltas relevant to operations teams.

52. Limitation Period for Claims

Except for fraud, confidentiality breaches, or indemnity obligations, neither party may bring claims arising from the Agreement more than twenty-four months after the event giving rise to the claim, or twelve months after termination for latent defects discoverable with reasonable diligence.

53. Counterparts and Electronic Signatures

The Agreement may be executed in counterparts and by electronic signature mechanisms recognised under applicable law, each counterpart constituting an original.

54. Relationship of Parties

The parties are independent contractors. Nothing creates partnership, joint venture, or employment relationship. MIJIRA LTD personnel are not entitled to Client employee benefits.

55. Order of Execution

In case of multiple statements of work, global terms in the master agreement prevail. Conflicts between statements of work are resolved by most recent execution date for overlapping scope unless merger clauses specify integration rules.

56. Contact and Notices Confirmation

Contractual notices to MIJIRA LTD must be sent to general@mijira.site with read receipt requested and copy to the registered office address. Operational support notices follow channels in service schedules.