General terms

Clients and users must have the legal capacity to enter contracts and comply with local laws. Engagements typically involve businesses, public sector entities, and legally authorized representatives acting on behalf of an organization.

Services are not intended for individuals under 18 acting on their own behalf; organizations engaging on behalf of minors must confirm lawful authority and consent where required.

Services must be used lawfully; clients must not request software to be developed for activities that contravene Singapore law or internationally accepted human rights standards.

Lumisara operates from Singapore and may restrict services in jurisdictions subject to export controls or sanctions. Project feasibility and legal compliance are evaluated during initial scoping.

Where an account is required to access development portals, staging environments, or support tools, the account holder is responsible for account setup, correctness of information, and authorized users.

Clients must provide accurate, complete information for billing, contact, and project scope. Case example: scope changes discovered after delivery will be handled through change requests and documented cost/time impacts.

Clients must protect credentials and follow recommended security practices. Lumisara implements recommended controls on its side but requires clients to maintain secure passwords and multi-factor authentication where supported.

Accounts are non-transferable except where explicit written agreement between Lumisara and the organization owner is provided.

If an account compromise is suspected, notify Lumisara immediately. We will outline containment steps, evidence preservation, and coordination with any third-party providers involved in the project.

Lumisara may suspend access to services for security reasons, non-payment, or material breach. Suspension notices include practical instructions for remediation and data access where feasible.

Lumisara delivers custom software development, systems integration, API design, and operational tooling tailored to business processes. Service scope is defined in statements of work that include deliverables, timelines, and acceptance criteria based on use-case scenarios.

Scope changes are managed via change requests with documented impacts on cost and schedule. Case-driven change governance ensures traceability and predictable outcomes for incremental deliveries.

Availability commitments are specified per engagement. For example, a managed platform for operational reporting may include monitored uptime targets and scheduled maintenance windows agreed in the service schedule.

To protect systems and other users, clients must follow the rules below; practical examples are included to illustrate prohibited and permitted activities.

• Do not attempt to reverse-engineer or extract source code from hosted environments without explicit permission and contractual provisions for code access.
• Do not upload or process data that violates privacy laws or contains unlawfully obtained information; when such data is identified, stop processing and notify Lumisara for remediation.
• Use APIs and integrations within documented rate limits and patterns; abusive traffic that impacts other clients may be throttled.
• Respect intellectual property rights; do not use third-party licensed components beyond their permitted scope without notifying Lumisara for licensing advice.
• Follow security and deployment guidelines for production rollouts; ad-hoc changes that bypass staging and approvals are not permitted.
• Provide timely responses to information requests during development sprints; delayed feedback can affect timelines and will be handled through agreed change controls.
• Coordinate public communications about shared case studies or references with Lumisara before publishing.

Client content includes specifications, data, documents, and materials submitted during an engagement. We treat client content according to the processing rules set out in the project agreement and this document.

Clients retain ownership of their pre-existing content and data. For code and deliverables, ownership and licensing are defined in the statement of work and intellectual property section below.

Clients grant Lumisara a limited license to use client content solely to perform the contracted services, including integration, testing, and deployment activities.

Clients are responsible for ensuring that content they provide does not infringe third-party rights and complies with applicable laws; practical checks during onboarding reduce downstream risk.

Requests to remove or return client content after project completion are handled per the retention schedule. For example, archived test data may be purged 90 days after project closure unless otherwise agreed.

IP arrangements differ by project: custom code, templates, and third-party components are identified and documented. Statements of work specify which deliverables are transferred under license and which are retained as Lumisara-owned assets.

• Clients must not reproduce Lumisara proprietary tooling beyond the license terms set out in the agreement.
• Reverse-engineering Lumisara-owned platforms without permission is prohibited.
• Where open-source components are used, their licenses remain in force; we include a manifest of such components in delivery artifacts.

Fees, invoicing schedules, and milestones are specified in the proposal and SOW. Billing examples include time-and-materials for exploratory work and fixed-price milestones for defined deliverables.

Pricing reflects scope, complexity, and resource planning. Pricing adjustments due to scope change are handled via documented change requests with transparent cost breakdowns.

Invoices are payable within the agreed term. Payment details and methods are included on invoices; late payments may incur interest as specified in the engagement agreement.

For subscription-based managed services, fees recur as specified in the subscription schedule and include renewal mechanics and termination notice periods.

Refunds are considered on a case-by-case basis and depend on the nature of the service and work completed; dispute resolution and evidence of work performed are factors in such evaluations.

Cancellation terms are set out in the SOW. Early termination may require payment for work completed, transition assistance, and costs associated with winding down services.

Clients are responsible for any taxes applicable to payments, in accordance with local tax regulations. Tax handling examples are included in standard commercial terms.

Price changes for ongoing subscriptions are notified in advance with rationale and a transition period for clients to accept or terminate the service per the agreement.

Non-payment may result in suspension of services after notice; restoration follows settlement of outstanding amounts and any applicable reactivation fees.

Lumisara provides professional services based on accepted standards and documented case practices. Outcomes depend on client inputs, environment constraints, and timely cooperation; references to typical results are illustrative and not promises of specific outcomes.

Liability is limited as set out in the agreement and applicable law. Typical disclaimers include caps tied to fees paid for the relevant service period and exclusions for indirect or consequential losses, subject to mandatory statutory protections.

Where third-party services, libraries, or platforms are used, their terms apply. Lumisara coordinates integration and compliance, and documents third-party dependencies in delivery materials and post-implementation support plans.

Either party may terminate for material breach after a notice and cure period as specified in the agreement. Termination conditions vary by contract type; e.g., fixed-term retained services include defined exit and handover procedures.

Upon termination, client access to services may be suspended. Transition assistance, data export, and final invoices are handled per the termination schedule to minimize operational disruption.

We process personal data in line with the privacy notice on jradius.pro and applicable Singapore data protection law. Practical safeguards, data minimization, and incident response procedures are integrated into project delivery.

Notices under these Terms should be sent to the contact details in the statement of work or to [email protected]. Operational communications about projects are routed through designated account leads to ensure traceability.

Material changes to these Terms will be communicated in advance. For ongoing projects, changes affecting delivery or cost will be proposed via formal change control and require mutual agreement.

These Terms are governed by the laws of Singapore. Dispute resolution procedures and jurisdictional considerations are described in the agreement and tailored to the client's commercial risk profile.

Disputes are first addressed through escalation between client and Lumisara account leads. Where unresolved, mediation or arbitration clauses in the commercial agreement may apply as practical alternatives to litigation.