Privacy policy
l5h-backup · last updated 30 October 2026
l5h-backup is a single-user tool. Its only user is its author, who is also the owner of the Google account it connects to. It has no other users, no accounts, and no sign-up.
What data the application accesses
-
Files it creates itself in the operator's own Google Drive, via the
drive.filescope. This scope cannot reach any other file in the account. - Those files are encrypted backup archives produced by restic. They are encrypted before upload; the key is held only on the operator's own server and is never transmitted to Google or anyone else.
What is not collected
- No personal information is collected from anyone.
- No analytics, tracking, advertising or cookies. These pages set none.
- No data is sold, shared or transferred to any third party.
- Google Workspace APIs are not used to develop, improve or train generalised artificial intelligence or machine learning models.
Where credentials live
The OAuth client credentials and the resulting refresh token are stored on the operator's own server, readable only by the system account that runs the backup. They are not shared and are not transmitted anywhere except to Google, to obtain access tokens.
Retention and deletion
Backup archives are retained according to the operator's own retention policy and pruned automatically. Because every file lives in the operator's own Drive, they can be deleted at any time from the Drive interface. Access can be withdrawn at any time at myaccount.google.com/permissions, which immediately revokes the application's ability to reach any file.