1. Eligibility and authority
You must be at least 18, have legal capacity to use the service, and have authority to bind the organization whose account you use. You must provide accurate account and billing information available through the approved sign-in and payment flows. Tsubasa does not currently require ordinary customers to submit government identity documents, but may require information needed by law, sanctions controls, fraud review, or a payment provider.
2. Service scope
Tsubasa provides access to the API surfaces and models shown as available in the current environment. Model availability, latency, output, and behavior may change. A compatibility label applies only to the interface and evidence described on its integration page.
3. Accounts and credentials
You are responsible for account activity and for keeping API keys confidential. Create separate keys for separate applications, revoke a key you believe is exposed, and do not share a dashboard session as an API credential.
4. Acceptable use
You must comply with the Acceptable Use Policy, applicable law, and authorization boundaries. Reduced-refusal model behavior does not authorize illegal activity, infrastructure abuse, credential theft, fraud, malicious software operations, targeted harm, or prohibited content.
5. Customer content and confidential information
You retain your rights in content you submit and grant Tsubasa only the rights needed to process it and operate the service. You must have authority to submit the content. Do not submit regulated or safety-critical data unless a separate written agreement expressly approves that use. Provider and subprocessor boundaries are described in the Privacy Policy.
6. Prepaid service credit
Purchased credit is a non-transferable, non-withdrawable service balance usable only for Tsubasa inference. Card purchases use Stripe; Bitcoin checkout is not available in this rollout. Prices and balances are in US dollars. A checkout redirect is not payment evidence. Credit is added only after Tsubasa verifies the matching provider payment. Purchase and balance limits apply. Purchased credit does not expire while the account remains in good standing. Tsubasa does not operate a wallet, exchange, or customer-to-customer transfer service.
7. Automatic reload
Automatic reload is optional. When you enable it, you authorize Tsubasa to initiate an unscheduled off-session charge to your selected saved card each time your available credit falls strictly below your chosen threshold. Each charge uses your chosen reload amount and will not start if it would exceed your chosen UTC calendar month maximum. This is not a subscription. You can disable future reloads from Billing at any time without losing access to one-time purchases. A payment already processing with Stripe might still complete and receive matching credit. A decline or required cardholder action pauses automatic reload until you update the card and enable it again.
8. Request accounting
An admitted request may reserve its worst-case cost before inference and settle against terminal billable usage. A cancelled or failed stream may still incur charges for work already performed. Usage records contain operational metadata rather than prompt or response bodies.
9. Privacy and infrastructure
The Tsubasa application does not intentionally persist prompt, completion, source-code, repository, patch, or tool-call bodies. Request content must still be processed by the application runtime and configured inference infrastructure. Operational, security, account, payment, and ledger records are retained as described in the Privacy page.
10. Output review and high-risk use
Outputs may be inaccurate, insecure, incomplete, or subject to third-party rights. You are responsible for human review, testing, authorization, backups, security checks, and licence review before deployment. The service is not approved for medical, legal, financial, employment, credit, law-enforcement, weapons, critical-infrastructure, life-safety, or other safety-critical decisions unless a separate signed agreement expressly permits the use.
11. Intellectual-property complaints
Report a claim with the affected output or identifier, the asserted right, your authority, and safe contact information. Do not send credentials or unrelated customer content. Tsubasa may restrict the affected model or account while reviewing a credible claim. Self-service access does not include an additional output indemnity or a negotiated service-level commitment.
12. Suspension and termination
Tsubasa may limit or suspend access to protect the service, respond to nonpayment or security risk, enforce policy, comply with law, or meet binding infrastructure-provider requirements. Revoked API keys stop working on the next validation.
13. Refunds and billing concerns
You may request a refund of unused purchased credit within 14 days of purchase by contacting [email protected]. Include the purchase or request identifier and a concise description, without card numbers, API keys, prompts, or unrelated customer content. An approved refund returns through the original payment method. This does not remove a refund or other remedy required by applicable law. Refund and dispute events create separate ledger adjustments; they do not rewrite the original purchase. If the matching spendable credit is no longer available, Tsubasa may suspend access while the adjustment is reviewed.
14. Reliability, mandatory rights, and disputes
Tsubasa does not promise uninterrupted service, error-free outputs, or suitability for a particular high-risk decision. Nothing in these terms excludes rights or remedies that cannot lawfully be excluded. These terms do not impose mandatory arbitration or an exclusive court. A dispute may be brought before a court with jurisdiction. Contact [email protected] with a concern so the operator can investigate it.
15. Changes
Material service or policy changes will be identified in the published documents. When the application requires renewed acceptance, API access remains restricted until the account accepts the current versions. Continued use after an effective change may constitute acceptance where permitted by law.