Policy
Terms of service
These terms describe the basic rules for using Star1Age services.
Last updated: August 30, 2026
Information transparency
Transparency note: this page does not publish a legal entity name, registration number, ICP filing number, or customer-service address. Those details are omitted until verified. The Star1Age brand name must not be treated as a substitute for legal-entity information.
The following principles apply to all accounts, API requests, generated results, and console activity.
Scope and acceptance
- These terms apply to Star1Age accounts, the API, the developer Portal, generated results, and related support surfaces.
- By creating an account or sending a request, you confirm that you can comply with these terms and any request-specific limits shown in the Portal.
Accounts and security
- Keep login methods, API keys, and recovery details confidential. You are responsible for activity made through your account until you report suspected compromise.
- Do not share production keys in client-side code, public repositories, screenshots, logs, or support messages.
Content and rights
- You retain responsibility for prompts, uploads, and the way generated results are used. Results may be similar to other users’ results and are not guaranteed to be unique.
- Review outputs for third-party rights, privacy, accuracy, and suitability before publishing or using them in a consequential context.
Availability, charges, and limits
- Model availability, pricing, rate limits, and request states are the values published by the Portal and recorded for the relevant request or order.
- We may change, suspend, or retire a model or feature when required for maintenance, capacity, safety, or provider availability.
Updates and termination
- Policies may evolve as the product grows. The latest version published on this page applies to future use of the service.
- Access may be restricted when necessary to protect the service, users, providers, or payment records.
If your account or order view provides a verified service channel, include the relevant request or order ID when using it. Otherwise, keep the identifier for future follow-up and do not send credentials to an unverified address.
Policies may evolve as the product grows. The latest version published on this page applies to future use of the service.