I. Core Commitment: No Storing of API Call Content
To avoid misunderstanding, onetoken explicitly states the following:- We will not store prompts, questions, instructions, system prompts, context, conversation history, code snippets, file text, business data, or other request content submitted through our API.
- We will not store the answers, code, analysis results, generated content, context results, or other response content returned to you by our models.
- We will not use your API call content to train onetoken’s proprietary models, nor will we proactively provide your API call content to any third party for model training.
- We will not save or reuse customers’ API call content as a knowledge base, sample library, case library, dataset, or operational analysis material.
- We will not proactively and manually review your API call content unless required by laws and regulations, regulatory authorities, or judicial authorities, or if you explicitly request our assistance in investigating specific issues and providing relevant content separately.
II. Processing of API Call Content
In the normal service flow, API call content is only used to complete the current request you initiated:- Receive your API request;
- Forward the request to the appropriate model or service provider according to your selection or system routing rules;
- Receive the result returned by the model or service provider;
- Return the result to you.
III. Necessary Service Records We Will Retain
To provide API relay, billing, quota statistics, security risk control, fault diagnosis, and compliant operation, onetoken needs to retain necessary service records. These records generally do not include API call content. We may retain the following information:- Account and Organization Information: Account identifier, login name, email or mobile phone number, organization name, account role, permission configuration, authentication status, API Key identifier and its status. The original API Key will be encrypted, hashed, or processed using other security measures.
- Order and Billing Information: Order records, recharge records, balance, package, quota, consumption amount, invoice information, payment status, contract or settlement information.
- Call Metadata Logs: Request time, request ID, account ID, organization ID, API Key identifier, interface path, model name or model type, token usage, billing amount, response status, error code, latency, call source IP, User-Agent, and frequency limit records.
- Security and Risk Control Logs: Login records, abnormal logins, abnormal calls, key risks, frequency anomalies, attack interception, abuse risks, permission changes, system alarms, and security incident handling records.
- Work Orders and Service Communication Records: Issues, screenshots, documents, explanations, and processing records that you proactively submitted through platform work orders, account backend, or other official channels.
IV. Content Not Included in Logs
Unless you submit a separate work order or there is a separate written agreement between both parties, onetoken’s regular call logs will not record the following:- Prompts, user questions, system prompts, context, or dialogue history;
- Model output body, generated code, generated text, or response content;
- Source code, configuration files, business documents, customer information, or file body that you submit;
- Content of images, audio, video, and parsed documents;
- Request body content that can directly reveal your business intent, business logic, customer data, or trade secrets.
V. Third-Party Model and Service Providers
As an API relay and model routing service, onetoken may forward requests to appropriate model, computing power, cloud service, or technical service providers based on your selection, platform configuration, model availability, price, stability, or compliance requirements. Please understand the following:- OneToken does not store API call content, but this does not mean that third-party models or service providers do not process related content at all. Third parties may process request content in their service processes to complete model inference and response generation.
- Different model vendors may have different data processing rules, logging rules, content security rules, geographic rules, and training rules. You should choose the appropriate model based on your business, data types, customer commitments, and regulatory requirements.
- When targeting business, users, or data processing scenarios within China, you should ensure that the selected model, vendor, calling region, and usage method comply with relevant Chinese laws and regulations, industry regulations, data security, personal information protection, algorithm governance, generative artificial intelligence, and deep synthesis requirements.
- If you require the use of models only within China, specifying vendors, disabling certain models, dedicated gateways, private deployment, log isolation, a commitment not to persist content to disk, or a separate data processing agreement, you should separately confirm this in writing with OneToken before use.
VI. Content You Should Not Submit
Even though onetoken does not store API call content, you should still use this service with caution and avoid submitting the following:- State secrets, work secrets, important data, or data that is legally restricted from processing, transmission, or export;
- Unauthorized personal information, sensitive personal information, original customer data, identity information, account passwords, keys, bank card information, medical and health information, or information about minors;
- Trade secrets, core code, unpublished financial data, unreleased product information, confidentiality agreements, source code repository content, or other highly sensitive business information;
- Any content that you are not authorized to upload, process, forward, or provide to third-party model services;
- Any content that may violate laws and regulations, regulatory requirements, contractual obligations, confidentiality obligations, or the rights of third parties.
VII. How We Use Necessary Service Records
OneToken uses account information, billing information, call metadata, and security logs only to the extent necessary for the following purposes:- Creating, verifying, managing, and protecting accounts;
- Completing API relay, model routing, quota statistics, billing settlement, order management, and invoice processing;
- Monitoring service availability, troubleshooting interface failures, locating abnormal requests, and optimizing gateway performance;
- Preventing fraud, abuse, malicious calls, attacks, unauthorized access, and account risks;
- Complying with laws, regulations, regulatory requirements, and legally mandated requirements from judicial or administrative authorities;
- Handling disputes, auditing bills, verifying call volume, and protecting the legitimate rights and interests of OneToken, customers, and third parties.
VIII. Information Sharing and Disclosure
OneToken does not sell your personal information, account information, call records, or business data. We may share or disclose limited information in the following necessary circumstances:- Necessary for Service Completion: Providing limited information necessary to complete services to model providers, cloud service providers, network service providers, payment institutions, SMS or email service providers, risk control service providers, ticketing systems, etc.
- Internal Organizational Management: Disclosing management information such as accounts, limits, orders, call volume, fees, and security incidents to authorized administrators, depending on your organization’s administrator settings and permissions.
- Legal Compliance: Disclosing information as required by laws and regulations, regulatory authorities, judicial authorities, administrative authorities, or other competent authorities.
- Protecting Legitimate Rights and Interests: Disclosing risk information to relevant parties to the extent necessary to prevent fraud, attacks, theft, illegal activities, system abuse, or security incidents.
- Business Changes: In the event of a merger, division, acquisition, asset transfer, reorganization, or similar transaction, necessary information may be transferred in accordance with the law, but the transferee shall continue to be bound by this policy or arrangements with a level of protection no less stringent than this policy.
IX. Data Security Measures
OneToken will adopt technical and organizational measures commensurate with the nature of its API relay service to protect information security, including but not limited to:- Protecting transmission security using TLS/SSL and other methods;
- Implementing access control for accounts, API keys, permissions, backend access, and sensitive configurations;
- Avoiding logging request and response bodies in regular logs;
- Encrypting, de-identifying, isolating permissions, or minimizing necessary logs and configurations;
- Monitoring abnormal logins, abnormal calls, attacks, abuse, and system risks;
- Establishing necessary backup, auditing, emergency response, and security incident handling mechanisms.
X. Data Retention and Deletion
- API call content is not treated as a regular OneToken storage object and will not be persistently saved by OneToken under normal circumstances. 2. Account information, order information, billing records, call metadata logs, security logs, and ticket records will be retained for a reasonable period necessary to achieve the purposes described in this policy and are subject to legal and regulatory requirements, accounting and auditing requirements, dispute resolution requirements, security risk control requirements, and contract performance requirements.
- When relevant information no longer needs to be retained, or when you legally request deletion and there is no legal or reasonable reason for retention, we will delete, anonymize, or take other reasonable measures.
- Upon account cancellation, service termination, or contract expiration, we may still retain necessary records for the period necessary for legal and regulatory compliance, auditing, dispute resolution, security logging, and backup cleanup, but we will not retain your API call content.
XI. Cookies and Website Technology
onetoken may use cookies, local storage, log identifiers, and similar technologies for maintaining login state, security verification, preference settings, access statistics, troubleshooting, and service optimization. You can manage or delete cookies through your browser settings, but disabling these technologies may affect website login, account security, or the use of some functions.XII. Enterprise Users and Individual Users
- This service is only available to enterprise and organizational clients, and is not intended for personal use by natural persons, consumers, or minors.
- If you register, recharge, or use this service as an individual, you acknowledge that this action is solely on behalf of your affiliated or authorized organization, and that you have obtained legal authorization from that organization.
- Unauthorized personal use, illegal use, unauthorized access, sub-providing of the service, or provision of services to third parties constitutes a violation of this policy and the Terms of Service. Any legal liabilities, regulatory liabilities, tort liabilities, contractual liabilities, data security liabilities, costs, and losses arising therefrom shall be borne by the actual user and the relevant responsible parties.
XIII. Your Rights
Within the scope permitted by laws and regulations, you may use the functions or channels provided by the platform to:- Inquire about, correct, or supplement account information and organizational data;
- View orders, balances, limits, bills, and call statistics;
- Manage account permissions, API keys, applications, callback addresses, and security settings;
- Request the deletion, cancellation, or restriction of processing of related account information;
- Consult, complain, or raise objections regarding personal information processing rules.