DeepSeek collects user-provided data, usage metrics, and technical information to operate its services effectively. This includes data explicitly provided by users, such as account details or input queries, as well as information generated through interactions with the platform, like API usage patterns. The collection focuses on enabling core functionality, improving performance, and ensuring security, while adhering to privacy standards.
User-provided data includes details like email addresses and usernames during account creation, API keys for integration, and input data submitted through prompts or API requests. For example, if a developer integrates DeepSeek’s API into their application, the service processes input queries and configuration settings to generate responses. Usage data encompasses metrics such as frequency of API calls, features accessed, and session duration—useful for identifying performance bottlenecks or popular endpoints. Technical data involves IP addresses, device specifications (e.g., operating system, browser type), and server logs, which help diagnose issues like API errors or latency spikes. For security, DeepSeek monitors login attempts and API usage to detect anomalies, such as sudden spikes in traffic that might indicate abuse.
DeepSeek employs encryption (e.g., TLS for data in transit, AES-256 for stored data) and access controls to protect collected data. It anonymizes or aggregates metrics where possible, such as removing personally identifiable information from error logs. The service complies with regulations like GDPR and CCPA, allowing users to request data access, deletion, or opt-out of non-essential tracking via account settings. Developers managing API integrations can audit usage logs for debugging or review rate limits. Privacy policies detail data retention periods—for instance, server logs might be stored for 30 days before anonymization. These practices aim to balance operational needs with transparency, ensuring users maintain control over their information.