1. Scope
This Privacy Policy explains how LegionASI handles information when you visit the website, create or use an account, participate in an AI conversation, use search or agent features, submit a contact message, or interact with a related service. It is written from the application behavior and configuration available at the time shown above.
2. Information the application handles
Depending on the feature you use, the application may handle these categories:
- Account information: account identifiers, name, email address, password-related records, credits or account state, and information needed to authenticate you.
- Conversation information: prompts, messages, agent selections, conversation history, uploaded files, generated responses, and other context you provide to receive an answer.
- Contact information: your name, email address, subject, message, and the time and technical context needed to process a contact submission.
- Technical information: IP address and request information available to the web server, browser and device characteristics, session identifiers, security events, and application logs.
- Transaction information: if a paid checkout is enabled and you use it, the application can receive payment and order status from the configured payment provider. Card details are handled by that provider rather than stored as raw card numbers in the application.
3. How information is used
LegionASI uses information to provide requested conversations and features, authenticate accounts, maintain sessions, process contact requests, operate and troubleshoot the application, prevent abuse, protect security, measure reliability, administer payments when enabled, and comply with legal obligations.
Conversation content may be sent to the model or inference service selected for a feature so that it can produce the requested output. Some paths use local or server-managed inference; others may use an external model API configured for the relevant agent. The applicable path determines where processing occurs.
4. When information is shared
LegionASI may share the minimum information needed with service providers that host the application, provide model inference, deliver email, protect the site, provide CAPTCHA or content delivery, or process an enabled payment. Providers act under their own terms and may process information in the locations where they operate.
Information may also be disclosed when required by law, to protect users or the Services, to investigate abuse or security incidents, or as part of a corporate transaction. LegionASI does not use the current site configuration to sell personal information.
5. Conversations, files, and model processing
Do not place secrets, credentials, or sensitive personal information into a conversation unless you are authorized to do so and the feature is appropriate for that material. AI output is generated from the information and instructions available to the model and can contain errors.
The application can retain account and conversation information as needed to provide account features and requested history. The codebase does not establish one universal deletion period for every type of content. Retention can depend on the feature, account state, operational logs, backups, and legal or security needs.
6. Cookies and sessions
The application starts a PHP session for public and authenticated routes. A session identifier may be stored in a browser cookie so the server can maintain login state, CSRF state, message limits, and other short-lived session data. See the Cookie Policy for the current cookie and browser-storage description.
7. Security
Security measures include authenticated routes, server-side validation in relevant workflows, session controls, access restrictions, input handling, and operational logging. Transport security and cookie flags depend on the production web-server configuration. No online system is perfectly secure, so do not submit information that would create an avoidable risk if exposed.
If you identify a security or privacy concern, use the Contact page and include safe, non-sensitive details.
8. Retention and deletion
We retain information for as long as reasonably necessary to provide the Services, maintain account records, complete transactions, investigate abuse, maintain security and backups, resolve disputes, and meet legal obligations. The available code does not support a single public retention number for every data class.
You may request access, correction, or deletion of personal information by using the Contact page. We may need to verify the request and may retain limited information where required for security, legal, or recordkeeping purposes.
9. Your choices
You can choose what to submit, stop using a feature, delete browser cookies through your browser controls, and contact LegionASI about account or privacy requests. Disabling session cookies can prevent sign-in and other features that depend on server-side session state.
10. Children
The Services are not directed to children who are not legally able to use them. Do not create an account or submit personal information if you are not eligible under the Terms of Service.
11. Policy updates
We may update this Policy when the application, providers, or legal requirements change. The last-updated date identifies the current version. Continued use after an update means the revised Policy applies to future use, subject to applicable law.
12. Contact
Privacy questions and data requests should be submitted through the Contact page. No separate public privacy address or physical business address is established in the current site configuration.