Privacy notice
Second Brain Backup · Last updated: November 14, 2026
Second Brain Backup is a personal application operated by its owner to back up the owner's Second Brain to the owner's Google Drive. This notice describes the backup application and these informational pages.
Information used and why
The application packages the owner's Second Brain notes, revision and conflict history, associated assets, and recovery information into backup archives. It uploads those archives to Google Drive so the owner can recover the Second Brain after a device or operating-system change.
The application uses Google account identity information to verify the intended backup account. It uses Drive file identifiers, names, locations, sizes, and checksums to upload and verify archives, record successful backups, and manage retention.
Google Drive access
The application requests only the Google Drive drive.file scope. Its access is limited to files it creates or that the owner explicitly selects for use with the application. It does not request access to every file in the owner's Drive.
Storage and sharing
Backup archives are stored on the owner's private host and in the owner's Google Drive. OAuth credentials are stored in private configuration on the owner's host and are excluded from backup archives.
The application does not sell backup content or Google user data, use it for advertising or model training, or share it with third parties other than Google Drive for the owner's requested storage. These informational pages contain no JavaScript, analytics, or tracking tools.
Retention and deletion
The configured cloud retention policy keeps the five latest verified backups. After a new upload is verified, the application may permanently delete older backup archives that its ownership records identify as created by this backup job. It does not delete unrelated Drive files. If verification or retention checks fail, older archives may remain until the owner resolves the issue.
Local archives are retained until the owner manually deletes them. The owner can also manually delete cloud archives in Google Drive. Revoking access does not delete existing archives. After revocation, those archives remain until the owner deletes them.
Revoking access
The owner can revoke this application's access in their Google Account's third-party connections settings. Once access is revoked, the application cannot continue accessing Drive through that authorization. The owner may also stop the local backup schedule and remove the local OAuth configuration.
Contact
Contact the Google account owner shown on the OAuth consent screen.