Skip to content
LEXUNCreate your KeyRun a decision free
Security & data

Security, data residency and the DPA — plainly.

LEXUN's honest security advantage is architectural: by default your decision data never reaches us, because analysis runs in your browser and is stored on your device. This page states exactly what that means, what our infrastructure does process, and what we can and cannot yet sign.

Architecture

  • Local-first processing — the simulation engine runs entirely client-side. Inputs, forecasts, outcomes and the audit trail live in your browser's local storage. There is no LEXUN database of user decisions. A LEXUN Key does not gate the engine: running a decision needs no Key and no account. The Key gates the record — it is the passcode that encrypts a saved decision on your own device. LIVE
  • One named exception, not a quiet one — the optional Copilot is the only feature that transmits decision-framing conversation text to a third-party model provider — and, when you press Explain, Challenge or Board summary under a result, the engine’s result summary (band, probability range, scenario percentages, the names of your inputs and which are assumptions, the horizon in months), none of the financial figures you entered. It is not the only thing that transmits typed content at all: the contact form, the waitlist and the Key email sign-up each send exactly the fields you put in them, and each appears in the table below. It is listed in the server-side table below with its processor, location and purpose, and it carries the same warning above its own text box. Everything else on this site works without it. LIVE
  • Encryption at rest, on your device — creating a LEXUN Key encrypts that record with AES-256-GCM (96-bit nonce) under a key derived from your passcode by PBKDF2-HMAC-SHA256 at 600,000 iterations, using the browser's own WebCrypto implementation. The passcode is never transmitted and never stored, so an unlock is a real decryption rather than a check we could remove — and nobody can read it without your passcode. What the 600,000 iterations buy is time, not immunity: someone who copies the encrypted record off the device can try passcodes against it offline, each guess made slow, so a short or common passcode can still fall. The minimum is eight characters, the strength note under the passcode box measures length only, and a passcode of several unrelated words is the practical defence. The corollary is blunt: a forgotten passcode means an unrecoverable record. LIVE
  • Transport security — all pages served over HTTPS with strict transport security. LIVE
  • No third-party trackers — no advertising pixels, no cross-site cookies, no third-party analytics scripts. The full storage-key inventory is in the Cookie Policy. LIVE

What is processed server-side today

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: —
—

That is the complete list, rendered from the same registry the privacy notice and the procurement pack read, so the three cannot disagree. The Copilot is the only optional AI route through which decision-related free text is sent to a model provider, and you decline it simply by not using it; it goes to Anthropic’s API through a LEXUN function, and is connected on this deployment. The forms send what you type into them to our hosting provider so that we can answer you. The row is here rather than buried because the whole point of this page is that the list is complete.

Where the API key lives. Calling a model needs a secret key, and a static site cannot hold a secret — every file in this deploy is downloadable by anyone. So the key is not in this site's files. It is set as an environment variable on the hosting platform and read at request time by the function, which never returns it, never logs it and never sends it to the browser. If it is absent, the assistant says so plainly and the rest of LEXUN carries on working, because the rest of LEXUN needs no server.

Data residency

Honestly stated: your decision data resides on your own device, in your jurisdiction, by construction. The things that travel are what you type into the optional Copilot and, if you ask it to explain, challenge or summarise a result, the engine’s result summary; both go to the United States and are covered in the table above. 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. Static site assets are served from a global CDN. We do not currently offer UK-only or EU-only hosting commitments because we do not host user decision data at all; if future sync features change this, residency options will be published here before launch, not after.

Data Processing Agreement

For organisations that require a signed DPA under UK GDPR Article 28: because LEXUN does not process your decision data server-side, a conventional controller–processor DPA covers only the narrow scope above (hosting logs, form submissions and, if your people use it, assistant messages). We will provide and sign a DPA reflecting that scope on request — email hello@lexun.co.uk. When hosted sync and team features ship, an expanded DPA with the full sub-processor list will be published on this page first. ON REQUEST

What we will not claim

No SSO, no SOC 2 report, no penetration-test certificate exists today, and we won't imply otherwise — capability status is tracked openly on the Organisations page. A security claim you cannot verify is worth exactly as much as an accuracy claim you cannot verify.

Reporting a vulnerability

Email hello@lexun.co.uk with "Security" in the subject. We commit to acknowledging reports within 5 working days.