SME Strategy 8 min Read

How We Built a Zero-Knowledge Exchange for Australian SMEs

By SMEStack Compliance Editorial • General information, not tax or legal advice

In Australia, data breaches carry catastrophic penalties. Despite this, thousands of small businesses still ask new hires to email their Tax File Numbers (TFNs), Bank Details, and ID documents, or they share temporary API keys via Slack. This is a massive security liability.

At SME Stack, we built the Safe-Drop Vault. But we faced a critical challenge: if we build a database to hold your sensitive data, we instantly become a high-value target for hackers. The solution? We built a system where we literally cannot read the data. We call it the Zero-Knowledge Exchange.

The Solution: Hybrid Asymmetric & Symmetric Encryption

We implemented a Zero-Knowledge architecture using End-to-End Encryption (E2EE) powered by the browser's native Web Crypto API. The vault supports three flows: Requesting info, Sending secrets, and Two-Way Exchange. Here is how it works under the hood:

Step 1: Key Generation

When an employer requests data (like a TFN and a photo ID), their web browser generates an RSA-OAEP Key Pair. The Public Key is sent to our database. The Private Key is saved securely in the employer's browser storage (localStorage). It never touches our servers.

If the employer is sending a secret (like a password), the browser generates an AES-GCM Symmetric Key. It encrypts the password, uploads the ciphertext, and embeds the AES key directly into the URL (which is never sent to the server).

Step 2: The Drop

When an employee opens an onboarding link, their browser downloads the employer's Public RSA Key. They type in their TFN and upload their Passport. The browser generates a random AES key, encrypts the payload, and then encrypts the AES key using the RSA Public Key. This hybrid E2EE ensures even large files (up to 500KB) are secured.

At this point, SME Stack is holding the encrypted blob. Because we do not have the Private Key, it is mathematically impossible for us (or a hacker) to read it.

Step 3: Reveal & Burn

The employer logs back in on their device. Their browser downloads the encrypted blob, retrieves the Private Key from local storage, decrypts the AES key, and then decrypts the payload.

The data appears on screen. The employer copies the BSB and TFN into Xero, and clicks "Reveal & Burn". Our system permanently deletes the encrypted record. The data is burned after reading.

Why This Matters for SMEs

We have completely removed the risk of a centralized data breach. You can confidently tell your employees that their most sensitive identity and financial data is handled with military-grade encryption.