Delivery format
Your proposal identifies the deliverables and the agreed handover channel, such as a download link, repository transfer, email or deployment to an authorised hosting account.
When the schedule starts
The written proposal states the project start conditions, milestones and expected delivery date or period before you agree. Work starts after acceptance and receipt of the agreed inputs and any agreed initial payment. There is no universal delivery time for all services.
Delays and changes
Missing content or access, late feedback, third-party approvals and agreed scope changes can affect delivery. We explain material changes and confirm a revised schedule in writing. If we cannot deliver the agreed scope, contact us to discuss a revised agreement or cancellation and refund of unperformed work under our refund policy.
Review and acceptance
The agreement describes milestones, review stages and acceptance criteria. Review deliverables against the agreed scope and report issues through the project contact channel.
Files, access and deployment
Source files, editable assets, credentials transfer and deployment are included only as specified. Third-party licences and platform requirements continue to apply. Secrets should be exchanged through an appropriate secure channel.
After handover
Any support, maintenance, hosting or future updates are governed by the agreed service scope. Retain a copy of your final materials and the relevant account access.
For questions about this policy: Contact us ↗