Legasus Product-Specific Terms

These Product-Specific Terms are incorporated into the Legasus Master Subscription Agreement and apply only to the features Customer uses or enables.

These Product-Specific Terms govern specific Services and functionality provided by AIDAN LLC d/b/a Legasus. Capitalized terms not defined here have the meanings in the Master Subscription Agreement.

1. General AI-Enabled Features

1.1 AI Technology

Legasus may provide AI-Enabled Features using Legasus technology, approved third-party AI providers, or a combination of systems. Model providers, model versions, orchestration techniques, retrieval systems, and supporting infrastructure may change over time.

Legasus may select or route requests among models based on performance, feature requirements, availability, security, cost, latency, Customer configuration, or other operational factors.

1.2 No Generalized Training on Customer Data

Legasus will not use Customer Data, Customer Content, AI Input, or AI Output to train generalized/shared Legasus models for unrelated customers unless Customer separately and expressly agrees in writing.

Approved third-party AI providers will be used under business/API arrangements intended to prevent Customer Data from being used to train generalized provider models, subject to provider-specific terms and any separately disclosed optional-feature conditions.

1.3 Human Review

AI Output is subject to the MSA, AI AUP, and AI & Professional Services Disclaimer. Customer is responsible for meaningful review before material reliance or external use.

2. Legasus Panel / Multi-Model Orchestration

Where Legasus provides a multi-model panel, orchestration, consensus, comparison, synthesis, ranking, or similar feature:

multiple models or agents may receive the same or different portions of AI Input;
an orchestration layer may select, combine, rank, critique, or summarize candidate outputs;
agreement among models does not establish truth or legal correctness;
disagreement among models does not necessarily indicate that one result is legally superior;
the orchestration process may change without changing the general nature of the Service;
model/provider availability may affect which models participate; and
Customer must independently verify final output, citations, reasoning, and authorities.

Unless an Order Form expressly states otherwise, use of Panel does not grant Customer rights in the underlying models, prompts, orchestration logic, routing methodology, evaluation methods, or system architecture.

3. Private AI Configuration

3.1 Availability

Private AI Configuration is available only by written approval, Order Form, or account configuration authorized by Legasus.

3.2 Meaning

Where expressly enabled, Private AI Configuration may be designed so specified AI Inputs are processed using Legasus-hosted/private model infrastructure without sending those Inputs to third-party foundation-model inference providers.

The exact configuration, supported features, deployment model, data location, performance characteristics, and limitations are defined in the applicable Order Form or technical specification.

3.3 No Implied On-Premises Commitment

Private AI Configuration does not mean Customer receives model weights, source code, on-premises deployment, dedicated physical hardware, or ownership of a model unless expressly stated in a signed Order Form.

3.4 Feature Differences

Private AI may have different quality, latency, model capability, context limits, feature support, maintenance requirements, or pricing than standard AI features. Legasus does not warrant identical results across AI configurations.

4. Customer-Specific AI Learning

4.1 Optional Feature

Customer-Specific AI Learning is optional and will be enabled only where Customer requests, authorizes, or purchases the feature.

4.2 Permitted Learning

Customer may authorize Legasus to adapt Customer's AI environment using Customer's own authorized materials, preferences, best practices, templates, terminology, workflows, prior approved work, instructions, or usage patterns.

Technical methods may include:

retrieval-augmented generation;
embeddings or vector indexes;
saved memory;
preference profiles;
customer-specific prompts/instructions;
adapters;
fine-tuning;
customer-specific evaluation datasets; or
other isolated techniques that serve substantially the same purpose.

Legasus may change the technical method without changing Customer's fundamental data-use rights.

4.3 Isolation

Customer-Specific AI Learning will be segregated from unrelated customers and will not be used to improve another customer's private agents or train a generalized/shared Legasus model.

4.4 Customer Responsibility

Customer is responsible for deciding what information is suitable for firm-specific learning and for ensuring it has necessary rights, authority, consents, and professional authorization.

4.5 Disable / Reset

Where technically supported, an Administrator may request that Customer-Specific AI Learning be disabled or reset. Deletion is subject to applicable law, backup cycles, dispute/legal-hold requirements, and technical limitations described in the Terms.

5. Legal Research, Web Research, Citations, and Third-Party Legal Databases

5.1 Research Assistance

Legasus may search, retrieve, summarize, quote, link to, or analyze legal or public information from Legasus systems and Third-Party Services.

5.2 LexisNexis and Licensed Databases

Legasus may make licensed legal research content or functionality available through providers such as LexisNexis under Legasus's commercial arrangements. Access may be limited by Customer plan, jurisdiction, provider license, usage restrictions, availability, or additional terms.

Customer receives no ownership interest in third-party databases or underlying licensed content.

Legasus may modify or discontinue access if a provider changes licensing, availability, APIs, terms, or commercial arrangements.

5.3 Verification

Customer must independently verify every material citation, quotation, authority, proposition, date, docket reference, and research result before reliance.

A citation or link does not guarantee:

existence;
correct citation format;
current validity;
precedential weight;
jurisdictional relevance;
accurate quotation;
correct procedural posture; or
support for the proposition stated.

5.4 Web Sources

Where research includes public web content, source websites may contain inaccurate, copyrighted, restricted, outdated, or misleading information. Customer is responsible for lawful use of third-party content and compliance with source-specific rights and terms.

6. Drafting and Document Generation

Generated documents, pleadings, discovery, correspondence, demands, contracts, forms, and templates are drafts unless expressly designated otherwise.

Customer is responsible for final legal sufficiency, factual accuracy, signatures, court/agency formatting, local rules, filing requirements, privilege, confidentiality, ethical requirements, and review by an appropriately qualified professional.

Templates supplied by Legasus remain Legasus or third-party intellectual property except for Customer's rights to use them with the Services. Customer-created templates remain Customer Content.

7. Intake AI and Lead Scoring

7.1 Decision Support

Legasus may score, classify, summarize, prioritize, or route incoming leads or inquiries using criteria such as practice fit, configured firm preferences, matter characteristics, geography, urgency, available information, experience, or other Customer-selected factors.

7.2 No Automatic Representation Decision

Legasus intake scoring does not itself:

accept a client;
reject a client;
establish an attorney-client relationship;
make a final legal-merit determination;
determine that an individual is ineligible for representation; or
determine that Customer is the best available attorney or firm.

Customer remains responsible for conflicts checks, legal assessment, engagement decisions, declination procedures, referral obligations, client communications, and all professional responsibilities.

7.3 High-Impact Use

Customer will not use an intake score as the sole basis for a legally significant decision where applicable law requires meaningful human review.

8. AI Agents and Agentic Workflows

8.1 Capabilities

Depending on enabled permissions, AI agents may prepare, propose, or initiate actions involving:

email or messaging;
calendar events;
tasks;
documents and files;
matter/contact data;
intake communications;
retainer preparation;
e-signature workflows;
Third-Party Services;
research; and
other workflows.

8.2 Default Approval

Material external or irreversible actions are intended to use human approval or confirmation controls by default where the product provides such controls.

Customer is responsible for reviewing the proposed action, recipient, attachments, content, permissions, and consequences before approval.

8.3 Customer-Configured Permissions

Customer controls agent permissions through available settings and is responsible for granting only necessary authority. Administrator permissions may permit broad actions and should be assigned carefully.

8.4 Reduced-Approval / Autonomous Experimental Mode

Legasus may, on request and at its discretion, permit Customer to reduce or bypass certain default approval controls.

Such functionality:

is experimental;
is not recommended for material legal, client-facing, financial, filing, or irreversible actions without meaningful supervision;
may require Administrator acknowledgment or an Order Form;
is enabled at Customer's direction and risk;
does not transfer professional responsibility to Legasus; and
may be suspended or revoked at any time for security, legal, compliance, reliability, or risk reasons.

Customer is responsible for scopes, limits, monitoring, approvals required by law, and resulting actions.

9. Email and Microsoft/Google Integrations

9.1 Connected Accounts

Customer may connect individual or firm-wide Google Workspace, Microsoft 365, or similar accounts where supported.

Customer represents that it has authority to connect each account and authorize the requested scopes.

9.2 Customer Control

Customer is responsible for Administrator decisions regarding:

which mailboxes/accounts are connected;
which users can search or access connected data;
sending authority;
retention and synchronization;
firm-wide delegation; and
revoking access.

9.3 Third-Party Terms

Google, Microsoft, and other providers may impose separate terms and API restrictions. Legasus may modify or discontinue integrations in response to provider changes.

10. Voice AI, Call Recording, Meeting Recording, and Transcription

10.1 Optional Functionality

Legasus may offer recording, transcription, voice generation, AI receptionist, call analysis, or related functionality to Customers who request or enable it.

Customer is solely responsible for determining what notice, consent, authorization, or opt-out is required under applicable federal, state, local, international, employment, privacy, professional, biometric, or wiretap laws.

Customer must provide/obtain legally required notice and consent before using recording or voice functionality.

10.3 Accuracy

Recordings and transcripts may contain errors, omissions, speaker misidentification, or inaccurate transcription. Customer must verify material information before reliance.

10.4 Synthetic Voice

Customer will not use voice-generation functionality for unauthorized impersonation, fraud, or deceptive synthetic communications.

11. Electronic Signature Workflows

Legasus may integrate with Third-Party Services such as DocuSign to prepare or initiate signature workflows.

The third-party provider's terms govern the signature service itself. Legasus does not independently guarantee that a signature, record, authentication method, or document is enforceable in every jurisdiction or transaction.

Customer is responsible for:

selecting signatories;
determining signature authority;
document accuracy;
legally required disclosures;
retention; and
determining whether electronic signature is appropriate for the transaction.

12. Client Portal

12.1 Limited Access

Customer may invite Client Users to limited matter-specific functionality, including viewing authorized matter information, receiving communications, or uploading/downloading authorized files.

12.2 Customer Responsibility

Customer is responsible for:

confirming identity and authorization;
deciding what information a Client User may access;
setting appropriate access duration;
revoking access;
determining whether disclosure affects privilege, confidentiality, protective orders, or professional obligations; and
answering substantive legal questions from Client Users.

12.3 Expiration and Revocation

Legasus may support expiring access links, limited sessions, or permission controls. Customer should configure available controls appropriately and promptly revoke unnecessary access.

13. Ethical Walls, Permissions, and Conflict Workflows

Legasus may provide role controls, matter permissions, ethical walls, conflict-screening workflows, and related tools.

These tools do not constitute a legal determination that a conflict has been cured, consent is sufficient, screening satisfies a professional rule, or an ethical wall is legally effective.

Customer is responsible for its professional analysis and configuration.

14. Legal Holds, Preservation, and Retention

Legasus may provide legal-hold, retention, preservation, archive, or deletion controls. Customer remains responsible for determining:

what data must be preserved;
when a legal hold begins and ends;
what retention schedule applies;
whether deletion must be suspended;
whether exported data must be retained elsewhere; and
whether a particular configuration satisfies law, professional obligations, insurance requirements, or Customer policy.

Legasus will follow Customer's configured instructions subject to technical limitations, law, and the Terms.

15. Medical, Insurance, and Matter Data

Legasus may extract, summarize, organize, or calculate information from medical, insurance, billing, or claim records.

Legasus does not provide healthcare, diagnosis, treatment, medical advice, medical necessity determinations, insurance coverage advice, or claims-adjusting services.

Customer must verify extracted data and calculations against authoritative records.

16. Settlement, Damages, Lien, Fee, and Recovery Calculations

Any calculations, ranges, predictions, or valuations supplied by Legasus are decision-support tools. Customer is responsible for verifying:

source amounts;
formulas;
fee agreements;
lien status;
applicable law;
costs;
interest;
reductions;
taxes where relevant; and
final distribution or settlement figures.

Legasus does not guarantee settlement value or recovery.

17. Mock Trial and Litigation Simulation

17.1 Simulated Participants

Legasus may simulate judges, jurors, opposing counsel, witnesses, panels, experts, mediators, or other roles for preparation or strategy.

17.2 No Prediction

Simulated output does not represent the actual views of a real person or predict how an actual judge, jury, witness, attorney, insurer, mediator, or tribunal will behave.

17.3 Input Quality

Simulation usefulness depends on information supplied by Customer and cannot account for all evidence, credibility, personality, local practice, judicial discretion, or real-world dynamics.

18. API and MCP

API and MCP access is not generally public and is granted on a case-by-case basis. Use is subject to the API & MCP Developer Terms and applicable Order Form.

Customer may not expose API/MCP credentials to unauthorized parties or use those interfaces to bypass permissions, extract Legasus proprietary technology, or access data outside authorized scopes.

19. Beta, Preview, Pilot, Early Access, and Evaluation Features

19.1 Status

Features marked beta, preview, pilot, early access, evaluation, prototype, experimental, or similar may be incomplete and may change or be discontinued at any time.

19.2 No SLA

Beta Features are excluded from SLAs unless an Order Form expressly states otherwise.

19.3 Sensitive Data

Customer should not process PHI or other regulated/sensitive data through a Beta Feature unless Legasus expressly designates that feature/configuration as eligible for that data.

19.4 Feedback

Legasus may use feedback regarding Beta Features under the Feedback provisions of the MSA.

20. Third-Party Services Generally

Third-Party Services may be subject to separate terms, privacy policies, license restrictions, uptime, rate limits, and availability. Customer is responsible for complying with applicable third-party terms.

Legasus may replace, disable, restrict, or discontinue an integration or third-party content source when necessary due to provider changes, licensing, security, law, reliability, or commercial impracticability.

Third-Party Service downtime is excluded from a Legasus SLA unless the applicable SLA or Order Form expressly states otherwise.

21. Updates

Legasus may update these Product-Specific Terms to reflect changes in features, providers, law, or risk. Updates are governed by the MSA.

22. Contact

Product/legal questions: legal@legasus.ai
Support: support@legasus.ai
Security: security@legasus.ai