Help and refunds

My reading has not arrived

A reading is usually ready within a few hours and always within 6 hours. We email a private link from hello@numeroclaw.com; check your spam folder for that address first. If nothing has arrived after 6 hours, write to us with the email address you used and the order number from your payment confirmation. We find the reading or refund you.

Something in my reading is wrong

A wrong number, a misread name, a missing chapter: write to us within 14 days of your order and we refund the payment to the card you paid with, usually within a few business days. We refund in money, not in vouchers. A reading you simply disagree with is not a defect, but tell us anyway; it helps us.

I lost the link to my reading

Search your inbox for hello@numeroclaw.com. The delivery email holds the private link and it does not expire. If the email is gone, write to us with the address you ordered with and we send the link again.

Promo codes, payment, and receipts

Promo codes are entered on the payment page, and the discount shows before you pay. Payment is handled by Stripe, which emails the receipt. We never see your card number.

For professionals and integrators

Email hello@numeroclaw.com for account access, billing, webhook troubleshooting, and reading delivery problems in the portal or through the API.

What helps us help you (professionals)

Include the workspace ID, reading ID, approximate timestamp, endpoint URL for webhook issues, and any relevant response body or status code.

Launch posture

Support is handled directly and pragmatically during launch. Public plans do not currently include a contractual 24/7 response SLA.

If you need commercial response guarantees, contact us for an enterprise arrangement.

Typical issue types

Most launch support requests are expected to fall into four buckets: access requests, insufficient credits, webhook delivery setup, and reading status investigation.

Documentation first

Before opening a ticket, check the docs for authentication, async lifecycle, errors, and webhook signatures. Most first-run issues are integration-shape issues rather than platform outages.