Guest access

Public policy draft

Refund And Cancellation Policy

How refund requests, failed payments, subscription cancellation, and access reconciliation are expected to work.

Purchase scope

Purchases may unlock a specific tour, journey, membership, or other offer shown at checkout.

Refund and cancellation handling depends on the product type, provider payment state, local order state, and entitlement state.

Refund requests

Users should contact support with the account email, support reference, order reference, and a short description of the issue.

Do not send full card numbers, passwords, private keys, or unrelated sensitive documents.

Full refunds

For a full refund, related access is normally revoked or expired after Stripe and local entitlement state reconcile.

A provider refund event alone should not be described as fully closed until local order, payment, audit, and access state are aligned.

Partial refunds

For a partial refund, access may remain active or may change depending on the support decision and product terms.

Support should record the reason, amount, access effect, and reconciliation state before treating the case as closed.

Failed or pending payments

Failed, canceled, expired, or incomplete payments do not create final protected access.

The account page or support path should show the next safe action when payment state is incomplete.

Subscription cancellation

Subscription cancellation should use the account billing path or Stripe Customer Portal when available.

Access may continue until the end of the billing period depending on subscription state and billing rules.

Reconciliation

Refund, revoke, subscription, order, payment, and entitlement state must be reconciled between Stripe and local records.

This draft must not be used to promise automatic refunds or immediate access changes before reconciliation evidence exists.

All policy pages