Privacy notice
What the current service processes, who can see it, storage and browser preferences.
1. Notice status and controller #
This draft describes the current deployment. The operator’s legal identity, service address and privacy contact have not yet been provided. This is an incomplete notice until those details, retention policy and applicable processing arrangements are finalized. Do not use this draft as evidence of GDPR certification or other compliance.
Account administration and security records are handled by the service operator. Customer content may involve different controller and processor roles depending on the deployment and contracts. A processing agreement is not automatically created by a website label; appropriate agreements and subprocessor arrangements must be completed for the intended use.
2. Data we process #
Account data includes usernames, email addresses, password hashes, display names, avatars, sessions and verification or recovery records. Technical and security records can include request metadata, IP addresses, authentication events and audit entries.
Creative data includes projects, films, prompts, source uploads, generated images, audio and video, tags, source-path provenance, metadata and derived thumbnails or previews. Compute records include node identifiers, host and system information, CPU/GPU and memory information, storage availability, installed model inventory, capabilities, routes, job status and transfer records. Access rules, CRED transactions, moderation reports and enforcement records may also be stored.
3. Purposes and proposed legal bases #
The service processes data to authenticate users, store and organize assets, run requested jobs, transfer results, produce previews, schedule resources and show account or node status. Security, abuse prevention, moderation and operational troubleshooting also require some records.
Where EU law applies, the basis for processing must be appropriate to each purpose: contract necessity for requested services, assessed legitimate interests for proportionate security and abuse prevention, legal obligations where applicable, and separate consent where required for optional processing. Account registration is not blanket consent. Any unrelated use requires an appropriate basis and an updated notice.
4. Recipients and shared compute #
Authorized users in the relevant account or tenant can access content according to permissions. Administrators, moderators and technical operators may access information necessary for their functions. Storage, hosting and delivery infrastructure necessarily process service data.
When work uses another owner’s node, inputs and outputs needed for that work reach that machine. Its owner may inspect the work and related user identity through node review or host access. Shared compute is unsuitable for confidential or regulated data unless an appropriate technical and contractual arrangement has been established. Private-node selection limits scheduling; it is not a promise that no service administrator can access data.
If you choose an external generation provider, relevant inputs and metadata must be sent to it under disclosed integration terms. A mention of a provider on the site does not mean data is already sent to it. Lawful disclosures may also be necessary for legal process or protection against abuse. The actual processor/vendor inventory and processing locations must be finalized before this notice is made final.
5. Retention, deletion and protection #
The current catalog retains stored assets and records; there is no universal automatic age-based deletion of all account content. Retention must reflect the requested service, security investigations, transaction integrity and legal requirements. Exact operational schedules, backup retention and deletion handling remain to be finalized.
Deletion from a library, removal of a source mapping, removal from node storage and expiry of backups are different operations. Copies may remain on participating nodes or in retained records until separately handled. Do not assume a user-interface action erases every copy. Access controls, authenticated transport and quotas reduce risk but do not eliminate breach or data-loss risk.
7. Requests and contact #
EU rights and cross-border processing are described in the EU data-rights page. Other jurisdictions may provide additional rights. Request handling requires a verified contact channel; the privacy contact is pending. Avoid sending passwords, private keys or unnecessary sensitive documents in a request. Existing profile controls do not constitute a complete statutory access or deletion workflow.
Official references
Reference material informs this draft; it does not certify the service.