FENDRIX CLOUD / LEGAL

Cancellation & Refund Policy

Last Updated: September 8, 2026

This Cancellation & Refund Policy explains the general approach to cancellation, project pauses, and refunds for professional software-development and technical services. Because most work is customized, labor-intensive, and scheduled around dedicated resources, cancellations are not treated like returns of ordinary consumer goods. The signed agreement for a project controls if it contains different terms.

1. Before Work Begins

If a client cancels before scheduled work has begun, any refund depends on the written agreement, non-refundable reservation or discovery fees, third-party costs already incurred, and administrative or planning work already completed. A payment is not automatically refundable merely because coding has not yet started if discovery, architecture, scheduling, procurement, or setup work has already been performed.

2. After Work Begins

Once work begins, fees attributable to work performed, committed project time, completed milestones, approved purchases, third-party services, and non-cancellable obligations are generally not refundable. Any unused prepaid amount may be handled according to the project agreement after outstanding fees and costs are reconciled.

3. Milestone Projects

For milestone-based engagements, approved or completed milestones are ordinarily non-refundable. If a project is cancelled between milestones, Fendrix Cloud may invoice for work completed through the effective cancellation date, including partially completed work where permitted by the applicable agreement.

4. Monthly Maintenance and Support

Recurring maintenance and support fees compensate for reserved availability and ongoing technical responsibility. Unless otherwise stated in the applicable agreement, amounts already earned for an active billing period are not refundable. Cancellation affects future periods according to the required notice period, if any.

5. Client Delays and Paused Projects

If a project is delayed because required information, access, approvals, content, credentials, decisions, or feedback are not provided, Fendrix Cloud may pause the schedule and reassign resources. Restart dates are subject to availability. Extended pauses may require re-planning or a revised commercial arrangement.

6. Scope Changes

A request to remove features after work has been planned or started does not necessarily create a refund. Work already completed or committed remains billable. The parties may instead agree to reallocate remaining budget to other approved work.

7. Third-Party Fees

Cloud subscriptions, software licenses, domain costs, API fees, AI usage charges, data services, paid libraries, and other third-party expenses are subject to the provider’s own refund rules and may be non-refundable.

8. How to Request Cancellation

A cancellation request should be made in writing and should identify the project, authorized client contact, requested effective date, and any requested transition or handoff. Cancellation becomes effective according to the governing project agreement, not merely when a message is sent.

9. Final Handoff

Subject to payment and contract terms, available project materials may be provided in the agreed form after cancellation. Transition assistance, migration work, documentation beyond the existing scope, or expedited handoff may require additional fees.