Cancelling a one-time backup process renders partially uploaded file undeletable.

[kevin1055]

Partially uploading a file in a one-time backup then cancelling it before it completes leads to space being used as shown by the online account information, but leaves nothing in the Browse Backups feature.

[csmiken]

This is expected behavior, but takes a little background to explain.
When you start a backup with Cyphertite, your data is split into 256k chunks. Each chunk is individually compressed, encrypted, and locked with your crypto passphrase before it is sent to our servers. This process repeats until all of your data is sent. After all the chunks of data are sent, Cyphertite will store a metadata file referencing each chunk and how to put them back together when you restore your data. If your backup is interrupted before this metadata file is sent (either by cancelling or a connection interruption) the metadata file will not be sent. This explains why storage space is used on our servers when you may not see a backup to restore.
If this happens, you can re-start the same backup again, and you will notice Cyphertite pickup where it left off. This is because our deduplication method will not re-send any chunks of data that are already on the server. Once the backyp sucessfully completes you will be able to list, browse, and restore your data.