Privacy Policy

Scope

This policy covers DeepSeekAgent.io accounts, previously issued API keys and feedback features. We operate independently and are not affiliated with DeepSeek. New free API key claims have ended; previously issued keys belong to our own DeepSeek-compatible API service.

Account and login data

For email registration, we process your email and password and store a generated username, password hash, registration time, verification status and account status. Passwords are stored as bcrypt hashes, not plaintext. Email verification and password reset use expiring tokens whose hashes are stored in the database. If you choose Google sign-in, we process the email, verification information and account identifier returned by Google to create or link your account; we do not receive your Google password. We also record recent login and activity times and login dates for account and service administration.

API keys and quotas

New free API key claims ended on September 21, 2026. Existing users can still view previously issued keys in their account, with their original quotas and expiry unchanged. We retain the account-to-token association, claim status, quota and issue time to retrieve and support existing keys. Previously submitted credit reservations and purchase-interest records may include the account, email, requested quota, notes and language; the retention and deletion-request provisions below apply to these records.

API request content

When you use a previously issued key with our API endpoint, prompts, messages, file content or other data you send are processed by the API service and the relevant model provider to generate responses. Your client and actions determine what is sent. Avoid sending unnecessary passwords, keys or sensitive personal information. For details of upstream request logging, data retention or model-training settings, contact us for confirmation before submitting sensitive content.

Feedback and security records

For desktop feedback, we store the message, platform, app version, language and any email you voluntarily provide. When you contact us, we process information in your email to respond and investigate. To limit abuse, the service processes request IP addresses and uses hashes of them, or hashes combined with account identifiers, in relevant rate-limit or feedback records. Servers and network services may also generate request and error logs.

Cookies and browser storage

Login uses an HttpOnly session cookie with a default lifetime of 30 days; signing out clears it. Language preferences are stored in localStorage and a language cookie. When Google Analytics is configured, we load its scripts to measure page visits, referral sources and device or browser information; it may use analytics cookies. You can clear or restrict cookies and local storage and block analytics scripts through your browser. Blocking the login cookie affects account features.

Service providers and external links

We use hosting, database and network services to operate the site, Resend for verification and password-reset emails, Google identity services when you choose Google sign-in, Google Analytics when enabled, and API management and model services for API functionality. These services process data needed for their functions and may process it outside your location. External sites such as GitHub and the official DeepSeek platform have their own privacy policies.

Retention, security and requests

Account and business records support ongoing account, quota and support services; there is currently no single automatic deletion period for all records. Rate-limit records expire and are cleaned up according to their windows. You can email us to request access, correction or deletion of your information, or to stop non-essential emails. We will verify account ownership and explain what can be processed. Some records may need to be retained for security investigations, disputes or applicable legal requirements.

Contact and updates

Send privacy questions and data requests to the email below. Changes to this policy will appear on this page with the actual modification date.

[email protected]