1. Scope
This draft describes information involved in using LigaX accounts, workspaces and AI-assisted software creation. The legal identity and address of the entity responsible for processing personal information must be confirmed before this notice takes effect.
2. Information involved
Account features use information such as your email address, profile and workspace membership. Project features process the prompts, messages, files, instructions and other content you submit, together with generated outputs.
Connected services can provide information you authorize them to share. Usage, run status and diagnostic information support the operation of the workspace. The complete server-side collection and logging inventory is still under review.
3. How information is used
These features use information to authenticate you, organize projects, carry out requested AI tasks, display results and support connected workflows. Information you send to support is used to respond to your request.
The final notice must identify the applicable legal bases for processing and any additional purposes. This draft does not establish permission for unrelated uses of your information.
4. AI and connected services
AI tasks and integrations can require sending relevant project content to external services. Review what you submit and the permissions you grant before connecting an account or running a task.
The provider list, processing locations, international-transfer safeguards and provider retention and model-training practices have not yet been confirmed for this notice. This draft makes no promise that all providers exclude your content from training.
5. Cookies and browser storage
LigaX uses cookies for session and cached profile information. Browser storage also remembers preferences such as theme and selected workspace, and helps carry invitations and task choices through sign-in.
You can clear cookies and site storage using your browser settings. Doing so may sign you out or remove locally remembered preferences. A complete inventory of production cookies and any optional tracking remains to be confirmed.
7. Retention and security
Retention periods, deletion procedures, backup handling and security commitments must be verified against the deployed service before publication. Removing browser storage does not by itself delete information held by the service.
Avoid placing passwords or unnecessary sensitive personal information in ordinary prompts or project files. Use designated credential controls when a supported integration requires a secret.
8. Your choices and requests
You can contact support with questions about accessing, correcting or deleting your information. Rights and response requirements depend on applicable law; the final notice must explain the relevant request process, identity checks and complaint channels.
Eligibility rules and policies concerning children, as well as the process for notifying users of material policy changes, remain to be confirmed.
Contact
Questions about this draft? Contact support@ligaments.ai.