WYEA / Security
Security
What is true today, and what is not finished
A security page is only useful if it distinguishes the two. Everything below is a property of the running system. The section after it lists what we are not claiming yet, which is the part most vendors leave out.
Your document system sits outside this boundary and stays authoritative. The cell reads from it and writes back only where you turn that on.
Holds today
Properties of the running system
These are enforced by how the platform is built, and we will put each of them in an engagement agreement.
Your content is not reused
The commitment most questionnaires open with, and the one we can answer without qualification.
No training on firm content
Not by us and not by a model provider underneath us. This is a contractual term as well as an architectural one.
No shared corpus
There is no cross-firm store to retrieve from. The isolation is structural rather than a filter applied at query time.
No secondary use
Your documents are read to answer your questions. They are not mined for product analytics or benchmarking.
Answers are evidence-bound
The grounding rule is a security property as much as a quality one, because an unsourced claim is an unauditable one.
Verbatim or flagged
A quote is located in the source character for character or the claim is flagged. Nothing unlocatable is asserted.
Bound to a version
Answers bind to a version identity supplied by your own platform, so a claim can be rechecked after the file changes.
Unreadable is recorded
A source that could not be read comes back as not checked rather than as a confident answer.
The platform does not act alone
It drafts, locates and flags. It does not send, file or decide.
Nothing is filed
No output leaves your firm without a person releasing it.
No clearance is rendered
Where a conflict or a privilege question arises, the platform can surface a signal. Your own systems and people remain authoritative.
Your access rules govern
Reads run under credentials you grant, scoped to what those credentials can already see.
Isolation
One firm, one cell
Not claimed yet
The unfinished list
We would rather lose a deal on this page than win one and be corrected in diligence. Ask for the current position in writing and you will get it.
Client-controlled hosting
The cell runs in WYEA infrastructure. Deployment into your own cloud account, or onto hardware in your building, is a design target and not something running today.
Export and deletion
Retention, legal hold, export, deletion and offboarding are specified and not yet implemented. Until they are, offboarding is a manual process we run with you.
Client-visible operator access
Our support access is scoped and limited, but you cannot yet watch it in a log of your own. Closing that gap is on the build, and it is not closed.
Customer-managed keys
Content is encrypted at rest by the platform. Keys you hold and can revoke independently of us are not something we offer today.
Independent audit
There is no SOC 2 report, no ISO certificate and no third-party penetration test to hand you. When that changes this page will say so and name the firm.
Production history
The platform is early. Anyone who tells you their first deployment is battle-tested is telling you something else. Ask us where we are and we will tell you.
Questions your counsel will ask
Answered plainly
Do you train on our documents?
No. There is no shared corpus, no cross-firm retrieval, and no training on firm content, by us or by a provider underneath us. Instances share code and never data. This goes in the engagement agreement, not just on this page.
Where does our content actually live?
Your own document system stays the system of record. The platform runs one cell for your firm, with its own database, network and identity, in infrastructure WYEA operates. It is not deployed inside your cloud account or on your hardware today.
When do you sign an NDA?
Before we are sent a single document. We prefer your form. If you would rather not draft one, ours takes about five minutes to read.
Can we see an audit trail?
Events are written to an append-only chain that is protected against edit and deletion at the database level, and four flows produce entries today. What does not exist yet is a client-facing view of it, including of our own support access. We will show you the current state rather than describe the target.
What happens to our content if we stop working with you?
Today, offboarding is manual: we return or destroy content on your instruction and confirm it in writing. The automated export and deletion path is specified and not built. If a contractual deadline for return matters to you, say so early and we will write the manual process into the agreement.
Do you have SOC 2?
No. There is no SOC 2 report, no ISO certificate and no third-party penetration test. If a certificate is a hard requirement for your firm, we are not the right vendor yet and we would rather say that on the first call.
Why does this page list your gaps?
Because the alternative is being caught out by a security questionnaire, and because a platform whose central claim is that it will not assert things it cannot support should hold its own marketing to the same rule.
Start a conversation
Tell us what your people spend the day reading.
Thirty minutes, no obligation. If a shared product would serve you better, we will say so on the call.
The Brief
The week in legal, in four minutes.
Free, national to Orange County, every Wednesday.