Website notice / Updated 3 November 2026
Cancellations and refunds
How to raise a change, cancellation or payment question concerning an actual project.
1. Browsing and enquiry are not a purchase
Viewing a study, reading a service description and preparing the local contact draft do not create a paid order. There is no portfolio checkout, recurring membership or automatic charge to reverse through this website. A request concerning a payment therefore needs to identify the actual arrangement and the person or service that received it. Sending an introductory enquiry does not itself cancel that arrangement. Any rights concerning work or money arise from the relevant facts, agreement and applicable rules rather than the act of browsing.
2. Changing the commissioned scope
A request to stop interface work should identify the engagement and the point reached: visual direction, screen exploration, component definition or agreed handover. Changing the user journey or adding new states can differ from correcting an error against an accepted brief. The effect on fees, work in progress and deliverables depends on the actual agreement and applicable rights. No universal cancellation charge or automatic full-refund promise is stated on this website. Keep the approval record so the discussion concerns the real scope and work supplied.
3. Deliverables and separate suppliers
For a commissioned interface project, clarify the treatment of supplied assets, design files and approved specifications if the work changes or stops. A design engagement can be separate from development, hosting, software licences or application subscriptions. Ending one arrangement does not necessarily stop those other services. Identify the recipient of any charge before requesting repayment. The portfolio has no checkout and cannot reverse an external payment or revoke software access. Any handover or continuing-use question should be resolved with the agreement and relevant parties in view.
4. Describing a project-specific concern
Describe a concern with the screen, state, specification or handover version involved, and explain the outcome requested. Distinguish work that differs from the agreed brief from a new product requirement or a later implementation defect. Relevant review comments and acceptance records can help locate the matter. Do not send a production credential, real customer export or full payment information with a complaint. Confirm an appropriate channel if confidential evidence is necessary; the portfolio’s local draft tool is not a secure file-transfer or support-ticket system.
5. A confirmed repayment arrangement
Where a repayment is agreed or required, confirm the amount, currency, responsible recipient and practical method. A bank or payment service can have its own processing role and timing. This website does not execute a refund or promise an unverified date for funds to arrive. A draft shown in the browser is neither acknowledgement of a request nor a decision about its merits. Retain the response and payment records relevant to the actual arrangement, using the established transaction channel when a time-sensitive issue needs attention.
6. Records and continuing remedies
A general website notice does not settle every cancellation question or remove rights that apply despite a disclaimer. Identify any part of a response that remains unresolved and the relevant facts you believe were missed. Keep accepted terms, approvals and correspondence so the matter can be considered consistently. No exclusive forum, invented banking guarantee or blanket rule that every creative service is non-refundable is imposed here. Available remedies and complaint routes depend on the real circumstances, agreement and applicable law.