Transparency & security
Understand the current service boundaries and data controls.
One account
DarkSeek uses one account authority across chat and the developer platform. Account-owned API keys are revocable. A valid web session or key never permits access to another account’s saved records.
Conversation and file data
Unsaved web conversations stay in the active tab. Saving history is an explicit action and can include reasoning. Stored files, when enabled, require private ownership checks, admission quotas, retention and physical deletion. Storage does not imply training, indexing or model interpretation.
Availability and financial terms
Public registration, payment settlement and token-based billing are not generally enabled. Technical admitted-request limits are not money. No paid entitlement, tax rate, service guarantee or refund promise is implied by an interface preview.
Independent service
DarkSeek is independently operated. Upstream model documentation, announcements and research are credited as reference material, not claimed as original DarkSeek releases. Final commercial/legal policies and security-reporting channels must be published before commercial launch.