Refund & Cancellation Policy

1. Scope

This Policy applies to:

• Miglify subscription plans;
• recurring subscription renewals;
• migration allowances and paid usage entitlements;
• Connection protection and monitoring services;
• Enterprise or custom plans, unless a signed order form states different terms; and
• other paid digital services expressly identified as being governed by this Policy.

Free plans and free allowances have no cash value and are not eligible for monetary refunds.

2. Subscription Activation and Service Commencement

Paid subscription access normally begins as soon as payment authorization is confirmed by our payment provider.

Once activated, Miglify may immediately make paid functionality available, reserve migration capacity, perform validation, process project metadata, initiate migrations, create destination resources, deploy supported components or provide Connection protection.

By starting a migration or using a paid feature after purchase, you request immediate performance of the digital service.

3. Automatic Renewal

Unless checkout or an applicable order form states otherwise, paid subscriptions renew automatically at the billing interval displayed when purchased.

By subscribing, you authorize Miglify and its payment provider to charge the applicable recurring fee, together with applicable taxes, until the subscription is cancelled.

Renewal pricing and billing frequency are displayed before purchase. If we materially change the subscription price, we will provide notice where required by applicable law before the new price takes effect.

You are responsible for keeping your billing details and payment authorization current.

4. How to Cancel

You may cancel an automatically renewing subscription at any time through the cancellation controls available in your Miglify account, through the applicable payment provider where supported, or by contacting Miglify through the support method published on our website.

A cancellation request must be submitted before the next renewal charge is processed. Cancelling after a renewal has already been processed does not automatically reverse that charge.

We may require reasonable account or transaction information to verify that a cancellation request was made by the account owner or an authorized representative.

5. Effect of Cancellation

Unless otherwise required by law or stated during cancellation:

• cancellation stops future automatic renewals;
• your paid plan normally remains active until the end of the current paid billing period;
• cancellation does not automatically produce a refund for the current period;
• unused subscription time, migration allowances or features do not carry cash value;
• unused allowances normally expire when the applicable billing period or subscription ends;
• your account may move to the Free plan after the paid period ends;
• features that require an active paid plan may become unavailable, paused or restricted; and
• Connection protection, monitoring, repair eligibility or other ongoing services may stop or become limited when the paid period ends.

Cancelling Miglify does not cancel, delete or refund third-party services such as Supabase, GitHub, Lovable, PayPal, hosting services, domains or cloud resources. You remain responsible for managing those services and any charges imposed by their providers.

Cancellation does not reverse a completed migration or automatically restore the source application to its previous state.

6. General Refund Rule

Except where this Policy or applicable law provides otherwise, subscription and digital-service payments are non-refundable after:

• a migration has been started;
• a paid migration or usage entitlement has been consumed;
• a paid Connection feature has been activated or used;
• Miglify has committed computing, deployment or operational resources;
• the customer has received the substantial benefit of the paid service; or
• the applicable refund-request period has expired.

We do not provide automatic prorated refunds merely because an account is cancelled before the end of a billing period.

This rule does not remove any remedy that must be provided for a defective, misdescribed or unlawfully supplied service under applicable law.

7. Initial-Purchase Refund Requests

For a customer’s first purchase of a paid Miglify subscription, we may approve a refund request submitted within seven calendar days after the original purchase only when:

• no migration has been started;
• no paid migration allowance has been consumed;
• no paid Connection protection or repair feature has been used;
• no substantial paid service has otherwise been provided; and
• the account is not associated with abuse, fraud, repeated refund requests or an earlier refunded account.

This seven-day provision is a contractual eligibility window and does not reduce any longer mandatory cancellation or refund right that may apply under applicable law.

8. Renewal-Charge Refund Requests

A renewal payment may be eligible for review when:

• the request is received within seven calendar days after the renewal;
• no migration or other paid entitlement from the renewed period has been used;
• no paid Connection protection or repair operation was performed during the renewed period; and
• the renewal was not already subject to a prior refund, dispute or chargeback.

A renewal refund is not guaranteed merely because the customer forgot to cancel. Each request will be assessed using account activity, payment history and applicable law.

If a refund is approved for a renewal, paid access may end immediately rather than continuing until the end of the renewed period.

9. Billing Errors, Duplicate Charges and Unauthorized Payments

Please contact us promptly if you believe that:

• you were charged more than once for the same purchase;
• the charged amount differs from the confirmed checkout amount;
• a cancelled subscription renewed because of a Miglify billing error; or
• a payment was not authorized by the account or payment-method owner.

Confirmed duplicate charges and billing errors will be corrected.

Unauthorized-payment reports may require cooperation with the payment provider and reasonable identity or transaction verification. Nothing in this section restricts any lawful right to report an unauthorized transaction directly to the payment provider or financial institution.

To help us investigate efficiently, billing issues should normally be reported within 30 days after the charge is shown. This reporting period does not override a longer period required by law.

10. Failed, Cancelled or Interrupted Migrations

A migration can depend on customer credentials, source-project availability, destination-project availability, third-party APIs, network conditions, database compatibility, project configuration and customer compliance with the migration instructions.

A failed or cancelled migration does not automatically entitle the customer to a cash refund.

Where Miglify’s usage rules provide that only successfully completed migrations count against a monthly migration allowance, a failed or cancelled migration will be handled according to those usage rules and may remain eligible for retry.

If a migration fails, Miglify may provide one or more of the following remedies, depending on the circumstances:

• retry or resume capability;
• technical investigation;
• correction of a Miglify platform fault;
• restoration or rollback where supported;
• replacement migration capacity;
• account credit;
• partial refund; or
• full refund where required by law or appropriate because Miglify could not provide the purchased service.

The remedy will depend on the cause, the work already performed, the resulting destination state, account history and applicable law.

11. Circumstances Normally Not Eligible for Refund

Unless required by law, refunds will normally not be provided when the issue results from:

• changing your mind after beginning or receiving the service;
• forgetting to cancel before renewal;
• not using available subscription time or allowances;
• incorrect, expired, revoked or insufficient customer credentials;
• inaccurate information supplied by the customer;
• source or destination projects that are paused, deleted, inaccessible or misconfigured;
• unsupported source customizations or incompatibilities disclosed by Miglify;
• customer changes made during a required source-write freeze;
• failure to follow migration, cutover, verification or publishing instructions;
• outages, restrictions or policy changes affecting third-party platforms;
• GitHub, Supabase, Lovable, PayPal, hosting-provider or internet-service failures outside Miglify’s reasonable control;
• deletion or modification of migrated resources by the customer or a third party;
• dissatisfaction with a result that materially matches the disclosed migration scope;
• suspension or termination resulting from fraud, abuse, security threats or a material breach of the Terms of Service; or
• currency-conversion costs or payment-provider fees that Miglify did not receive.

This section remains subject to mandatory legal rights and does not excuse Miglify from responsibility for its own failure to provide the purchased service with legally required care and conformity.

12. Service Unavailability or Miglify Failure

If a paid service cannot be provided because of a verified Miglify platform failure, we will first make reasonable efforts to restore, repeat or correct the service.

If correction is not reasonably possible, an appropriate remedy may include replacement service, account credit, a prorated refund or a full refund, depending on:

• the affected service;
• the duration and severity of the failure;
• whether the customer received usable value;
• whether the service can be repeated;
• the amount paid; and
• applicable law.

Scheduled maintenance, announced service windows and short interruptions that do not materially prevent use will not normally qualify for a refund.

13. Enterprise and Custom Agreements

Enterprise plans, custom migration services and negotiated arrangements may be governed by an order form, statement of work or separate written agreement.

If a valid signed agreement directly conflicts with this Policy, the signed agreement controls for the conflicting subject.

Setup charges, professional services and custom work may be non-refundable once work begins, except where the applicable agreement or law states otherwise.

14. Suspension or Termination by Miglify

We may suspend or terminate access as permitted by our Terms of Service, including for non-payment, fraud, abuse, unlawful activity, security threats or material breach.

If we terminate a paid service for convenience and not because of customer breach, fraud, legal requirement or security risk, we will provide any refund or credit required by applicable law and may provide a prorated refund for the unused paid period.

Where termination results from customer breach, fraud, abuse or unlawful activity, fees already paid will normally remain non-refundable to the extent permitted by law.

15. How to Request a Refund

Submit a refund request using the support method published on the Miglify website.

Include:

• the email address associated with the Miglify account;
• the transaction or invoice identifier;
• the charge date and amount;
• the affected subscription or service;
• a clear explanation of the request; and
• any relevant screenshots or error references.

Do not send passwords, private keys, database passwords, service-role keys, access tokens or other confidential credentials in a refund request.

We may request additional non-secret information necessary to verify the account, payment or service history.

16. Refund Processing

If approved:

• the refund will normally be returned to the original payment method;
• we will submit the refund to the payment provider within 10 business days after approval;
• the payment provider or financial institution may require additional processing time;
• exchange-rate differences, bank fees or payment-provider charges outside Miglify’s control may affect the final amount received; and
• related paid access, allowances or account credits may be removed when the refund is issued.

Receiving a refund does not require Miglify to delete migration records that must be retained for security, fraud prevention, accounting, legal compliance or dispute resolution. Personal data remains governed by our Privacy Policy.

17. Chargebacks and Payment Disputes

We encourage customers to contact Miglify before initiating a chargeback so that we can investigate billing errors or service problems.

A chargeback or payment dispute may cause the affected subscription or account to be temporarily restricted while the matter is investigated.

Fraudulent, abusive or duplicate disputes may result in suspension or termination. Nothing in this section removes any lawful right to challenge an unauthorized or incorrect charge.

18. Taxes

Prices may exclude or include taxes depending on what is displayed during checkout and what applicable law requires.

Taxes will be refunded only when required by law or when they relate to a refundable charge and the applicable tax treatment permits reimbursement.

19. Changes to This Policy

We may update this Policy to reflect changes to our services, billing practices or legal obligations.

The revised version will display a new “Last updated” date. Material changes will be communicated where required by law.

Changes will not unlawfully remove rights that already apply to an existing valid refund claim. Continued purchase or renewal after the effective date of an updated Policy constitutes acceptance to the extent permitted by law.

20. Contact

For cancellation, billing or refund assistance, contact Miglify through the support email address or contact method published on our website.

Please never include passwords, database credentials, API keys, service-role keys or access tokens in a support message.