Data processing information

Scope of this public website

This website publishes service information, documentation and model disclosures. Briefs are generated locally in the browser. This deployment provides no account registration, payments, inference or business database. Website requests may generate server access logs. Account, API, conversation and archive descriptions apply only to separately provisioned services.

Roles and responsibilities

When an enterprise entrusts DAYWORLD with business data, both parties determine their processing roles, purposes, scope, and responsibilities according to the service, and document them where needed. Account and platform-operation information is covered by the privacy policy.

Data scope and purposes

• Model inputs, outputs, and related files
• Account or team contact information and login sessions
• Request times, models, usage, charges, and incident records

Specific categories and purposes depend on enabled features and service terms, to provide, protect, and support the service.

Service providers

Providers involved in processing depend on the selected models, deployment regions, and routes. They may provide model services, cloud hosting, transmission, or security. Enterprises can confirm the relevant providers and change requirements before integration.

Protection measures

Public website and API traffic use HTTPS. Account and management functions are controlled by role, and API keys can be managed in the console. Data access, request archives, and logs follow feature policies and service agreements. See Security and trust.

Processing regions

This website provides public information and documentation. Access logs follow the actual hosting configuration. Inference services, processing regions and upstream scope are confirmed when the relevant service is provisioned.

Retention, return, and deletion

Retention follows the processing purpose, feature policies, applicable law, and contractual terms. Request archives, conversations, files, billing, and access logs have distinct scopes and retention requirements.

Written terms define return or deletion after the service ends, backup handling, and legally required retention.

Security incidents

If a security incident affects customer data, we investigate its impact, take response measures, and notify relevant parties as required by applicable law and contract. Notification channels, contacts, and cooperation procedures can be agreed before integration.

Requests and cooperation

Data enquiries, correction, export, deletion, and enterprise audit cooperation follow applicable law and the agreed terms. Contact the operator to confirm scope and process.