Privacy Policy

1. DARKMIND and scope

This policy explains processing on the DARKMIND website, API, client and support service. For personal-data questions or to request operator information, select Privacy in support; a public form is available without signing in.

Processing is governed by applicable law. Accepting service terms acknowledges this policy; it does not replace a separate consent where the law requires one for a particular optional processing activity.

2. Account and technical data

Registration and authentication involve your email, name, language, account ID, a protected password representation, session information and device tokens. Passwords are not intended to be stored in plain text. We also record preferences, the accepted policy version and time, and your adult-age confirmation. That confirmation is not document-based age verification.

Infrastructure operation and security may involve connection addresses, browser or client information, request times and routes, error codes, rate-limit records and administrative events. Network-log details also depend on the hosting and protection services used. Necessary logs and billing records are not a public user history.

3. Website conversations and files

Text conversation history, technical request and generation-result records, and billing records are retained in the main service database. New uploaded and generated media use the separate darkmind.live media service. The main service and media service currently run on the same physical VPS; separate domains and processes do not mean separate physical servers.

New media become unavailable 14 minutes after the object is created in media storage, and files are then removed by automatic cleanup. The interface shows each file’s expiry beside it. Opening, downloading or issuing another link does not extend that deadline. Save any result you need to your device before it expires. Historical files in the previous store also receive a deadline no later than 14 minutes from their original creation; older files are deleted when the retention policy is applied.

Before releasing a file, the main service checks account ownership and access restrictions. For new media it issues a temporary signed darkmind.live link usually valid for up to 60 seconds. For audio and video playback, the link may remain valid until the file expires, never longer than 14 minutes. No link extends the file’s storage lifetime. Anyone holding a valid link can open the file, so do not publish or share it with others. An unpredictable file identifier alone does not replace an access check.

Deleting a conversation in the interface removes its visible history but does not immediately erase every related technical record, billing entry or backup. Make a data request for a broader deletion review. Media expiry does not delete conversation text or billing records, and cannot recall copies already downloaded by you or other recipients.

4. Client, API and agent tools

The installed client keeps working history and files locally in its profile. To complete a request, it sends the selected conversation context, parameters and necessary attachments to the service, which relays them to the model provider. Desktop API server accounting retains request identifiers and billing metadata, rather than a copy of the full message history.

Tools you enable may read local files, run commands and access websites or connected services. Their data can become part of the model context. Limit permissions to what is needed. Deleting a local project or website account does not automatically erase information held by an independent service you connected.

5. Billing, support and notifications

Balance and reconciliation records include reserved and charged amounts, model, time, status, request IDs and technical usage information. Actual payment data will depend on the payment provider when enabled. Do not enter card details in a support ticket.

Support stores messages, category, status, linked references, reply history and staff-only operational notes. A public report can include contact details you choose to supply. Tickets do not accept attachments. Do not paste full conversations, prohibited images, passwords, keys, payment credentials or unrelated sensitive information about others.

Tickets and replies are displayed on the website. Providing a contact email does not by itself mean automatic email delivery is enabled or that the support queue is monitored around the clock.

6. Purposes and legal grounds

Data is used to create and protect accounts, fulfil generations, display history, calculate charges, provide support, review notices, prevent abuse and satisfy binding requirements. Where applicable, grounds include performing the agreement, legal obligations or legitimate interests in security and defending rights, balanced against the user’s interests.

When a processing activity requires separate consent, it must be requested separately with a way to withdraw it. Using the service is not unconditional consent to any future processing, sale of conversations or advertising use.

7. Providers and transfers

Inputs and necessary context are transmitted to API and selected-model providers for generation. Hosting, delivery and connection-security providers, and payment or email providers if enabled, can receive data needed for their function. Staff access is limited to operational, support, security and legal needs.

Retention and privacy arrangements vary between models and providers. Do not assume every model offers zero retention or end-to-end encryption. HTTPS transport is not a promise that only you can read a request. Ask support for available recipient identities, roles and processing-country information before submitting sensitive data.

Processing may take place outside your country. Applicable localisation, international-transfer and contractual-safeguard requirements must be addressed for the actual operator and recipients. These terms do not authorise bypassing those requirements.

8. Retention and deletion

Account data and text history remain in the main database while needed for an active account and the requested functions, or until an appropriate deletion request, subject to legal exceptions. There is no general automatic expiry for server conversations. Uploaded and generated files follow the period of no more than 14 minutes from storage-object creation described above; historical files are also capped at 14 minutes from their original creation.

Resolved and closed tickets, including their messages, are automatically deleted during regular cleanup after 12 months without activity. An exception applies where justified preservation is needed for an unresolved dispute, a lawful requirement or the defence of rights; that need must be reviewed. Open tickets are retained to complete their review.

Transaction records, acceptance evidence and necessary dispute materials can remain after working-history deletion for the period required by law, reconciliation, a claim or the defence of rights. The need and scope must be reviewed; storing conversation content is not necessary merely to establish that a charge occurred.

Removal from working storage is not a promise of irreversible physical erasure or immediate deletion from earlier backups and hosting snapshots. When handling a deletion request, support should explain the scope, exceptions and available completion time. Temporary media expiry does not determine model-provider retention periods or mean providers retain nothing. We cannot promise deletion of information held solely by you or an independent external recipient.

9. Cookies and local storage

Authentication uses necessary secure session cookies. Your browser may keep language, interface preferences and a draft request; the client keeps its local history and settings. Clearing browser or client data does not automatically delete your server account.

Loading external fonts or other resources can disclose technical connection information to their suppliers. Optional advertising or analytics technologies, if introduced, need their own explanation and applicable user choice. Accepting the terms does not give advance consent to those technologies.

10. Requests and security

Depending on applicable law, you can request processing information, access and a copy, correction, deletion, restriction or portability, or object on an available ground. Where processing relies on separate consent, you can withdraw it without undoing the lawfulness of earlier processing. Contact support with your account and request. Proportionate account-ownership verification may be necessary.

Do not send identity documents without a specific justified request and an agreed secure method. Report a suspected compromise through Account support or the public form. Absolute security is not guaranteed; an incident is handled with the notification and corrective steps required by applicable law.

You may contact a competent data-protection authority or pursue other remedies. The service is not intended for minors. Report a suspected child account without providing unnecessary additional information about the child.

11. Policy changes

The current date and version appear on this page. We update the description and provide suitable notice when processing purposes, recipient arrangements or other material terms change. Where fresh separate consent is required, publishing an update does not replace obtaining it.