Operator and scope
This policy covers the website, console, API and support. The operator, privacy contact and service regions must be identified before launch. This draft is not a certification of compliance in any jurisdiction.
Categories of information
Depending on the feature, processing may involve account identifiers and contacts, login and security events, key management metadata, payment orders and status, model identifiers, timestamps, token quantities, charges, errors and local request identifiers.
Inference and troubleshooting also involve submitted prompts, files, inputs, outputs and necessary request context. Do not send support usable credentials or unrelated sensitive data. Actual payment fields must be checked against the deployed payment flow.
Purposes and necessity
Information supports accounts, inference routing, metering, order checks, troubleshooting, abuse prevention, complaints and necessary legal obligations. Collection and access should be limited to the relevant purpose.
This draft does not authorize advertising profiles, sale of personal information or training platform models on customer requests. Any new use requires prior disclosure and the applicable safeguards and choices.
24-hour request retention
Request content and troubleshooting request data are proposed to be retained for at most 24 hours, then deleted automatically. This must be verified before commercial use. The 24-hour window does not automatically apply to account, accounting or security records.
Other records should be deleted or anonymized after the periods necessary for service, disputes and applicable legal duties. Exact periods, backup deletion and lawful exceptions require confirmation and publication. No unverified zero-retention promise is made.
Security and browser storage
The service should apply transport protection, access separation, credential safeguards, audit and incident handling. Administrative access must follow job necessity. Security incidents should be investigated and notified as required; no system is risk-free.
Cookies and local storage maintain login, language, theme or preferences. Additional storage introduced by identity, payment or analytics integrations requires disclosure. The service does not make an unverified claim that no third party processes data.
Access, correction and deletion
Users may contact the published privacy channel to request access, correction, export, deletion, restrictions or other applicable rights. Reasonable identity checks may be required to protect accounts.
Legally required accounting or security records may not be immediately deletable. Delayed or declined requests should receive an explanation and an appeal path. Account closure and balance treatment are separate matters.
Children and policy updates
The service is for eligible developers and teams. Do not submit harmful content involving minors. Report suspected inappropriate collection or child-safety concerns through the official channel.
Material changes should be notified before taking effect. The published version must identify its effective date and version history. Viewing a draft is not consent to undisclosed processing.
Contact and appeals
Service operator: to be confirmed.
Official contact details have not been published. Valid support, privacy and appeal channels must be provided before launch.
Back to top