Skip to content
LEXUNCreate your KeyRun a decision free
Trust and procurement

Everything a buyer needs before signing — only what is true today.

Architecture, data flows, hosting, encryption, access control, audit logging, backup, incident response, subprocessors, residency, retention, deletion, the DPA, continuity, model governance, AI usage and the known limitations. Where a control is designed with reference to a standard rather than certified against it, it says so.

Wording rule for this page: LIVE means you can verify it now; PLANNED means not built; BY AGREEMENT means offered only once implemented and tested for that customer. LEXUN holds no security certification and does not imply one.

Architecture

LEXUN is a local-first static application. The decision engine — three released Monte Carlo models on a shared core — runs entirely in the browser; decision inputs, forecasts, outcomes and the personal audit trail are written to the device’s own storage, encrypted under a passcode-derived key. There is no LEXUN database of customer decisions and no upload endpoint for them. The server-side components that do exist are listed below with their state on this deployment — what is active, what is deployed code waiting for a key, and what is planned — rendered from the registry rather than described from memory.

Every server-side component and its state on this deployment: ACTIVE works today; BUILT · DISABLED is deployed code that answers “not configured” until the operator sets the named variable; PLANNED is designed, not built. Rendered from the truth registry.
ComponentThis deploymentPurposeData it handlesConfiguration
Static site and CDN (Netlify)ACTIVEServes the pages, the registries and the assets; keeps server request logsRequest logs (IP address, user agent, path) held by NetlifyNone
Form processing (Netlify Forms)ACTIVEReceives and stores what a person deliberately types into a form and emails it to LEXUNThe submitted fields onlyNone
Copilot function — /api/askACTIVEForwards Copilot messages to the model provider (Anthropic) and counts the daily allowance on the serverThe text typed into the Copilot, the horizon and a filtered result summary; never the financial input valuesNeeds ANTHROPIC_API_KEY
Checkout state — /api/billing-configACTIVEAnswers whether this deployment can take money; the pages and the status page read itNoneNone
Stripe Checkout — /api/checkoutBUILT · DISABLEDStarts a Stripe Checkout session for Pro or Organisation seatsPlan, seat count, optional email; card details are entered on Stripe, never on LEXUNNeeds STRIPE_SECRET_KEY and the price ids
Entitlement check — /api/entitlementBUILT · DISABLEDReads the plan live from Stripe on every visit; nothing is inferred from browser storageA plan token or a Checkout session idNeeds STRIPE_SECRET_KEY
Billing portal — /api/portalBUILT · DISABLEDOpens the Stripe Customer Portal: change card, invoices, cancelThe plan tokenNeeds STRIPE_SECRET_KEY
Plan restore by email — /api/restoreBUILT · DISABLEDSends a 30-minute sign-in link to a paying customer's email so a plan can be recovered on another deviceThe email address typed; matched against Stripe customersNeeds STRIPE_SECRET_KEY and an email sender
Stripe webhook — /api/stripe-webhookBUILT · DISABLEDRecords Stripe events; grants nothing on its own because entitlement is read liveStripe event payloadsNeeds STRIPE_WEBHOOK_SECRET
Hosted service: accounts, organisations, shared workspaces, roles, approvals, an organisation audit log, server-verified seat billingPLANNEDThe organisation product's software promise (Release 2)Not yet designed in detail; published before it goes live—
Hosted API and webhooksPLANNEDProgrammatic access to the engine and records (Release 4)——

The organisation workspace — accounts, members, roles, shared decisions, review and approval workflows, an organisation audit log and server-verified billing — is the hosted service, PLANNED · R2. Its architecture is set out in the engineering blueprint that ships with every release bundle and will be published here before it goes live. Nothing on this page describes it as existing. The API contract is published at /api as a specification; LEXUN does not host those endpoints yet (PLANNED · R4).

Data flows

LEXUN data flows Decision data stays in the browser on the customer's device, encrypted under the LEXUN Key. Three named flows leave the device: static page requests to the Netlify CDN, form submissions to Netlify Forms, and the optional Copilot, via a Netlify function to Anthropic: it sends what a person deliberately types and, when they press a result button, a filtered result summary (band, probability range, scenario percentages, input names and the horizon) — never the figures entered or a saved record. No saved decision travels on any of them. Customer device — browser Decision engine (runs locally) inputs · classifications · 5,000 paths bands · sensitivity · receipts Decision Record store (device only) AES-256-GCM · key from passcode PBKDF2-HMAC-SHA256 · 600,000 iterations No decision data leaves this box. Netlify CDN (US/EU)static pages, scripts, JSON · request logs Netlify Forms (US)contact, waitlist, Key email, organisations request Netlify function → Anthropic API (US)optional assistant: typed messages onlynever a decision, figure or Key HTTPS · page assets form fields you typed assistant text (optional)
The complete set of network flows on the current architecture. The hosted service (Release 2) will add an encrypted workspace store and will be diagrammed here before it launches.

Three flows leave the device, each named in the privacy notice and the security page: page requests to the CDN (standard request logs), the fields a person types into a form, and — only when someone uses the optional Copilot, which is connected on this deployment — the Copilot’s own flow. The Copilot does not receive the simulator's financial input values. It may receive the text you type into it, the horizon in months, the model version and the engine-produced result summary — the band, the probability range, the scenario labels and percentages, the names of the inputs and which of them are assumptions, and the resolution criterion and date — and nothing else: no saved decision, no Key, no passcode, no email address. No saved decision, Key or passcode travels on any flow. Every flow, its state on this deployment and what it carries:

Every flow that can carry data off your device, with its state on this deployment. Rendered from the truth registry (data_flows) at every release; the same table appears on the privacy notice, the security page and the procurement pack.
FlowThis deploymentDestinationWhat travelsPurposeProcessorRetentionResidencyDoes it carry…Safeguards
Reading the siteACTIVENetlify (hosting and CDN)
  • server request logs: IP address, browser user agent, path and time
Serving the pages, the registries and the assetsNetlify, Inc.Netlify's request logs, then deleted on Netlify's own scheduleUnited Statesmodel inputs: no
financial figures: no
free text: no
identity: IP address only
  • no cookies
  • no third-party script, font, pixel or embed
  • a Content-Security-Policy that confines every request to this origin
Contact, organisation, pilot and Decision Audit request formsACTIVENetlify Forms, then an email to LEXUN
  • the fields you type on the organisations request form (/organisations, /packages, /decision-audit, /procurement): name, work email, organisation, role, team size, decision type, preferred next step, message
  • the fields you type on the pilot request form (/pilot): name, work email, organisation, short decision summary in words, business question, deadline
Answering youNetlify, Inc.24 months from the last exchange, or earlier on requestUnited Statesmodel inputs: no
financial figures: no
free text: yes
identity: name and email
  • honeypot field
  • nothing is booked or charged by a form
  • a form never sends a saved decision
The encrypted-sync waitlist (/roadmap#sync)ACTIVENetlify Forms
  • your email address
One email when encrypted sync across devices is releasedNetlify, Inc.Until you unsubscribe or ask, or 24 months after the launch emailUnited Statesmodel inputs: no
financial figures: no
free text: no
identity: email
  • opt-in, never pre-ticked
  • one-click unsubscribe on every email
The optional email beside a new LEXUN KeyACTIVENetlify Forms
  • your email address, if you give one
  • whether you ticked the marketing box
Warning you before a change that could affect a locally encrypted record; marketing only if tickedNetlify, Inc.Until you ask, or 24 months after the last emailUnited Statesmodel inputs: no
financial figures: no
free text: no
identity: email
  • the encrypted record, the derived key and the passcode never leave the device
  • the field is optional and says so
The optional CopilotACTIVEAnthropic's API, through a LEXUN serverless function
  • the text you type into the Copilot
  • the horizon in months and the model version
  • the engine-produced result summary: band, probability range, scenario labels and percentages, input names and which are assumptions, the resolution criterion and date
Plain-English intake, explanation, challenge and the board summaryAnthropic, PBCPer Anthropic's API terms: not used to train its modelsUnited Statesmodel inputs: the horizon in months only
financial figures: no
free text: yes
identity: none beyond the IP address the function sees
  • no financial input value is sent
  • every number in a reply comes from the engine or is removed
  • the API key never reaches the browser
  • the daily allowance is counted on the server
Buying Pro or Organisation seatsBUILT · DISABLEDStripe (Checkout, the customer portal, entitlement checks)
  • the plan and seat count
  • the email you give at checkout
  • card details, entered on Stripe's own page and never seen by LEXUN
Taking payment and verifying the plan on every visitStripe Payments Europe, Ltd. / Stripe, Inc.Per Stripe's terms; LEXUN holds no card dataIreland and the United Statesmodel inputs: no
financial figures: no
free text: no
identity: email and payment identity, held by Stripe
  • entitlement is read live from Stripe, never inferred from browser storage
  • no purchase control is shown while checkout is off
Recovering a paid plan on another deviceBUILT · DISABLEDStripe (lookup) and an email provider, named here the day it is connected
  • the email address you type
Sending a 30-minute sign-in link to a paying customerStripe; the email provider is named here the day it is connectedThe address is used once, to sendUnited States (Stripe); the email provider's location is stated the day it is connectedmodel inputs: no
financial figures: no
free text: no
identity: email
  • the reply is identical whether or not the address is known
Saved decisions, the Key, settingsACTIVEThis device only: browser storage, encrypted under your Key
  • everything you analyse and save
Your own recordNone — no server copy existsUntil you delete it, clear the browser's data or lose the device; the export is a readable copy you keep; it cannot be imported back into the workspaceYour devicemodel inputs: yes
financial figures: yes
free text: yes
identity: whatever you type
  • AES-GCM under a key derived from your passcode
  • LEXUN cannot read or recover it
Encrypted sync across devicesPLANNEDNot yet designed in detail; published before it goes live
  • encrypted records LEXUN cannot read
The same record on more than one deviceTo be named before launchTo be stated before launchTo be stated before launchmodel inputs: encrypted only
financial figures: encrypted only
free text: encrypted only
identity: to be stated
  • end-to-end encryption is the design constraint
Hosted API and webhooksPLANNEDNot live; the contract is published at /api
  • —
Programmatic access (Release 4)———model inputs: no
financial figures: no
free text: no
identity: —
—

In a founding pilot, evidence documents are exchanged through the customer’s own systems (shared drive or email at the customer’s choice) under a data-processing agreement; they are not uploaded to LEXUN infrastructure, because none exists to receive them.

Hosting

Netlify, Inc. serves the site from a global CDN with primary infrastructure in the United States and the EU, stores form submissions, and runs the Copilot function. The deployment is a versioned static bundle; every release is retained as a numbered archive, so any version can be redeployed byte for byte. Environment secrets (the Copilot’s API key and the Stripe keys) are held in the hosting platform’s environment configuration, never in a file.

Encryption

In transit: HTTPS on every page with HTTP Strict Transport Security. At rest, on the device: a saved Decision Record is encrypted with AES-256-GCM (96-bit nonce) under a key derived from the person’s passcode by PBKDF2-HMAC-SHA256 at 600,000 iterations, using the browser’s WebCrypto implementation. The passcode is never stored or transmitted; a forgotten passcode means an unrecoverable record, and the sign-up says so before it takes one. At rest, on our side: form submissions are stored by Netlify under its own encryption at rest.

Access control

There are no LEXUN accounts today, so there is no LEXUN account to compromise: access to a Decision Record is possession of the device plus knowledge of the passcode. Access to the hosting account and the form store is limited to the founder’s hosting account. Whether two-factor authentication is enabled on that account is verified as part of a customer’s security review and stated in the signed pack, not asserted on this page.

Roles and permissions for organisations (owner, approver, reviewer, challenger, read-only), invitation expiry and delegation are PLANNED · R2. SSO/SAML and SCIM are PLANNED · R4 only once implemented and tested.

Audit logging

Every frozen decision carries a sealed receipt over its question, model and engine versions, seed, a hash of its inputs, the probability and its band, the count of facts and assumptions, any alternatives compared, the success criterion and the resolution date; outcomes and evaluations are write-once. The challenge’s opposing case, the pre-mortem and the commitment (next action, owner and review date) are kept with the record, outside the seal, and each step is logged in its hash-chained audit trail. The software does not record reviewers or approvals yet: in the pilot, a person writes them into the record. That is the audit trail that exists today, per record, on the device. LIVE An organisation-wide, action-by-action audit log with who / when / why / from-which-state on every transition is PLANNED · R2. Administrative actions on the hosted service will be audited from its first release.

Backup and recovery

Site: every release bundle is retained; recovery is redeployment of the last good bundle, which takes minutes. Customer decision data: it lives on the customer’s device and is copied out by the customer’s own exports — the plain JSON export of the whole record, the sealed .lexun package for each decision and the PDF Decision Record — which the pilot schedules at freeze. These are archives, not restorable backups: they preserve the content and the .lexun package verifies on /verify, but the workspace cannot import any of them back today. We cannot recover a record for a customer, because we never hold it; that is a limitation we state rather than a promise we cannot keep. Recovery objectives for the hosted service will be published with it.

Incident response

Security reports are acknowledged within five working days. A personal data breach is handled as set out in section 13 of the privacy notice, including notification to the ICO within 72 hours where the UK GDPR requires it and to affected people without undue delay where the risk to them is high. Because no customer decision data is held by LEXUN, the realistic incident surface today is the form store and the hosting account, and the response plan is sized to that honestly.

Vulnerability reporting

Email hello@lexun.co.uk with “Security” in the subject; /.well-known/security.txt carries the same contact. We acknowledge within five working days and tell you what we did. No penetration test has been commissioned and no report exists; the release gate runs automated header, dependency-free and structured-data checks on every release, and the whole bundle is inspectable because it is static.

Subprocessors

WhoWhatWherePersonal data
Netlify, Inc.Hosting, CDN, request logs, form storage, serverless functionUnited States / EURequest logs; form fields you type
Anthropic PBCModel behind the optional assistantUnited StatesAssistant messages only; not used for training under its API terms
Mailbox providerEmail to and from @lexun.co.ukNamed on requestCorrespondence
Stripe BUILT · NOT CONNECTEDCard payments when self-serve checkout is switched onUnited States / IrelandNone today

This is the complete list at the date of this page. Additions are published here and in the privacy notice before they process anything.

Data residency

Decision data resides on the customer’s own device, in the customer’s jurisdiction, by construction. Form submissions and request logs are stored by Netlify in the United States; assistant messages go to Anthropic in the United States. We do not offer UK-only or EU-only residency commitments for those flows and will not imply one. Residency options for the hosted service will be published before it launches.

Retention

Organisation requests: 24 months from last correspondence, or the life of a resulting contract plus six years. Contact and waitlist submissions: 24 months. Server logs: the hosting provider’s own policy. Assistant conversations: not kept by us at all. Decision data on the device: until the customer erases it. The full table is section 7 of the privacy notice.

Deletion

Personal data we hold is deleted on request to privacy@lexun.co.uk within 30 days and confirmed. Decision data is deleted by the customer on the device — the cookies page carries the erase control — and LEXUN has nothing to delete because it holds no copy. Organisation and account deletion rules for the hosted service (what is deleted, what is retained for legal reasons, and the timing) will be published with it.

Data-processing agreement

Available on request and signed for the scope that exists: hosting logs, form submissions and, if used, assistant messages. It is drafted against the current architecture rather than a future one. When the hosted service ships, an expanded DPA with the full subprocessor list is published here first.

Business continuity

Stated plainly: LEXUN is founder-run. The mitigations are structural. The entire product is a static bundle that any competent engineer can redeploy from the retained archives; the models, tests, registries and release gates ship inside that bundle; the MCP server exposes the models to any client; and a customer’s records are exportable and verifiable without LEXUN’s involvement (/verify runs in the browser). Escrow of the release bundle is available by agreement for Enterprise customers and for Organisation-seat customers on an annual invoice.

Model governance

Three models are released; nine are proposed and not released. A model is released by proof, not by interface: 1055 automated checks, 96 frozen reproducibility results that must resolve unchanged, a mutation-tested contradiction engine over every public claim, and a public model registry with versions, lifecycle states and outcome-verification grades. No model, seed derivation or hash function changes silently; every change lands in the changelog with its version. Organisation-level model-approval controls (which versions an organisation permits) are PLANNED · R4.

AI usage

The decision models are not machine-learning systems: they are seeded Monte Carlo simulations with published inputs, so the same inputs and seed reproduce the same result on any machine. The one AI component is the optional Copilot, which sends what a person types — and, on request, the engine’s result summary without the figures entered — to Anthropic’s API to produce a reply. Every number in a reply is checked against what the engine produced and any figure the model wrote on its own is removed before it is shown; the form is filled only with figures the person wrote; the system prompt forbids quoting an accuracy figure or giving regulated advice; the allowance is enforced server-side. No customer data is used to train anything, by LEXUN or, under its API terms, by the provider.

Known limitations

  • No certification. Controls are designed with reference to Cyber Essentials and ISO/IEC 27001 principles; no certification, SOC 2 report or penetration-test report is held.
  • Single-user, local-first today. Team features, roles, approvals and an organisation audit log are planned, and delivered by people in the pilot.
  • No SSO, SCIM or uptime SLA. Offered by agreement only once implemented and tested.
  • Form data resides in the United States. No UK/EU residency commitment for that flow.
  • Founder dependency. Mitigated structurally (retained bundles, exportable records, escrow by agreement), not eliminated.
  • Records cannot be recovered by LEXUN. A lost device without an export, or a forgotten passcode, means a lost record.
  • ICO registration ZC183768. CA Capital Limited is on the ICO public register as a data controller (registered 27 June 2026, renewal due June 2027).

Request the signed security pack

The pack is this page as a dated PDF, the data-processing agreement for signature, the data-flow diagram, the model-governance overview and a procurement FAQ — plus answers to your own questionnaire, including the gaps.

A person reads every request and replies by email, normally within one working day. Nothing is booked, and no pilot starts, until we have confirmed it with you in writing — this form is a request, not a booking system. Details are processed by our hosting provider solely to deliver the request to us.