Terms & Conditions

We require a 50% upfront payment of the total project cost before starting. The remaining 50% is due on delivery.

Example · If your website project costs $1,000, you pay $500 upfront to begin, and the remaining $500 on delivery.

You provide the technical details we need to build (domain, hosting, API keys, payment gateway credentials) so development can move.

Example · For an online store, you share your PayPal or Shopify credentials for secure integration.

Some tasks, like setting up payment systems, need temporary access to your accounts. You agree to share those credentials, trusting us to handle them securely.

Example · To integrate a payment gateway, you might share Stripe API keys for us to connect it to your site.

We share regular updates through the project so you can track progress and steer changes. Clear communication keeps us on the same page.

Example · We might show a preview of your app's homepage and ask for feedback on the layout.

After delivery you get one free revision. List every change in a single Google Doc; further revisions are charged separately.

Example · A colour change or button tweak fits the free revision. Adding a new feature (a chatbot, say) comes with its own quote.

Any feature or change you want after the scope is agreed comes with a fresh estimate. You pay 20% upfront on that estimate to proceed, and the timeline extends by whatever the new work needs.

Example · Adding a blog mid-project might come in at $400 over 10 days; you pay $80 upfront to start.

For multi-stage projects, each milestone is paid before we move to the next. It keeps the work honest and the schedule predictable.

Example · For a mobile app, that means paying for the design phase, then the build phase, then testing, one after the other.

If you cancel mid-project we settle a refund based on the work completed. The percentage is agreed between us.

Example · If you cancel at roughly the halfway point, a 50% refund is a reasonable starting position.

On delivery we add a small "Built by CodeMyPixel" line in the footer, and we may show screenshots of the finished work in our portfolio. Your ideas, code and business logic stay confidential. That part is not negotiable.

Example · Your footer might read "Powered by CodeMyPixel" and a homepage screenshot might appear in our case studies; nothing under the hood ever does.

Any bug that surfaces in what we built is fixed free, for as long as the product runs. That is our default. What we can't own is code someone else has changed after handover. Those fixes are theirs.

Example · A button that stops working in our code, we fix. A button broken by another developer editing that code, we don't.