Security · as of 24 Sep 2026

Encryption that accounts
for quantum computers too

Post-quantum encryption is a new generation of encryption, designed to withstand not only today’s computers but future quantum ones as well. Our websites, the Modulo admin and the Kioskbase, Veredar and Veredaria servers use it automatically with any modern browser. Sign-ins moving between Kioskbase tablets are already encrypted post-quantum end to end. And where we control the connection end to end — our apps talking to our servers — we allow nothing else: Veredar from version 0.18.0, Veredaria and Kioskbase for Mac, iPad and iPhone from their upcoming versions.

Why it matters

Harvest now, decrypt later

A quantum computer able to break today’s encryption does not exist yet. The threat, however, starts today:

  1. Today

    Someone on the way records your encrypted traffic. They cannot read it yet — and they do not need to.

  2. Years

    The recording sits on a disk. Invoices, contracts, passwords and staff personal data stay sensitive for five or ten years.

  3. Later

    A powerful enough quantum computer would break the classic key exchange (RSA, elliptic curves) and decrypt the recording after the fact. A post-quantum exchange is designed so that even it cannot.

That is why regulators are planning for it. The US NIST proposes to deprecate classic asymmetric cryptography (RSA, ECC) around 2030 and disallow it around 2035. The European Union’s coordinated roadmap of June 2025 recommends starting the transition by the end of 2026 and moving critical systems by 2030.

What exactly we have

Specific, not general

Automatic

Modulo website and admin

modulocms.com and admin.modulocms.sk run behind Cloudflare, which offers a hybrid post-quantum key exchange. A modern browser — Chrome and Edge on desktop from version 131, Firefox on desktop from 132, Safari from iOS and macOS 26 — uses it on its own, nothing to configure. An older browser still connects encrypted as before, just without the post-quantum part.

Post-quantum only

Apps ↔ our servers

The apps connect to our servers with a post-quantum key exchange only: Veredar for sync, updates and the Modulo link (from version 0.18.0, 24 September 2026), Veredaria for the Modulo link, where its connections and passwords come from, and Kioskbase for Mac, iPad and iPhone for the Kioskbase server (both from their upcoming versions, now in testing). A server that cannot do it is refused — no silent fallback to weaker encryption.

End to end

Moving a sign-in between tablets

When you replace a tablet in Kioskbase, the saved sign-in moves from the old one to the new one encrypted end to end with a post-quantum hybrid. The server only carries an encrypted package it cannot open itself, valid for 10 minutes. Since Kioskbase 1.25.0 for Android.

Preferred

Where the other side decides

With third-party servers the apps prefer the post-quantum exchange and use the classic one only when the server does not know it: Veredaria for SFTP (the ML-KEM-768 + X25519 hybrid, the same as in OpenSSH 10), Veredar for mail (IMAP, SMTP — with Gmail it already negotiates it) and for calendars and contacts (CalDAV, CardDAV) from version 0.18.0 on desktop, and Kioskbase for Apple when pairing with attendance systems — with dochadzka.online it does negotiate it (from the upcoming version). Veredar in Settings → Security and Veredaria with a badge next to the connection show what was actually negotiated with the server.

AES-256

Stored passwords

Connection passwords in Modulo sit in a vault encrypted with AES-256-GCM. 256-bit symmetric encryption is considered resistant to quantum computers too: the best-known quantum attack (Grover’s algorithm) reduces it to roughly 128-bit strength, which is considered sufficient.

Verified domains

On each of these addresses we verified on 24 September 2026 that the server negotiates the X25519MLKEM768 post-quantum key exchange:

  • modulocms.sk
  • modulocms.com
  • admin.modulocms.sk
  • kioskbase.sk
  • kioskbase.com
  • portal.kioskbase.sk
  • api.kioskbase.com
  • veredar.com
  • sync.veredar.com
  • veredaria.com

Why it is an advantage

The difference from companies that do not have it yet

Without post-quantum protectionWith us
Every connection captured today is an investment in the future for an attacker.A captured connection is designed to stay unreadable later too.
The transition is still ahead of them, and 2030 and 2035 are getting closer.For the connections we control, the transition is done.
They have to solve it themselves or wait for a vendor.Nothing for you to install or configure.
When a customer, auditor or bank asks about readiness, there is no answer.You have a specific answer: what, where and since when.

What is not post-quantum yet

Honest about the limits too

  • Website certificates. Certificate authorities do not issue post-quantum certificates yet. A certificate only proves the server’s identity at the moment of connecting, though — it has no bearing on “harvest now, decrypt later”.
  • Mail and FTPS. Mail (IMAP, SMTP) is encrypted by the device’s system and your mail server; we do not claim post-quantum protection for mail — on Apple devices the system does not support it today. FTPS is not post-quantum, and plain FTP is not encrypted at all.
  • App signatures. Our apps’ installation packages are signed with a classic signature.
  • Older app versions. Veredar has post-quantum-only connections from version 0.18.0 (24 September 2026); older versions connect with classic encryption. Veredaria and Kioskbase for Mac, iPad and iPhone bring them in their upcoming versions — once they are out, we will add the date here.

Questions

Do I have to set anything up or install anything?

No. An up-to-date browser is enough. With an older one the connection stays encrypted as before, just without the post-quantum part — nothing breaks.

Does this mean we are unbreakable?

No, and we do not call it that. It means the connection is also protected against a threat that classic encryption does not account for. Hence the hybrid: the classic and the new method together, so if one turns out weak, the other still protects the connection. Security has other sides too — passwords, access rights, updates.

How can I check it myself?

The easiest way is at the top of this page: if your browser negotiated post-quantum encryption, you will see a green badge. By hand: open modulocms.com/cdn-cgi/trace — the line kex=X25519MLKEM768 means your connection is running post-quantum right now. Which browsers support it and since which version is on the page Which browsers protect you (link below).

Do quantum computers that can do this exist already?

No. Nobody can say today when they will. That is exactly why it pays to protect today’s connections — what is recorded now can be decrypted later.

For IT: technical details
  • Key exchange in TLS 1.3: X25519MLKEM768 = classic X25519 + ML-KEM-768 (NIST FIPS 203, approved August 2024). Both shared secrets are combined; an attacker would have to break both parts.
  • Apps → our servers (Veredar from 0.18.0, Veredaria and Kioskbase for Apple from their upcoming versions): TLS 1.3 only, X25519MLKEM768 as the single allowed group, no fallback to a classic exchange. A server without ML-KEM (tested against github.com) fails the handshake.
  • Veredaria SFTP: mlkem768x25519-sha256 preferred (as in OpenSSH 10), with fallback to a classic exchange if the server does not know it (tested against test.rebex.net).
  • Kioskbase sign-in transfer: ML-KEM-768 + X25519 → HKDF-SHA-256 → AES-256-GCM, the package is valid on the server for 10 minutes.
  • Stored secrets: Modulo vault AES-256-GCM; Veredaria backup PBKDF2-SHA256 → AES-256-GCM.
  • Command-line check (curl with OpenSSL 3.5+): curl -s https://modulocms.com/cdn-cgi/trace | grep kex, or openssl s_client -connect modulocms.com:443 -groups X25519MLKEM768.
Which browsers protect you →
Details for each product:Kioskbase ↗Veredar ↗Veredaria ↗

As of 24 September 2026. When another part is added, we will list it here with a date.

Security questions? Write to us →