Security
How Cirdan encrypts addresses, what our servers can see, and where the protection stops.
2 min read
Cirdan is built so that a breach of our servers, your store or a warehouse system exposes ciphertext, not names and addresses. This page explains how, and is plain about the limits.
Encryption at checkout
The address is encrypted in the buyer's browser before the checkout form is sent. Cirdan uses libsodium sealed boxes: X25519 key agreement with XSalsa20-Poly1305 authenticated encryption, with a fresh sender key for every order. Holding the public key lets you encrypt, never decrypt, and nothing learned from one order helps with another.
If the encryption script cannot load or encryption fails, the order is not placed and the buyer is asked to try again. Checkout never falls back to sending the address in plain text.
What our servers hold
Our servers store the encrypted address, the items, the shipping country and postal code, statuses and tracking. They contain no code that can decrypt an address. Passwords are stored as scrypt hashes, sessions as hashes, and integration secrets encrypted at rest.
Who holds the key
You choose when you sign up.
- Your own key (recommended). Addresses are encrypted to a key made from 24 words that only you hold. Before an order ships, you release it in your browser, which opens the address and seals it again for the warehouse. Cirdan cannot read an address you have not released.
- Cirdan holds the key. Addresses are encrypted straight to the warehouse key, so orders ship without a release step. You trust Cirdan with the key.
The 24 words are only ever typed on the release page. That page loads no third-party code, pins every script with a subresource integrity hash and may only talk to the Cirdan API. Cirdan keeps no copy of the words: if they are lost, orders sealed to that key cannot be shipped.
What stays readable
Some data has to stay readable for the store to work:
- The shipping country and postal code, for rates, duties and routing.
- The buyer's email and billing details in your store, for confirmations and payment.
- The items, quantities, prices and timing of each order.
What Cirdan does not protect against
- A store or device that is compromised before the address is encrypted, including malicious code injected into the checkout page.
- The carrier, which needs a readable address to deliver.
- Someone who learns your 24 words. Treat them like the keys to every address your customers give you.
Reporting a problem
If you find a security issue, write to [email protected].