Level 1 decryption keys never reach our servers
Level 1 means only you, and whoever you share your link with, can read your content. Two faults broke that — one left the key on our servers, the other handed back no key at all. Both are fixed, and we now keep no copy of your key.
A Level 1 workload is encrypted so that we cannot read it. Only someone holding your key can, and the point of the level is that we never hold one.
What was wrong. Workloads built in the portal had their key placed inside the page we served, so the key ended up sitting on our systems next to the content it unlocked. Workloads built through our API had the opposite problem — the key was never handed back at all, which left them impossible to open by anyone, including the customer who built them.
What is true now. Your key is shown to you once, at the moment you deploy, and we store it nowhere. Builds made through the API return it once as well, together with a link that carries it. Nothing we serve contains your key.
Was anything of yours exposed? No. When this was found, every workload on the network was Level 0, which is public content by design, so no customer key was ever written anywhere.
How to deploy one
- Deploy your site as Level 1, from the portal or through the API.
- Save the key when it is shown. It is shown once and we cannot recover it.
- Share the link that carries the key with the people who should read the content.
If you lose the key, redeploy — that is the trade for us not holding it. If you deployed anything as Level 1 before this change, redeploy it so it gets a key that was never on our side.