Paris, post-quantum
Since 5 November 2026, your workspace’s database, its files and the servers that run the platform are in Paris. Connections to them use a post-quantum key exchange on devices that support it, your documents are sealed with ML-KEM-1024 and your record is signed with post-quantum signatures. Here is what it covers, what we measured, and where it stops.
Your browser
On Mac or PC
X25519MLKEM768
TLS 1.3
The platform’s servers
Paris, France
X25519MLKEM768
TLS 1.3
The database and files
Paris, France
Measured on 5 November 2026, offering X25519MLKEM768 alone. A browser that does not offer it gets classical TLS.
4 to 5 November 2026
On the night of 4 to 5 November 2026, the platform moved to Paris. The final copy travelled over post-quantum connections only, and every table was compared with the original before Paris took over, at 00:27 Paris time.
217
Tables comparedRow by row, by fingerprint: identical to the original.
100%
Files identicalEach one checked by its SHA-256 fingerprint after the copy.
1
Key exchange offeredX25519MLKEM768 alone, with no classical fallback.
0
Direct connections allowedThe database’s own port refuses every address on the internet. Everything goes through HTTPS.
One exception, disclosed: during the rehearsal, before the post-quantum test, a first trial copy went over classical encryption. It was deleted, and everything after it travelled post-quantum.
Post-quantum, on the wire
Encrypted traffic can be recorded today and kept until a quantum computer can open it. That is why the platform and its database’s gateway negotiate a hybrid key exchange, X25519MLKEM768: ML-KEM-768, standardised by NIST to resist quantum computers, together with the long-established X25519. To read the traffic, an attacker would have to break both.
The platform and its database’s gateway accept the hybrid exchange, so a browser that offers it gets it, as current versions of Safari, Chrome, Firefox and Edge do. An older browser falls back to classical TLS.
The platform’s servers in Paris run Node.js 24 with OpenSSL 3.5, which offers the hybrid exchange first. The database’s gateway accepts it.
The database’s own port cannot negotiate post-quantum TLS, so it is closed to every address on the internet, with TLS required. From outside, your data is reached over HTTPS alone.
lornevale.com accepts the same exchange. If your browser offers it, you are reading these words over it.
Sources: NIST FIPS 203 (ML-KEM), August 2024 · NIST FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA), August 2024 · ANSSI on post-quantum cryptography (in French).
At rest
What is stored is protected too. Each document is encrypted with a key of its own, and that key is locked by ML-KEM-1024 and X25519 together. Each checkpoint of your record carries three signatures, two of them post-quantum.
AES-256-GCM, a new key for each document, locked by X25519 + ML-KEM-1024, the strongest of the three ML-KEM levels in NIST FIPS 203.
Every action chained to the one before it, and checkpoints signed with ML-DSA-87, SLH-DSA and Ed25519.
The keys that lock your documents are specific to your company.
Said plainly
Paris holds your workspace. Some of the services the platform uses work elsewhere, with the providers we name.
Supabase and Vercel, which host the platform, are companies based in the United States; your workspace is held in their Paris regions. The service providers page lists our providers, their roles and where they work.
Where it stops
Here is where our post-quantum protection ends today.
The certificates that prove each server’s identity, and the tokens that keep you signed in, still use classical cryptography. Post-quantum protects what crosses the wire; who sent it is still checked the classical way.
A call reaches the assistant over the public telephone network, which is not encrypted end to end.
Emails, payments and calls also pass through our providers, under their own encryption. Some, such as the card payment provider, do not accept post-quantum connections yet.
Each connection ends at our hosts’ edge or at the database’s gateway; beyond that point, the links inside Vercel and Supabase use their own encryption, which we cannot measure. Your records and messages are encrypted on disk by the host, not sealed one by one like documents.
We walk your IT team through every measurement on this page before you start.
