Refund Policy

1. Our starting position

A SentinelX licence is a term of access to a maintained binary. Because it is delivered as a download and activates instantly, we treat activation as the point of consumption. That is the moment you begin receiving the software and any support attached to it.

2. When we refund

We will refund in these situations:

• The voucher is defective. It will not activate, or it fails validation for a reason on our side. We will fix it or replace it, and refund if we cannot.
• Duplicate purchase. You bought the same term twice, or two vouchers were issued for one order.
• Misrepresentation. We described a module as working when it is not, or in development, and you bought on that basis. This is covered by the status badges on the pricing page.
• We cannot deliver the term. For example the licence API is unavailable for an extended period and you cannot activate at all.
• Mandatory consumer law entitles you to a refund in your jurisdiction.

3. When we do not refund

We will not refund where:

• The voucher has already been activated on a node, except in the defective or misrepresentation cases above.
• Unused time has been consumed. For any refund we normally deduct a pro-rata amount for the elapsed portion of the term.
• You are revoking your own licence after reading the terms, where the term has begun.
• You were revoked for breach of the Acceptable Use Policy or the Terms.
• Three failed activations occurred. The activation lockout is a security control and repeated failures are treated as a failed delivery attempt.
• Payment was reversed. A chargeback, fraudulent card use or a refund from your payment provider withdraws the licence and is not re-refunded by us.

4. Partial refunds for a broken licence

Where a licence activates correctly but a module you paid for turns out not to work, we will either fix the module, extend your term by an equivalent period, or refund the unused proportion of the term, at your choice. We decide which remedy applies; if the defect is material and unfixable, we refund the unused proportion.

Known limitations are not defects. Modules that are described on our pricing page as partial or in development are disclosed before purchase. Buying with that disclosure in place does not entitle you to a refund for those specific limitations.

5. Licences we revoke

Where we revoke a licence for breach, refund is not offered. Where we revoke for an operational reason — for example a licence record corrupted by a database fault that is ours, or a defect in the validation service — we will offer a replacement voucher or a refund of the unused term.

Note also that a revoked licence only stops a running node at its next revalidation, up to 24 hours later, because the node validates against its local signed file in between. See the Licence Agreement.

6. How to request a refund

Use the contact form or email support@wildandev.tech, and include:

1. the voucher code(s) involved;
2. the order reference or payment receipt;
3. the node hostname and machine fingerprint prefix, so we can look up the activation record;
4. the reason, and the outcome you are asking for: replacement, term extension, or refund.

If we agree to a refund, we return the payment to the original method. Bank and card settlement typically takes five to ten business days. We do not issue cash or cryptocurrency refunds.

7. Timeframes

These targets are aspirations for service quality. They are not a guarantee of outcome and do not create a service level agreement.

8. Chargebacks

Please contact us before raising a chargeback. A chargeback reverses the payment immediately, revokes the licence without refund, and can leave your nodes unprotected at the next revalidation. Opening one where a direct request would have been resolved costs you the benefit of the refund terms above.

9. Questions

Anything not covered here, ask us before you buy: support@wildandev.tech.