Cancellation Policy

This policy applies to cancelling a development project, a platform configuration, or an ongoing service such as hosting, maintenance or support.

Where a signed contract sets different cancellation terms for an engagement, that contract applies to it and this page does not.

Up to the point where you sign a scope, you can walk away and nothing is owed in either direction. Quoting is free and there is no obligation attached to it.

Cancel by writing to info@algoryntech.com. The date we receive your notice is the date the project stops.

We then do three things. We stop work and stop incurring cost on your behalf. We set out in writing what has been delivered and approved, and what that comes to. We hand over the work you have paid for.

What happens to money already paid is set out in the Refund Policy.

Hosting, maintenance, support and retainers are cancelled with 30 days written notice. The notice period gives us time to hand over data, transfer or close infrastructure, and take your work off our monitoring.

Service runs normally until the notice period ends. The period already served is not refunded.

On cancellation you receive the following for work you have paid for in full.

• The source code and project files produced to that point.
• Your data, exported in a standard format.
• Credentials and access to accounts and infrastructure held in your name.
• Documentation of what was built and what remained outstanding.

We keep nothing back as leverage. Unpaid work is not handed over, which is the only thing that is withheld.

We may end an engagement where an invoice remains unpaid after notice, where the Terms and Conditions are breached, or where the work becomes unlawful.

If that happens we give you written notice, hand over everything you have paid for, and invoice only for work already delivered.

Projects are sometimes paused rather than cancelled, because a budget moves or a decision is waiting on somebody else. Tell us and we will agree a pause in writing, including what happens to the schedule and to team availability when you restart.

Pausing is usually cheaper than cancelling and restarting, so it is worth asking before you cancel.