Refund Policy

Before work starts

If your project is cancelled before work on it starts, you may be eligible for a refund of the amounts you have paid, less any non-refundable third-party or payment-processing costs already incurred, subject to applicable law.

Any refund is based on the amounts we have actually received.

After work starts

Once work has started, a full refund is not automatic. We may keep the value of the work already completed, and any remaining eligible amount may be refunded.

The refundable amount is calculated from the project's progress and the work completed up to the cancellation. Completed custom work and assets may remain chargeable.

Third-party costs

Amounts already paid or committed for domains, hosting, paid assets, plugins, external services or other third-party purchases made specifically for your project are not automatically refundable.

After final deployment

Payments for a completed and deployed project are not automatically refundable.

A bug within the approved scope is handled under the 14-day post-deployment support described in our Terms. New work and change requests are separate paid work.

Your mandatory rights

Nothing in this policy limits a mandatory legal or consumer-protection right that you have under the law that applies to you.

What happens when we approve a refund

A refund is recorded against your project as a negative entry in your payment record. Nothing is deleted or rewritten: the original payment and the refund both stay visible to you, with their dates.

Your deposit and your remaining balance are then recalculated from that record. What you owe is always derived from what has actually been credited, never from a flag somebody sets by hand.

A refund that has been requested but not yet approved changes nothing in your payment record. A partial refund reduces what has been credited by its own amount only: it never cancels, recreates or resets the other payments on your project.

A refund before deployment

If a refund takes what has been credited below your project total, your website cannot be deployed until the balance is settled again. The portal will say so, and will name the exact amount outstanding.

This is a technical consequence of how payment is checked, not a penalty. If the balance is restored, deployment can proceed.

A refund after deployment

Once your website has been deployed to your own hosting, it is on infrastructure you control. A refund does not remove it, take it offline or undo the deployment, and we do not delete anything from your hosting.

Your payment record still shows the refund, so your account remains accurate.

How a refund reaches you

A refund is returned by the same route the payment arrived, to the account it came from.

If somebody contacts you asking you to accept a refund by another route, or to a different account, it did not come from us. Check with support@meedagency.com first.

How to ask

Write to support@meedagency.com with your project reference and what you are asking for. We aim to respond within 2 business days. That is a response target, not a guaranteed decision time.

Disputes

If you disagree with an amount, tell us before you raise it with your bank. A conversation almost always resolves it faster, and we would rather fix a mistake than argue about one.

Raising a dispute does not close your account, stop your project or remove anything we have already delivered. Nothing happens to your project by itself because a payment is questioned.