Project Cancellation & Refund Policy

1. Purpose and scope

This policy describes WebTownship's general approach to project cancellation, termination, final settlement and refunds for professional services such as custom software development, SaaS development, web applications, websites, e-commerce, mobile applications, UI/UX and product design, SEO and digital growth, optimization, maintenance and technical support.

Because these services are customized, this page is a general commercial framework rather than a universal refund formula. The rights and obligations for a particular engagement are determined primarily by the signed project documents for that engagement.

2. Project-specific documents govern the engagement

Before work begins, WebTownship and the client may execute one or more documents that define the commercial relationship. Depending on the engagement, these may include a Service Agreement or Master Services Agreement, a Project Agreement, Statement of Work, proposal, order form, payment schedule or approved Change Order.

Common project documents

• NDA, where required: protects confidential business, product and technical information and does not ordinarily replace the commercial project terms.
• Service Agreement / MSA: sets the wider commercial and legal relationship where an MSA or equivalent agreement is used.
• Project Agreement / SOW: defines scope, deliverables, milestones, payment schedule, acceptance, dependencies and cancellation or termination terms.
• Change Order: records material changes to scope, price, responsibilities or timeline after the original project terms have been agreed.

3. Cancellation requested by the client

A client who wishes to cancel or terminate an engagement should provide written notice through the communication method specified in the applicable agreement, or otherwise by email to an authorized WebTownship contact.

• WebTownship may stop new discretionary work after receiving the cancellation notice while preserving work, records and systems required for an orderly close.
• Completed work, accepted milestones, services already performed and other amounts already earned are generally taken into account in the final settlement and are not automatically refundable.
• Approved or unavoidable third-party commitments may also be included in the settlement where they cannot reasonably be cancelled or recovered.
• Any unused prepaid amount, credit or remaining balance will be handled according to the project-specific agreement and the status of the engagement on the effective cancellation date.

4. Cancellation or termination by WebTownship

WebTownship may cancel, suspend or terminate an engagement where permitted by the applicable agreement, including circumstances such as prolonged non-payment, material breach, unlawful or unsafe requirements, repeated failure to provide essential client dependencies, or other conditions specifically defined in the signed terms.

If WebTownship ends an engagement for reasons not caused by client breach, the project will be reconciled fairly according to the work performed, amounts earned, third-party commitments and the project-specific agreement. Any unearned prepaid amount that is refundable under those terms will be identified in the final settlement.

5. Refunds, credits and final settlement

WebTownship does not use a single public hourly deduction or one-size-fits-all refund formula for every project. The financial outcome of cancellation depends on the commercial model and signed terms of the engagement.

What may be considered during reconciliation

• Completed work: completed milestones, accepted deliverables or services already performed may remain payable and are generally not treated as unused prepayments.
• Unused prepaid amounts: where the project agreement provides for it, genuinely unearned prepaid amounts may be refunded or credited after final reconciliation.
• Third-party costs: domains, hosting, cloud services, licenses, plugins, paid APIs, advertising spend, stock assets or other approved external costs may be non-refundable where WebTownship cannot recover them.
• Outstanding balances: if earned fees or committed costs exceed prepaid amounts, the client may have an outstanding balance payable under the applicable agreement.

6. Quality issues are handled through correction first

If a deliverable materially fails to meet agreed scope or acceptance criteria, the client should report the issue in writing with enough detail for WebTownship to investigate. Where reasonably possible and contractually applicable, WebTownship should be given an opportunity to correct, re-perform or resubmit the affected work before refund or termination remedies are considered.

Acceptance periods, testing procedures, warranty periods and remedies may vary by project and should be specified in the applicable Project Agreement or SOW.

7. Client delays, inactive projects and project pauses

Technology projects often depend on timely client approvals, content, credentials, access to systems, feedback, legal approvals or other inputs. If required dependencies are delayed for an extended period, WebTownship may pause, reschedule or close the engagement in accordance with the applicable agreement.

Any effect on timeline, reserved capacity, fees, reactivation costs or cancellation settlement should be determined by the signed project terms rather than by an informal assumption.

8. Material changes should be documented

Requests that materially change scope, deliverables, responsibilities, integrations, delivery dates or commercial terms should be documented through an approved Change Order, revised SOW or equivalent written amendment.

This protects both parties by keeping the agreed project baseline clear and reducing disputes about what was included in the original engagement.

9. Orderly handover and project closure

When an engagement ends, WebTownship and the client should complete a clear closure process. The exact handover depends on payment status, intellectual-property provisions, third-party rights and the project-specific agreement.

1. Written notice: the cancellation or termination request is recorded.
2. Acknowledgement: the effective date and immediate next steps are confirmed.
3. Project review: completed work, commitments and dependencies are assessed.
4. Settlement: any refund, credit or outstanding balance is calculated.
5. Handover: eligible paid-for deliverables and access are transferred.
6. Closure: the engagement is formally closed and records retained as required.

Source code, design files, credentials, documentation, domain or hosting access and other project materials are transferred only to the extent provided by the signed agreement, applicable payment status, third-party licensing terms and applicable law.

10. Applicable law and non-excludable rights

Nothing in this policy is intended to exclude, restrict or waive rights or remedies that cannot lawfully be excluded. Where mandatory law provides a client or consumer with rights in relation to deficient services, those rights remain subject to the applicable law and the facts of the engagement.

If this general policy conflicts with a project-specific signed agreement, the project-specific agreement governs to the extent permitted by applicable law.

11. Questions about cancellation or settlement

For questions about an active project, clients should contact their authorized WebTownship project or account contact and refer to the applicable Project Agreement or SOW. General policy questions may be sent to info@webtownship.com.