FENDRIX CLOUD / LEGAL

Terms of Service

Last Updated: September 8, 2026

These Terms of Service describe the general framework under which Fendrix Cloud may provide software-development, cloud, integration, DevOps, AI-related, maintenance, and technical consulting services. Specific projects should be governed by a signed proposal, services agreement, statement of work, order form, or similar document that defines scope, fees, schedule, deliverables, responsibilities, and project-specific terms.

1. Scope of Services

Services may include SaaS product development, custom web applications, cloud architecture and consulting, API development and integration, business-process automation, cloud migration and modernization, DevOps and CI/CD implementation, software maintenance and support, AI-enabled functionality, UI/UX work, technical planning, deployment support, and enterprise software development.

No service is automatically included merely because it appears on the website. The agreed written scope controls.

2. Project Discovery and Requirements

Software projects depend on accurate requirements and timely decisions. Clients are responsible for providing relevant business rules, stakeholder input, access to existing systems, technical documentation, lawful data, third-party account information, and approvals reasonably required for the work. Material changes to requirements may require schedule, scope, or fee adjustments.

3. Client Responsibilities

• Provide timely feedback and approvals.
• Ensure that materials, data, content, software, and credentials supplied for the project may lawfully be used.
• Maintain appropriate backups of systems and data unless backup services are expressly included.
• Obtain required third-party licenses and subscriptions unless otherwise agreed.
• Designate authorized project contacts who may provide binding operational decisions for the engagement.

4. Development and Delivery

Development may be completed in phases, milestones, iterations, or other delivery units appropriate to the project. Technical implementation may evolve as requirements are clarified, dependencies are discovered, or more maintainable solutions are identified. A schedule is an estimate unless the signed agreement expressly states otherwise.

5. Testing and Acceptance

The applicable project agreement should define acceptance procedures where formal acceptance is required. Clients are expected to review deliverables within the agreed review period and provide specific issue reports. Defects are distinguished from new features, changed requirements, third-party failures, unsupported environments, and issues caused by modifications made outside the agreed work.

6. Cloud and Third-Party Dependencies

Many software systems depend on external cloud providers, APIs, libraries, frameworks, AI services, payment processors, communications platforms, data providers, or other vendors. Fendrix Cloud does not control third-party uptime, pricing, policies, rate limits, model behavior, deprecations, security incidents, or product changes. Work needed because of third-party changes may be treated as additional scope unless covered by an active support agreement.

7. AI-Related Services

When AI-powered functionality is included, outputs may be probabilistic, incomplete, or incorrect. Appropriate human review, guardrails, testing, permissions, logging, and use-case controls may be required. Fendrix Cloud does not guarantee that an AI system will produce a particular answer, business outcome, or level of accuracy unless a specific measurable acceptance criterion is expressly agreed in writing.

8. Intellectual Property and Licenses

Ownership and license rights for custom project deliverables, pre-existing materials, open-source software, reusable development tools, templates, libraries, and third-party components must be determined by the signed project agreement. Open-source and third-party components remain subject to their applicable licenses.

9. Security

Reasonable secure-development practices may be used according to project scope, but no software system can be guaranteed invulnerable. Security requirements, compliance obligations, penetration testing, regulated-data controls, backup objectives, disaster recovery, high availability, and formal certifications must be expressly scoped if required.

10. Maintenance and Support

Maintenance may include issue resolution, dependency updates, operational support, monitoring coordination, minor improvements, and planned technical work as defined by the applicable support plan. Monthly support does not automatically include unlimited feature development, major redesigns, large migrations, emergency work outside agreed hours, or third-party fees.

11. Suspension or Termination

A project may be suspended for material nonpayment, unlawful instructions, unresolved security concerns, failure to provide required access or decisions, or other material breach, subject to the applicable written agreement. Termination rights and payment obligations should be defined in that agreement.

12. No Business Outcome Guarantee

Software can support operations and growth, but no particular revenue, funding, market adoption, conversion rate, cost savings, search ranking, regulatory approval, or commercial outcome is guaranteed unless an express written commitment states otherwise.