Refund Policy

1. Merchant of record

Runtime Guard subscriptions are sold through Paddle, acting as merchant of record.

Paddle handles payment collection, taxes, receipts, refund processing, chargebacks, buyer payment support, and checkout-related buyer communications through its own systems.

Runtime Guard remains responsible for providing the Runtime Guard software service described on the website, pricing page, Terms and Conditions, order form, or written agreement.

2. Launch customer category

Paid Runtime Guard subscriptions are initially offered for professional, business, institutional, DAO, protocol, treasury, and organizational use.

Runtime Guard does not currently make paid subscriptions available to French or EU consumers acting solely for personal, family, or household purposes unless a plan, checkout flow, or written agreement expressly states that consumer purchase is available.

3. Cancellation

Customers may cancel a paid subscription through the Paddle checkout, Paddle buyer portal, Runtime Guard application, or Runtime Guard support where available.

Unless otherwise stated at checkout or required by applicable law:

• cancellation stops future renewals;
• access normally continues until the end of the paid billing period;
• cancellation does not automatically create a refund for the current billing period;
• unpaid, chargebacked, fraudulent, abusive, or materially breaching accounts may be suspended earlier under the Terms and Conditions.

4. Refund requests

Refund requests are reviewed case by case.

Refunds may be granted where:

• required by applicable law;
• Paddle determines that a refund is required under Paddle's buyer terms or refund policy;
• duplicate billing occurred;
• a billing error occurred;
• the paid service was not made available as described;
• Runtime Guard and Paddle agree that a refund is appropriate in the circumstances.

Unless required by law or approved by Paddle, Runtime Guard does not promise refunds for:

• unused time in a billing period;
• forgetting to cancel before renewal;
• lack of use after access was made available;
• changes in the user's Safe, wallet, organization, DeFi strategy, or operational needs;
• failure to maintain required Safe configuration, browser, wallet, network, or third-party service access;
• dissatisfaction with a non-guaranteed security verdict where the service was provided as described.

5. Consumer withdrawal rights

Where mandatory consumer withdrawal rights apply, Paddle's buyer checkout, buyer terms, refund policy, and buyer support process are the primary route for exercising those rights.

In the European Union and similar jurisdictions, consumers may have a statutory withdrawal right for distance contracts. If a digital service has started during the withdrawal period at the buyer's request, applicable law and Paddle's buyer terms may allow a full refund, partial refund, or pro rata retention depending on the circumstances and buyer consents collected at checkout.

Nothing in this Refund Policy limits mandatory consumer rights where they apply.

6. Payment disputes and chargebacks

If a chargeback, payment dispute, suspected fraud, or payment abuse occurs, Runtime Guard and Paddle may investigate and may suspend paid access while the issue is pending.

Do not send refund payments directly to Runtime Guard if Paddle was merchant of record for the transaction. Paddle must process refund flows for Paddle transactions.

7. How to request a refund

Use the buyer support or manage-subscription link provided by Paddle in the purchase receipt where available.

You may also contact Runtime Guard at contact@runtime-guard.io. Runtime Guard may redirect you to Paddle where Paddle is the merchant of record or where Paddle needs to process the refund.

8. Relationship with other terms

This Refund Policy applies alongside Runtime Guard's Terms and Conditions, the pricing page, any order form or written agreement, and Paddle's applicable buyer terms and refund policy.