1. What DevSSD Backup is
DevSSD Backup is a privately operated workflow using Restic for local encrypted backups and Rclone for Google Drive connectivity. It is not a public cloud-storage product or a hosted file-upload service. The website at backup.betterdayworks.cloud is informational and does not process backup files.
2. Google data and permissions requested
The local Rclone configuration requests the Google Drive API permission https://www.googleapis.com/auth/drive.file. This permission is used to create, identify, read, update, and delete backup repository files associated with the app's authorized Google Drive access, as needed to upload, verify, maintain, and restore backups. It does not request blanket access to unrelated Google Drive files.
The operator authorizes access through Google's OAuth screen. Google authentication tokens are held in the local Rclone configuration, not in the public website. Access remains subject to Google's permission controls.
3. What information is backed up
The operator selects local development files and directories for backup. These may include source code, project metadata, Git history, configuration files, archives, and other files selected by the operator. Backup contents can include confidential information; they are encrypted locally by Restic before uploading to Google Drive. The actual content backed up depends on operator-defined backup selections and exclusions.
4. How information is used, stored, and shared
- Use: To perform backup, integrity checking, version recovery, and repository maintenance initiated by the operator.
- Storage: Encrypted repository data is stored in the authorized Google Drive account. Credentials and the encryption password are managed by the operator outside this website.
- Sharing: Backup data is transferred to Google Drive for storage. Google and its infrastructure process that data under their applicable terms. No Google user data is sold or used for advertising.
- Human access: Access to the local workflow and recovery credentials is limited to the authorized operator and anyone that operator expressly permits.
5. Retention and deletion
Encrypted snapshots remain in Google Drive until the operator changes retention settings or deletes backup repository content. Older versions may be retained in snapshots even after the local source changes. Revoking the OAuth authorization prevents further app access but does not automatically delete previously uploaded files. The operator may delete the repository in Google Drive using authorized tools.
6. Security and limitations
Restic encrypts files before transfer and requires a repository password for restoration. Protecting the repository password, OAuth credentials, and recovery instructions is the operator's responsibility. No backup mechanism guarantees protection against every outage, user error, or data loss; restoration should be tested periodically.
7. Website data
This static website does not provide sign-in, cookies for site analytics, advertising trackers, or data-entry forms. Its hosting provider may still process routine access information such as IP address, request time, URL path, and browser details for security and operations.
8. Google API data use
Information accessed through Google APIs is used only to support the backup and recovery functions described above, not to serve ads or build unrelated profiles. The operator may revoke access in Google Account settings. Google Drive storage itself remains governed by Google’s terms and policies.
9. Changes and questions
This notice may be updated if the backup workflow, requested permissions, or hosting arrangements change. The latest version will be posted on this page. For questions, use the support email shown for DevSSD Backup on Google's OAuth consent screen.
Scope note: This policy describes the intended privately operated backup configuration. The website itself does not transfer or store project backup files.