Refund Policy

1. General Policy

Memix subscriptions are billed through Paddle. Refund decisions are handled in accordance with Paddle's billing systems, applicable law, and our review of the specific purchase or renewal request.

2. Requests We May Approve

We may approve refunds or credits in situations such as:

• Duplicate charges or obvious billing mistakes.
• Accidental renewals reported promptly after renewal.
• Material technical issues with a paid feature that we cannot reasonably resolve.

3. Requests We May Decline

We may decline refund requests in situations such as:

• Attempts to bypass licensing, payment, or paid-feature enforcement.
• Repeated refund requests that suggest abuse of the policy.
• Cases where the subscription remained active and usable for a substantial period before the request.

4. How to Request a Refund

To request a refund, contact support@memix.dev with the email used for purchase, your subscription ID if available, and a short explanation of the issue. Approved refunds are processed through Paddle and may take several business days to appear on your original payment method.

5. Effect on Access

If a refund is granted, the related paid subscription or license may be canceled or deactivated. Continued use of paid functionality after a refunded purchase is not permitted.

6. Open-Core Licensing Context

The public repository describes core daemon and solo-use layers as MIT-licensed, while paid team-sync components and commercial activation paths are described as BSL 1.1 licensed code that converts to Apache 2.0 after four years. A refund does not expand rights to use paid or commercially gated functionality beyond the terms that apply to those components.