Security & Trust
Built on architecture,
not promises.
Your regulatory documents — SOPs, submissions, dossiers, proprietary procedures — are among the most sensitive assets your organization holds. Lexim Sphere is built from the ground up around a single architectural guarantee: your data is yours, completely, and no one else's data ever touches it.
Security isn't a feature we added.
It's how the platform is built.
Most security pages describe policies — what a vendor promises to do with your data. Ours describes architecture — how the platform is built so that your data cannot be accessed, used, or exposed to other customers, regardless of policy. Architecture is a stronger guarantee than policy because it doesn't depend on anyone following the right procedures.
01
Siloed by Design
Every customer environment is architecturally isolated. Your data doesn't share infrastructure with other customers. Isolation isn't a configuration — it's the default state of the platform.
02
No Cross-Contamination
Your documents, your Cabinet, your analysis history — none of it can reach another customer's environment. The boundary between tenants is architectural, not logical.
03
Zero Training Guarantee
Your documents are never used to train our AI models. Not as examples, not as fine-tuning data, not in any form. This is an architectural commitment — not a setting that could be changed.
The Zero-Training Guarantee
Your documents train
nothing and no one.
​
When you store your SOPs, submission dossiers, manufacturing procedures, and quality documentation in Lexim Cabinet, you are activating them for use by our Engines. You are not contributing them to any training dataset.
​
This matters because many AI platforms — even those with strong privacy policies — reserve the right to use customer data to improve their models. Lexim does not. Our models are trained on regulatory content, not on your proprietary documents. That distinction is the foundation of our relationship with every customer.
​
The Zero-Training Guarantee is not a contractual promise that could be renegotiated or overridden by policy change. It is a reflection of how the platform is built — your documents are processed by the Engines and returned to you. They are never retained for any purpose other than serving your organization.
Zero Training Guarantee
WHAT IT MEANS IN PRACTICE
Your documents are never used as training data — not for our models, not for any third-party models integrated into the platform.
Documents stored in Cabinet are processed to serve you — they are not retained beyond what is required to run the Engines on your request.
Your outputs — gap reports, analyses, translations — belong to you entirely. They are not reviewed, referenced, or retained by Lexim.
This applies to every document type — SOPs, submissions, dossiers, clinical documents, proprietary procedures, and any other content you upload to Cabinet.
Architecture
Single-tenant.
Completely siloed.
Every Lexim Sphere customer operates in a fully isolated environment. Not a logical partition within shared infrastructure — a complete architectural separation that means your data cannot reach another customer's environment under any circumstances.
Isolated by default, not by configuration
Isolation isn't something you need to request or configure. Every Lexim Sphere environment is isolated from every other from day one. There is no shared database, no shared processing environment, no shared storage layer.
No data sharing between customers
Your Cabinet contents, your analysis outputs, your Engine usage patterns, and your configuration cannot reach or influence any other customer's environment. The boundary is architectural — not a policy enforced at the application level.
Your outputs belong to you
Every gap report, every translation, every Synthesis analysis, every Docket dossier — all outputs generated by the Engines on your behalf belong to your organization. They are yours to download, distribute, and use without restriction.
Our Commitments
Four principles that govern your data.
These aren't policies that describe what we intend to do. They're the principles that shaped how the platform was built — and they don't change.
01
Your data is used only to serve you.
Documents you upload to Cabinet, queries you run through the Engines, and analyses you produce — all of this exists to serve your regulatory function. None of it is used for any other purpose — not to improve our models, not to benchmark performance across customers, not to train any system.
02
Regulatory intelligence is derived from regulatory content.
Lexim Sphere's AI capabilities are built on regulatory documents — publicly available guidance, standards, and regulatory body publications. Our models learn from the regulatory world, not from your proprietary documents. Your SOPs improve your outcomes, not our training data.
03
We tell you what we can and can't do with your data.
We don't make vague commitments about "responsible data use." We tell you precisely what happens to your documents when they enter the platform, how they're processed by the Engines, and what we do and don't retain. Transparency is part of the trust we're asking you to extend to us.
04
Security commitments evolve as the platform does.
We're building toward formal certifications that validate the architectural commitments we're making today. As Lexim Sphere matures, our security posture will be externally validated and continuously updated. We'll always tell you where we are on that journey — and we'll never claim certifications we don't have.
For Security Evaluators
Questions we expect from your IT and security team.
If you're evaluating Lexim Sphere on behalf of your organization's security or procurement function, these are the questions we expect — and the honest answers we give. If your evaluation requires information not covered here, contact us directly. We'd rather have a transparent conversation than a page that glosses over hard questions.
​
We're a growing company and our security posture reflects that honestly. We've built the platform on the right architectural foundations. Formal external certifications are on our roadmap and we'll update this page as they're achieved.
Q
Is customer data logically or physically separated?
Architecturally separated. Each customer environment is isolated at the infrastructure level — not partitioned within a shared database or processing environment. There is no technical pathway for one customer's data to reach another's.
Q
Will our documents be used to train your AI models?
No. The Zero-Training Guarantee is an architectural commitment. Documents uploaded to Cabinet are processed by the Engines to serve your requests. They are never retained as training data or used to improve our models in any form.
Q
What happens to our data when we terminate our subscription?
Your data is deleted from our systems at termination. We'll specify the deletion timeline and process in your agreement. You have the right to export all outputs before termination.
Q
Are you SOC 2 or ISO 27001 certified?
Not yet. These certifications are on our roadmap and we're building toward them. We won't claim certifications we don't have. If your procurement process requires specific certifications at this stage, let's have a direct conversation about what we can provide.
Q
Where is our data stored geographically?
We can discuss specific data residency requirements directly. If your organization has geographic data residency requirements, contact us to discuss what we can accommodate and our roadmap for regional hosting options.
Q
Who at Lexim can access our documents?
Access to customer environments is strictly controlled and limited to essential personnel for support and maintenance purposes. We maintain access logs and can provide details of our access control policies to evaluators upon request.
Security Questions?
We'll answer every question
directly and honestly.
Security evaluation shouldn't be a barrier to seeing what Sphere can do for your team. If your procurement or IT function has questions not covered here, reach out directly. We'd rather have the conversation early than have it slow down your evaluation.