> For AI agents: the complete documentation index is available at /en/llms.txt, the full documentation bundle is available at /en/llms-full.txt.

# Encryption & key

GetGeek Proxmox Backup uses **client-side encryption**. It is the single
most important property of the service, and it is on by default in
[Getting started](/en/proxmox-backup/kom-igang.md) — this page explains what it actually
means.

## How it works \{#hur-det-fungerar}

When you enable Encryption Key on your PBS storage in Proxmox VE, your own
PVE node generates an encryption key pair. Every time a backup runs, the
backup client encrypts the data **locally, on your server**, before
anything is sent to `sto-pbs.getgeek.se`. What reaches us is already
ciphertext.

In practice this means:

- The key never leaves your environment automatically — it is created and
  stored on your side, as `/etc/pve/priv/storage/<id>.enc` on your PVE node.
- GetGeek receives, stores, deduplicates and verifies already encrypted
  chunks. We have no way of reading the contents of your backups — not via a
  support request, not via administrator access to the server, not at all.
- Self-service restore works exactly as usual: your PVE node has the key,
  so restores happen transparently for you. Only we never see plaintext.

This makes it easy to demonstrate in a GDPR or NIS2 audit: your offsite
storage provider cannot, by design, access the contents of what is stored.

## You own the key — and the responsibility for it \{#du-ager-nyckeln-och-ansvaret-for-den}

Because encryption happens on the client side, it is you, not GetGeek, who
holds the only copy of the key needed to read your own backups. That is
the strength of the model — and its only risk.

As soon as you have created the key:

1. Back up the key file to a password manager, or print it and put it in a
   safe.
2. Keep the copy **somewhere other than on the PVE node it protects** —
   otherwise you lose both at once if the node fails.
3. Repeat steps 1–2 if you rotate or regenerate the key.

Proxmox also supports a master/recovery key that can be used to recover a
lost datastore key without GetGeek having to be involved — see the official
Proxmox documentation for the advanced workflow if you want an additional
safety net.

:::danger Lost key = unrestorable backup
If you lose the encryption key (and any master/recovery key of your own),
**your backups at GetGeek can no longer be read.** There is no back door,
no master key on our side and no support process that can help you —
GetGeek by definition cannot decrypt data we never had the key to. This is
not a limitation of our support; it is the whole point of client-side
encryption. Treat the key with the same seriousness as the master key to
the safe.
:::

## Common misconceptions \{#vanliga-missforstand}

- **"Can you restore the key if I email you?"** No. We have never had it.
- **"Is encryption optional?"** Technically you can add the storage without
  a key, but GetGeek never recommends it and does not describe it as an
  option in [Getting started](/en/proxmox-backup/kom-igang.md).
- **"Does encryption affect restore speed?"** Marginally — decryption and
  encryption happen locally on your PVE node, which normally has plenty of
  CPU capacity for it compared with network and disk I/O.
