Laputa Backup · Personal use
A backup and restore workflow for machines you control, using restic encryption and selected, app-created files in your Google Drive account.
The Google consent screen identifies this application as LaputaBackup.
Each step depends on the configuration and permissions you choose.
Choose the source files and authorize the Google account for the application's backup files. Unrelated Drive files are outside the intended scope.
Restic encrypts the repository payload locally before it is transferred to Drive. Google still processes account information and storage-object metadata.
Retain the repository password separately and test a restore. A successful upload alone does not establish a complete, usable backup.
OAuth configuration, credential protection, selected sources, transfer behavior, and isolated restoration must be checked for the particular machine and account.
This page does not certify that those steps are complete. The utility does not itself establish encrypted credential storage, independent recovery-key custody, or protection from every host or account failure.
You can revoke the application's Google access through your Google account. Revocation stops authorized access; it does not delete backup objects already stored in Drive.
Backup deletion and retention are owner-controlled decisions. Keep recovery information until you have confirmed what you intend to retain or remove.
Use the support contact displayed on the application's Google consent screen. Refer to “Laputa Backup” or the consent-screen name “LaputaBackup” so the request can be identified.
Describe the issue without sending passwords, OAuth tokens, recovery keys, or backup contents. Review the privacy information and personal-use terms before authorizing access.
