Security without empty promises.
RansomBackup reduces the privileges of credentials stored on the client. It does not promise absolute security or replace patching, secure authentication and offline copies.
Confidentiality
Restic encrypts content, names and metadata before upload. The repository password stays on the client. Transport to the gateway uses HTTPS.
Deletion resistance
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.
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.2-beta is not digitally signed yet; a checksum helps verify the download but is not a replacement for code signing.