TERMS OF SERVICE
This page describes the current technical service boundaries. It is a product-accurate draft and requires jurisdiction-specific legal review before production launch.
Draft status: legal review required. Last technical review: August 14, 2026.
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.
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.
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.
Purchased credit is a non-transferable, non-withdrawable service balance usable only for Tsubasa inference. A checkout redirect is not payment evidence. Credit is added only after the configured provider confirms a matching invoice or payment event. Tsubasa does not operate a wallet, exchange, or customer-to-customer transfer service.
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.
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.
The service and models are provided on an as-available basis. Outputs may be inaccurate, incomplete, or unsuitable for a particular purpose. You are responsible for review, testing, authorization, backups, and safeguards before applying generated code or actions.
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.
The current product has no automated withdrawal or exchange path. Underpayment, overpayment, late payment, duplicate payment, or a requested refund requires support review and is handled according to provider capabilities and applicable law. Do not send funds to an expired invoice without confirming its status.
Material service or policy changes will be reflected in the published terms and product documentation. Continued use after an effective change may constitute acceptance where permitted by law.