Sixxie

Pricing

Preview first. Pay only after the result feels right.

Sixxie does not ask for payment before a user understands the preview standard. Checkout is placed after approval, not before the first upload, and the final price is visible before payment.

Create a preview View hosted checkout flow

Preview first

Create a first preview before checkout. This is where you decide whether Sixxie can capture the pet's shape, posture, and feeling.

  • No payment before preview approval.
  • Photos and habit notes can be adjusted before generation.
  • Checkout appears only when the preview path is clear.

What payment covers

The paid package covers the approved desktop pet build, packaging, desktop installation access, and future deletion controls.

  • Generated desktop pet package after user approval.
  • Access to installation and account recovery surfaces.
  • Privacy and deletion controls for uploaded materials.

Checkout after approval

Payment information belongs after the user has reviewed whether the pet feels familiar, comfortable, and worth keeping. Hosted checkout is handled by Stripe through a server-created session.

  • No charge before preview confirmation.
  • Hosted checkout is created by the server, not by client-side price logic.
  • No pressure discount timers.
  • Refund rules should be visible before payment is collected.

Revision support

If the result feels off, the user should be able to request changes for color, posture, expression, tail, or motion.

  • Revision scope should be shown before checkout.
  • Major photo-quality failures should be explained clearly.
  • Refund and retry rules belong near payment.

Refund and cancellation

Users can request support when payment succeeds but access is missing, when the approved package cannot be delivered, or when the preview quality does not match the stated standard.

  • Subscription cancellation stops future renewals.
  • Refund requests are reviewed against the published refund policy.
  • Support should not ask for raw private pet photos unless the user chooses to resend materials for a failed generation investigation.

Beta availability

Mac beta access is invite-based until the distribution build is notarized, the real cloud API is live, and the end-to-end generation path passes release checks.

  • Do not download internal or unnotarized builds from unofficial links.
  • Use the installation page for the current public build status.
  • Support can verify entitlement status without receiving raw photos.