Billing
Billing Policy
This billing policy sets expectations for the early paid web product, including one-time token packs, recurring subscription posture, renewal handling, and how billing-related access decisions are treated.
Effective date: March 29, 2026
Purchase posture
Paid access is expected to run through one-time token packs and a recurring subscription once the Stripe-backed flow is enabled. Token amounts, pricing, and renewal timing should be shown clearly before a customer starts a purchase.
If pricing or tier structure changes later, those changes should be presented deliberately rather than hidden behind vague copy or vague upgrade language.
Renewals, cancellations, and failed payments
Subscription access may renew automatically until canceled, and one-time token purchases should not imply a recurring charge. Failed payments, chargebacks, or billing integrity concerns can result in downgraded or suspended paid access until the account is resolved.
Cancellation and renewal state should remain visible to the user once billing is active, even while the product is still in its early commercial phase.
Refund and support posture
Refund handling may depend on applicable law, platform rules, the type of purchase involved, and the specific account situation. Requests should be reviewed through support rather than assumed automatically.
This policy page exists so pricing and onboarding surfaces can point to a real billing posture instead of implying one.