Request flow and processing scope
API endpoints, routes and available log fields are confirmed when a service is provisioned. An entry route does not determine inference or all storage locations.
Data categories and retention
| Category | Handling |
|---|---|
| Accounts and sessions | Used for sign-in, session management and account security, subject to functionality, legal requirements and contracts. |
| Usage, billing and operational logs | May record time, account/key identifiers, model, tokens, charges, request ID, outcome and authorized metadata such as IP, User-Agent and entry route. |
| Web conversations, canvas and files | Depending on the feature and settings, conversations, uploads or generated results may be retained; content is not necessarily confined to the browser. |
| Request-body archives | Managed separately from usage logs and disabled when no archive policy exists. Authorized administrators can enable a policy per account with capture deadline, retention and size limits. Enabled policies may retain prompts, history and tool arguments in request bodies. |
Retention varies by data category; another platform’s retention period does not define DAYWORLD’s policy. Stopping archive capture does not immediately delete existing records. Backups and legally retained billing or security records require separate handling.
Keys and account protection
- Use HTTPS and keep API keys in server-side environment variables or a secret manager, away from public frontends, screenshots, URLs, repositories and support tickets.
- Separate development and production keys; configure model allowlists, expiry and quotas by purpose. Organization members should use keys issued by their own accounts.
- Disable or revoke a leaked key, update client configuration and inspect usage records. Where account security settings provide them, use two-factor authentication and review signed-in devices.
Provider processing and enterprise requirements
Confirm provider retention, training use and processing location against the terms for the actual channel. A DeepSeek model name, open license or entry route does not replace written confirmation of zero retention, training exclusion, residency or at-rest encryption requirements.
Applications should implement input and permission validation, appropriate content governance, output review and generated-content labeling. Design the workflow around the actual provider and enabled capabilities rather than assuming a single automatic moderation system covers every model.
Related rules: DAYWORLD service terms, privacy policy and data processing information. For verification or enterprise documentation, contact the operator.
Access, correction and deletion requests
For access, correction, export or deletion, contact support with the account, data category and date range. Requests are handled subject to identity checks, applicable law and effective agreements. Do not include passwords, full API keys or unnecessary raw prompts.
Related rules: DAYWORLD service terms, privacy policy and data processing information. For verification or enterprise documentation, contact the operator.