Security without empty promises.

Confidentiality

Restic encrypts content, names and metadata before upload. The repository password stays on the client. Transport to the gateway uses HTTPS.

Recovery-key sheet and resumable setup

Version 0.7.9 generates a printable sheet containing the key, email, computer name, date, Terms version and security instructions; it can also save a text copy. RansomBackup servers receive neither the document nor the key; the client keeps a protected copy of the key on the PC so automatic backups can run. Anyone who obtains the sheet may try to open the backup, so keep it offline and separate from the protected PC. If the window is closed after account creation but before confirmation, the client keeps the incomplete state locally and shows the same key when reopened; backup does not start until setup is completed.

Reduced client-side deletion risk

The BACKUP token allows required uploads and index reads, while the gateway denies DELETE and GET /data/*. Restore uses a separate, temporary and revocable token. This separation limits what everyday credentials can do, but does not eliminate risks from failures, server errors or broader compromises.

Explicit limitations

• Losing the password means losing access to the backup.
• Malware controlling the PC may alter files before backup.
• Availability also depends on network, power, storage and maintenance.
• A snapshot list does not replace an end-to-end restore test.

Responsible disclosure

Send impact, reproduction steps and version to help@ransombackup.com. Do not access other users’ data, impair availability, or include unnecessary secrets or personal data.

Software integrity

Public packages include a SHA-256. Windows 0.7.9-beta is not digitally signed yet; a checksum helps verify the download but is not a replacement for code signing. The update checker does not install software and accepts HTTPS links from the official site only.