1. One-time credit purchases
Orindle offers the following one-time packages. They do not renew monthly and are not subscriptions.
| Package | One-time price | Credits |
|---|---|---|
| Creator | $19 USD | 1,900 |
| Pro | $49 USD | 4,900 |
| Studio | $99 USD | 9,900 |
Hosted Dodo checkout presents the final total and applicable taxes. Credits are granted only after a signed webhook passes purchase, product, amount, currency and fulfillment validation; returning from checkout alone grants nothing.
2. One universal wallet
Credits are designed to be used across Orindle Chat, Image Studio, Video Studio and Websites under one Orindle account. There are no separate product-specific wallets or required monthly plans in this model.
Credits are a usage unit, not cash, a bank deposit, an investment or a transferable financial product. They cannot be represented as earning interest or having a cash withdrawal value.
3. Usage value and variable deductions
One hundred credits represent $1 of customer-facing usage value. This conversion explains the usage unit; it does not make credits redeemable for cash and does not mean every operation costs the same.
Different models and operations have different metered costs. Text, images, video and website-related operations can therefore deduct different credit amounts. Public pages do not promise a fixed number of generations for any pack.
In the production system, prices and deductions must be calculated on the server using the active configuration and verified metered usage. The browser cannot authoritatively set the final deduction. Where feasible, an estimate should be shown before an operation, with actual usage recorded in the account history.
4. Additional packs, expiry and transfers
You may purchase another one-time pack when you need more credits. There is no monthly reset because these are not recurring subscription allowances.
No expiry, transfer or mixed-wallet consumption rule is implemented in this frontend. Any such production term must be decided, clearly disclosed before purchase and applied fairly in the ledger. It must not be introduced retroactively in a way that removes rights or purchased value contrary to applicable law.
5. Usage history and corrections
The planned usage history will provide a cross-product record of operations and credits used. If a technical error creates an incorrect deduction, the production support process should investigate the ledger and provider records, then apply an auditable correction where appropriate.
Provider failures, interrupted jobs and estimated-versus-actual usage require explicit reconciliation rules before launch. A failed operation should not be presented as successfully completed.
6. Consumer rights, refunds and payment disputes
Applicable statutory consumer rights, cancellation or withdrawal rights, payment dispute mechanisms and legally required remedies remain available where they apply. This policy does not claim that every purchase is final or that a refund is never possible.
Eligibility and process can depend on factors such as local law, whether digital content or services have been supplied with required consent, the amount used, technical defects and the circumstances of the request. Any discretionary refund or credit correction process must be explained separately and must not reduce mandatory rights.
If you believe a charge is unauthorized or incorrect, contact support with the purchase reference and do not include full payment details. You may also have rights through your payment provider or card issuer.
7. Changes and related terms
Changes to credit pricing or terms should be dated and communicated appropriately. They must not undermine already purchased rights contrary to law. Server-side historical price versions and ledger records should preserve the ability to explain past transactions.
Read this policy with the Terms of Use and Privacy Policy. See Pricing for the public pack comparison.