Resources
Certificates, authorisation documents, company materials and the full FAQ.
01DOCUMENTS
DOKÜMANLAR02FAQ
SIK SORULAN SORULAROpen questions, straight answers.
If your question isn't answered here: info@lpschain.com
Can LpsChain or system administrators access customer content?
The platform is designed so that our infrastructure does not require access to plaintext customer content. Files are encrypted before they leave your device and the keys stay under your institution's control; only encrypted data reaches our servers.
Who holds the keys?
Your institution. The LpsKey stays with the user, and content keys never leave institutional control; no content key is held on the server side.
What if quantum computers break the encryption?
Key establishment in the device and server layers uses ML-KEM-768 (FIPS 203), NIST's post-quantum standard. It is a safeguard designed against "harvest now, decrypt later" attacks.
Does the audit ledger have anything to do with cryptocurrency?
No. The ledger is an append-only record holding permissions and audit history that exposes any tampering. It involves no cryptocurrency or tokens and runs on CEIC-BFT consensus.
Does it work in an air-gapped (offline) environment?
Yes. The platform runs with air-gapped on-premises deployment. LpsChain Crypter is designed for fully offline encryption.
Does it integrate with our existing systems?
AD/LDAP, SIEM, SOAR, DLP, ClamAV, sandbox, Office 365, Collabora and Jitsi integrations are ready; extend via REST API.
What is the limit of the protection?
If the user's own device is compromised, end-to-end confidentiality cannot be preserved for that user. In every other scenario, all the attacker gets is ciphertext.
The architecture brief and deeper technical documents are shared on request. Just write to us from your institutional e-mail address.
info@lpschain.com