Septembet 17, 2026
Privacy policy
Welcome to Asset. This Privacy policy explains how we collect, use, and protect your personal information when you use our website.
1. Data Collection & Categorization
1.1 Personal Information
Lexera operates as an infrastructure layer. We classify the information flowing through our Model Context Protocol (MCP) into three distinct categories:
Agentic Payloads (Transient Data): The raw contract text, negotiations, and system prompts generated by your autonomous agents.
Corporate Playbooks (Persistent Data): Your proprietary internal legal guidelines, risk tolerances, and compliance checklists uploaded to the Custom Pipeline tier.
Escrow & Routing Telemetry (Operational Data): Transaction hashes, API call frequency, state management logs, and pre-funded wallet balances necessary for the Smart Escrow system.
2. The Zero-Training Mandate
This is our core commitment to enterprise data sovereignty. Lexera explicitly prohibits the use of your proprietary data for foundational AI model training.
No Model Fine-Tuning: Agentic Payloads and Corporate Playbooks routed through our API are never used to train, fine-tune, or improve any proprietary or third-party Large Language Models (LLMs).
Statutory Engine Isolation: Our Core AI performs localized statutory risk assessments entirely in-memory during the execution thread, ensuring no residual data is absorbed into a global training corpus.
3. Strict Data Segregation & Architecture
Row-Level Security (RLS): Our backend infrastructure leverages strict RLS policies within our Supabase database. This guarantees that one enterprise agent cannot systematically or accidentally query the contracts, playbooks, or escrow states of another tenant.
Siloed Execution: When an AI agent triggers a routing event, the payload is securely containerized and transmitted exclusively to the designated local partner law firm, bypassing all public registries.
We utilize a multi-tenant cloud architecture engineered for absolute cryptographic isolation between enterprise accounts.
4. Cross-Border Routing & Jurisdiction
Because Lexera routes physical legal verification across international borders, strict data handling protocols are enforced.
Localized Routing: Contract payloads designated for the United Arab Emirates (Federal or DIFC) or Jordan are routed exclusively to vetted attorneys physically operating within those respective jurisdictions.
Data Sovereignty Compliance: We process and route data in alignment with UAE federal data protection laws and DIFC specific regulations, ensuring compliance for cross-border asset management and commercial operations.
5. Retention & Cryptographic Purging
Our data lifecycle is tied strictly to the verification state of the document.
Unverified States: Temporary prompt histories and unverified draft states are actively purged upon the successful cryptographic sign-off by a human attorney.
Immutable Audit Trails: For compliance and liability transfer purposes, Lexera indefinitely retains the final verified document payload, the attorney's signature hash, and the transaction receipt associated with the Smart Escrow release.
6. Sub-Processors & The Partner Network
To provide human-in-the-loop verification, Lexera shares necessary payload data with authorized third parties.
The Supply Side: Your contract data is shared securely with our vetted legal network. These partner law firms act as sub-processors and are bound by strict non-disclosure and malpractice liability agreements.
No Third-Party Reselling: Under no circumstances does Lexera sell, lease, or monetize your Agentic Payloads or Corporate Playbooks to data brokers, marketing firms, or external legal networks outside of your explicit routing requests.
8. Changes to This Privacy Policy
We may update this Privacy Policy periodically. We will notify you of any changes by posting the new Privacy Policy on this page. Your continued use of the website after such modifications will constitute your acknowledgment of the modified Privacy Policy.
9. Contact Us
If you have questions, contact us at hello@lexera.dev