Delivery Policy

All work is delivered digitally. There is no physical product, no courier, no shipping charge and no delivery address. Any reference to shipping in a payment receipt is the payment provider’s standard wording, not an indication that something is in transit.

Depending on the engagement, delivery is one or more of:

• A deployed site or application at a URL you control.
• Source code in a repository you own or have been granted access to.
• Design files shared to your Figma account.
• Written documentation, handed over as files or in your own documentation system.
• Scheduled hours of work, for retainer engagements.

What counts as delivery for your engagement is set out in the proposal before any payment is taken.

Access credentials, repository invitations and file shares are issued within 2 business days of confirmed payment.

Project delivery dates are agreed in the proposal and depend on the scope. Where a date is at risk, you are told before it passes, not after.

Retainer hours begin on the start date of the retainer period and are reported monthly.

On final payment, ownership of the delivered work transfers to you. That includes source code, design files and content produced for the engagement.

Third-party components keep their own licences, and any that carry ongoing cost or restriction are named in the proposal before you commit to them.

Email anandhusiva1234@gmail.com and access will be reissued. Delivery problems are almost always an email going to spam or an invitation sent to the wrong address, and both are quick to fix.