Data & privacy

This notice explains how NekoCloud API processes account, API usage and operational data when providing its services. It does not replace the privacy policies of upstream model providers or third-party moderation services.

Do not include unnecessary passwords, API keys, private keys, identity documents or other highly sensitive information in requests.

1. Purposes of processing

We process relevant data as needed to provide the service, primarily for:

• Account sign-in, identity verification and service authorization;
• Request forwarding, usage statistics, billing and reconciliation;
• Troubleshooting, maintenance and data recovery;
• Content safety screening, abuse prevention and security investigations;
• Handling inquiries and complaints, and fulfilling necessary legal obligations.

2. Forwarding request content

To fulfill model calls, prompts, conversation context, images and other inputs are forwarded to the upstream service corresponding to the selected model.

When content safety screening is enabled, content being screened may also be sent to an external moderation service. Upstream model and moderation services process received content under their own policies.

We therefore do not promise that request content is never sent to third parties or that there is zero retention throughout the processing chain.

3. Data that may be retained

Account and service data

This includes account identifiers, necessary contact information, account status, and records of balances, top-ups, redemptions and subscriptions, for account administration, service delivery and reconciliation.

Request and usage records

This includes request times, models, usage, costs, durations, request identifiers and necessary client information, for displaying usage history, billing and troubleshooting.

Ordinary usage records differ from full conversation records. This does not mean that request content is never retained at any processing stage.

Error and safety screening records

Failed requests may leave error information or upstream error responses. Content safety screening may retain screening results and necessary content excerpts. The actual scope depends on the relevant features and configuration.

Operational backups

Relevant databases, logs and service data may be included in operational backups to support recovery.

4. Retention and cleanup

Different types of data may have different retention periods based on service delivery, billing reconciliation, security and recovery needs.

Actual retention and cleanup depend on the relevant systems' retention settings, cleanup tasks and backup rotation mechanisms. This notice does not promise a single fixed retention period for all data, or immediate removal of every copy after a deletion request.

Data relating to unfinished transactions, billing disputes, security incidents or legal requirements may need to be retained. Historical backup copies may follow a different cleanup cycle from live data.

5. Access and security

We manage data access permissions according to the operational needs of service delivery, maintenance and security handling.

Authorized personnel may need to access relevant records to verify billing, troubleshoot failures, investigate security incidents or fulfill necessary obligations. We will not ask users to provide complete API keys, passwords or private keys in public group chats or support tickets.

Users should also protect their accounts and keys. Before entering a key into a third-party workspace, plugin or website, assess its trustworthiness. Third-party tools may process or retain data provided to them under their own policies and implementations.

6. Access, correction and deletion requests

To ask about processing of your data, request a correction or request deletion, contact:

admin@nekocloud.vip

To verify identity and locate the relevant data, we may need account email addresses, request time ranges, request IDs and other necessary information. Do not send passwords, complete API keys or unrelated full conversations.

We will assess requests based on their scope, identity verification, technical conditions and necessary retention requirements, and explain the scope and limitations of available handling.

Please note:

• Deleting an API key does not delete historical usage or billing records;
• Deleting live data does not immediately remove historical copies in backups;
• A request to us does not replace requests that users may need to make to upstream services or third-party tools.

7. Updates

This notice may be updated when data processing practices or related rules change. Refer to the latest notice published on this page.

See the main site's Terms of Service and Usage Policy for usage requirements.