Eligibility
To use LogicMApps services you must be able to form legally binding contracts in Malaysia. Entities using our enterprise services should supply accurate organizational details and a designated technical contact to coordinate assessments and deployments.
Individuals must be at least 18 years old or the legal age to enter contracts in their jurisdiction to enter into agreements with LogicMApps.
Services must be used lawfully. Examples of prohibited uses include attempts to circumvent software licensing controls, misuse of data for unlawful profiling, or launching attacks against third-party networks.
LogicMApps operates from Malaysia and may restrict services in jurisdictions subject to export controls or sanctions. Clients should confirm compliance with applicable laws for cross-border projects.
Accounts
Enterprise accounts with LogicMApps enable service management, support access, and deployment coordination. Accounts must reflect current contact and billing details and be managed by authorized representatives.
Clients are responsible for maintaining accurate contact and organizational information. Case example: updated contact details ensure timely incident coordination during a scheduled migration window.
Clients must protect account credentials and use recommended security controls, such as multi-factor authentication and role-based access. LogicMApps provides guidance for securing API keys and deployment pipelines.
Account access is specific to the registered entity and should not be transferred without prior written approval from LogicMApps and an executed amendment to the agreement.
If you suspect account compromise, notify LogicMApps support immediately and follow the incident response steps provided in your engagement plan. Timely notification helps minimize operational impact.
LogicMApps may suspend account access for non-payment, abuse, or legal orders. In such cases we will communicate the reason and remediation steps, and work to restore services once the issue is addressed.
Service scope
Services include assessments, architecture design, software development, integrations, and managed operations as specified in the applicable statement of work. Each engagement includes defined milestones and acceptance criteria to align technical outcomes with business objectives.
Service scope can change through written change requests. A case example: adding a real-time analytics pipeline mid-project will require an updated timeline and cost estimate documented in a change order.
We design solutions with availability targets appropriate to the chosen architecture. Availability commitments are described in the statement of work and are tied to documented operational runbooks and monitoring practices.
Acceptable use rules
Users must follow reasonable usage rules to preserve system integrity and service quality. The following list provides examples rather than exhaustive items.
- Do not attempt to degrade service performance through abuse or denial-of-service.
- Respect third-party intellectual property and licensing terms when integrating external components.
- Avoid uploading or transmitting content that violates privacy or data protection laws applicable in Malaysia.
- Use testing and staging environments for load testing; coordinate planned tests with LogicMApps support.
- Do not share account credentials; use IAM controls and audit logs to manage team access.
- Report vulnerabilities responsibly to the contact specified in your engagement so they can be remediated.
- Follow export control and data residency requirements agreed in the statement of work.
User content
User content includes configurations, data uploads, and code provided to or generated by LogicMApps during an engagement. Ownership and licensing depend on contractual terms.
Clients retain ownership of their data and customer content. LogicMApps retains ownership of pre-existing tools, templates, and proprietary software used to deliver services unless otherwise assigned in writing.
Clients grant LogicMApps a limited, non-exclusive license to process and store content solely to deliver contracted services. Example: code provided for integration will be used to build and test the delivered solution.
Clients are responsible for ensuring that uploaded content does not violate third-party rights and that necessary consents are in place for processing personal data in line with applicable law.
LogicMApps may remove content that violates these terms or applicable law. For contested removals we provide a contact path and review process described in the engagement documentation.
Intellectual property
Intellectual property created under a project is allocated according to the statement of work. Typical models: client owns bespoke code and configurations, while LogicMApps licenses reusable components under defined terms.
- Clients must not reverse engineer or redistribute LogicMApps proprietary modules without authorization.
- Use of open-source components is subject to their licenses; clients and LogicMApps will follow compliance processes described in the SOW.
- Deliverables identified as 'work for hire' in the contract are assigned to the client as specified in the agreement.
Paid services
Paid services are provided under a commercial agreement with defined deliverables, pricing, and payment terms. Engagements often begin with a scoped pilot project to validate assumptions before a broader rollout.
Pricing is specified in the proposal and varies by scope, technology, and level of managed services. Example: an assessment has a fixed fee, while managed operations may be billed monthly based on agreed SLAs.
Payments are due as set out in the invoice schedule. Accepted payment methods and invoicing details are in the commercial proposal. Late payments may incur administrative holds on services.
Subscription services (e.g., managed monitoring) are billed on a recurring basis and include notice periods for termination described in the contract.
Refunds are considered in line with the contract terms. For example, if a prepaid pilot is not delivered per the agreed milestones, a pro-rated refund or credit may be issued following a documented review.
Cancellations require written notice. Cancellations during active work may trigger charges for work completed to date and non-recoverable third-party costs.
Clients are responsible for any taxes associated with the services, as required by local law. LogicMApps will itemize applicable taxes on invoices where required.
Price adjustments for ongoing services will be notified with reasonable advance notice and documented in an amendment to the agreement.
Non-payment may result in suspension of services. We provide remediation steps and a timeline to restore services once payment or a dispute resolution is reached.
Disclaimer
LogicMApps provides services based on current best practices and documented case experience. Technical recommendations are offered to improve reliability and scalability, but actual outcomes depend on client environments, data quality, and cooperation in implementation.
Limitation of liability
Liability is limited to the extent permitted by law and as set out in commercial agreements. Example: indirect or consequential losses arising from third-party outages are typically excluded unless expressly covered in a separate agreement.
Third-party services
Projects often rely on third-party cloud providers, software, or APIs. Clients are responsible for third-party licensing and compliance. LogicMApps assists in vendor selection and integration but does not assume third-party obligations unless specified.
Termination
Either party may terminate for material breach if the breach is not remedied within the cure period specified in the agreement. Termination processes are illustrated in the SOW with steps for knowledge transfer and data return.
On termination, outstanding fees for services performed become due and we coordinate secure handover of client data and documentation per the agreed offboarding plan.
Privacy
LogicMApps handles personal data in accordance with privacy obligations applicable in Malaysia. Data processing is limited to service delivery, troubleshooting, and improvement of project outcomes. Data retention and deletion procedures are documented in the engagement plan.
Communications
Official communications are sent to the account contacts and designated technical leads. For incident communications, we follow the notification and escalation paths defined in the SOW.
Changes to terms
We may update these terms to reflect operational or legal changes. Material changes are communicated with reasonable notice and will be reflected in the client portal and via email to account contacts.
Governing law
These terms are governed by the laws applicable in Malaysia. Disputes will follow the dispute resolution procedures set out in the commercial agreement.
Dispute resolution
Commercial disputes are handled through the escalation path in the agreement, starting with technical mediation, then senior management review, followed by the agreed legal procedures if necessary.
