Lexa Shield — Frequently Asked Questions
Explore our most commonly asked questions below.
Platform & Core Differentiation
1. What makes Lexa Shield different from traditional AI compliance tools?
Lexa Shield is built on an explainable, white-box intelligence architecture. Each detection includes the triggering text, the condition involved, and a clear, human-readable explanation. There are no black-box predictions or hallucinations. Results are predictable, stable, and suitable for governance, legal review, and audit environments.
2. How is Lexa Shield different from LLMs or generative AI?
Large language models generate content based on probability. Their outputs can drift or vary.
Lexa Shield does not generate, predict, or guess.
It identifies informational patterns using structured, controlled logic built for transparency and repeatability.
Key distinctions:
- deterministic and explainable
- no hallucinations
- no content generation
- no training on client data
- stable, versioned behavior
- consistent results appropriate for compliance workflows
Lexa Shield is an analysis engine — not a generative model.
3. Why would I use Lexa Shield if I already have an AI?
Many organizations already use AI tools — including LLMs, copilots, chat assistants, or automated drafting systems. Those tools help create content, but they are not designed to evaluate compliance, risk exposure, or regulatory alignment in the content your teams produce.
Lexa Shield does something different and complementary:
- It does not generate or rewrite content.
- It does not behave like a probabilistic model.
- It performs explainable, deterministic analysis that identifies patterns linked to regulatory exposure.
- It provides clear explanations so governance, compliance, and audit teams can understand the “why” behind each flag.
- It operates with strict data minimization and never trains on customer content.
In short:
Your existing AI helps people create.Lexa Shield helps you ensure what was created is safe, compliant, and defensible before it is used, published, or deployed.
They serve different purposes — and together, they make your AI initiatives safer, more aligned, and more controlled.
4. Why do I need Lexa Shield if there are already compliance technologies in the market?
Most traditional compliance technologies focus on:
- policy management
- document repositories
- workflow routing
- case management
- training modules
- manual checklists
- after-the-fact review
Lexa Shield addresses a completely different layer of the compliance stack.
Lexa Shield performs real-time analysis of the actual text your organization produces — whether from humans or AI systems — and highlights potential areas of concern automatically, before those issues turn into regulatory, reputational, or operational risk.
It is not static and not limited to policy documents.
It analyzes the content itself.
This makes Lexa Shield valuable even if you already have:
- GRC tools
- DLP systems
- policy repositories
- audit software
- manual approval workflows
Lexa Shield strengthens these systems by adding:
- automated detection
- explainability
- consistency
- proactive risk visibility
- human-review support
Lexa Shield does not determine compliance status. It highlights patterns for review within your existing governance workflows.
It does the work traditional compliance tools can’t: reading content, spotting risk patterns, and offering structured explanations.
5. How is Lexa Shield different from other compliance platforms and tools?
Lexa Shield differs in three fundamental ways:
A. It analyzes content, not organizational structure.
Traditional compliance platforms manage standards, controls, checklists, and workflows.
Lexa Shield looks directly at the words, claims, and statements in your documents and communications.
It operates at the point where risk appears in real life: inside the text itself.
B. It is real-time, automated, and explainable.
Legacy platforms rely heavily on manual review or templated logic.
Lexa Shield provides:
- real-time analysis
- explainable detections
- versioned, consistent behavior
- clear reasoning behind each flag
- non-retentive, privacy-by-design scanning
This lets teams understand exactly what happened and why, without waiting for a review cycle.
C. It is built to complement — not replace — existing systems.
Lexa Shield works alongside your existing:
- AI tools
- GRC platforms
- governance systems
- legal review processes
- risk controls
- policy frameworks
It enhances your compliance posture by providing a layer of automated insight that other platforms do not offer.
You don’t need to replace anything.
Lexa Shield simply makes everything you already use stronger, safer, and more transparent.
Data Handling & Privacy
6. Does Lexa Shield store or learn from the content we upload?
No. All submitted content is processed only in isolated, short-lived memory and deleted immediately after analysis. Lexa Shield does not store, retain, reuse, or train on customer content — this applies to uploads, text input, and API requests.
7. How does Lexa Shield improve if it doesn’t learn from customer data?
Updates come from Lexa Shield’s own research, expert review cycles, and de-identified operational signals that do not contain text and cannot be linked to any client. Improvements never involve customer documents or user-submitted content. This ensures progress without compromising privacy or regulatory expectations.
8. Does Lexa Shield provide or interpret legal advice?
No. Lexa Shield highlights informational patterns that may warrant review, but it does not determine compliance status or provide legal conclusions. All findings should be evaluated by qualified professionals within your organization.
Libraries & Customization
9. Which regulatory libraries are available?
Lexa Shield offers a growing catalog of global laws, standards, and frameworks. These libraries can be activated based on your plan level and organizational needs. Coverage spans privacy, security, healthcare, labor, consumer rights, and industry-specific domains.
10. Can we customize libraries or add internal policy content?
Enterprise clients may request tailored configurations through our Custom Enterprise Solutions program. This allows organizations to reflect internal policies or sector-specific considerations within their workflows while maintaining explainability and consistency.
Dashboard & User Access
11. What dashboard features are included?
Depending on your plan level, the dashboard may include:
- Reports
- Risk Analysis
- Library Management
- History & Compliance Signatures
- Billing
- Library Controls
- User Assignments
- User Management
- Audit Log Viewer
- Security & Settings
- Help Center
All dashboard features follow strict data-minimization principles.
12. Do you support multi-user access and role-based permissions?
Yes. Administrators can manage users, configure roles, and control library access to align with internal governance requirements.
13. Does Lexa Shield support two-factor authentication and SSO?
Yes. Two-factor authentication is available, and the platform is designed for SSO readiness depending on your plan and deployment requirements.
API & Integrations
14. Does Lexa Shield support API integration?
Yes. The API allows organizations to embed explainable compliance intelligence directly into platforms such as case-management systems, governance tools, CMS environments, HR/CRM applications, and LLM-Ops workflows.
15. Does the API store, reuse, or learn from API input?
No. API input is processed only in isolated memory and deleted immediately after analysis. No text, metadata, or content is retained.
16. What management features are available for API-only users?
Depending on tier, API-only users may access:
- Monitoring
- Logging
- Library Controls
- Billing
- Security Settings
- Help Center
Submitted text is never visible in the console.
Security & Governance
17. Is Lexa Shield suitable for regulated industries?
Yes. The platform’s explainable, audit-ready structure is designed for sectors with high standards of oversight, including healthcare, financial services, insurance, life sciences, government, education, and global enterprise governance.
18. Does Lexa Shield align with global privacy and security principles?
Yes. Lexa Shield is engineered with strong alignment to widely recognized principles found in GDPR, LGPD, HIPAA data-minimization expectations, and the control philosophies of SOC 2 and ISO 27001. For full details, see the Security & Trust page.
Hashes, Integrity & Auditability
19. What is a compliance signature (hash), and why is it used?
Each analysis is paired with a tamper-evident cryptographic hash.
This allows organizations to confirm that:
- the results remain unaltered
- the analysis matches its original state
- integrity is maintained for audit or review
No underlying text is stored.
20. What internal records does Lexa Shield maintain?
To support consistency and version control — without storing any customer content — the system maintains limited internal metadata such as:
- rule identifiers
- risk identifiers
- engine version used
- system-level events related to the analysis
These records help ensure predictable behavior across updates.
21. How do audit logs work?
Lexa Shield logs system-level events including logins, user actions, administrative changes, and API events. These logs help organizations maintain governance visibility while ensuring no user-submitted content is retained.
Understanding Results
22. How do teams understand why something was flagged?
Each detection includes:
- the triggering text
- the condition that matched
- a clear explanation
- the engine version
Optional match-strength indicators help teams understand contextual relevance without probabilistic scoring.
Myths vs. Facts
Myth
Fact
Myth
Fact
Myth
Fact
Myth
Fact
How do we begin?
You can start a trial, request a demo, or speak with our team to explore the best configuration for your organization.
* Pricing, features, and limits may vary by plan. Additional terms apply. See Data Handling & Privacy Controls page for details.