Encrypted archives in your Google Drive. Recovery keys kept separately.
Developed and maintained by CredoNomics Investment Solutions, CardLedger Backup is currently used for controlled development and recovery validation with synthetic data.
Choose your Google account and the intended backup folder or existing files through Google’s supported authorization and Picker flow.
02
Encrypt locally
The utility encrypts the backup archive using AES-256-GCM before cloud transfer. The decryption key stays separate from Google Drive.
03
Verify recovery
Controlled tests read back the encrypted archive and non-secret integrity metadata, authenticate them and restore into an isolated disposable test database.
Security and control
A narrow permission. Deliberate safeguards.
Only drive.file
The utility requests only https://www.googleapis.com/auth/drive.file. It works with files created by the app or explicitly selected for it, rather than arbitrary access to your entire Drive.
This scope can permit changes to app-authorized files. The current controlled workflow does not enable remote deletion or retention pruning.
Tokens protected on Windows
OAuth token records use Windows DPAPI CurrentUser encryption and restricted local permissions. Decryption requires the authorized Windows user profile; tokens are not published on this website.
Separate recovery-key custody
Backup decryption keys are not uploaded to Google Drive. Keep the recovery key and its unlock information safely and independently; losing the key can prevent recovery.
Stay in control of access and stored files.
You can revoke Google authorization through your Google Account connections. Revocation stops future authorized access; existing encrypted archives remain until you separately delete them. The privacy policy explains local tokens, retention and cleanup.
For CardLedger Backup support or revocation/deletion guidance, contact credonomicsinvest@gmail.com. Never send tokens, passwords or recovery keys.