1. Who operates this app?
S.H.I.E.L.D. Backups is a private-use integration operated by the developer of the S.H.I.E.L.D. security-monitoring project. It is not offered as a public service. The public website is informational; it does not authenticate users or display stored backups.
2. What Google account information may be accessed?
With the account owner's explicit OAuth consent, the backup integration requests the Google Drive drive.file scope. This permission allows it to create, read, update, list, and delete files that it creates or that the user specifically opens or shares with the application. It does not request unrestricted access to every file in the account.
The authentication process provides OAuth credentials/tokens to the configured backup client so it can access the permitted files. The application does not require a Google account password.
3. Why and how is data used?
The intended use is to transfer approved S.H.I.E.L.D. controller backups and historical security data to the operator's Google Drive, check uploaded data integrity, and restore those archives when necessary. Security archives may contain technical information such as timestamps, IP addresses, request paths, and finding metadata originating from monitored websites.
Access to Google Drive data is limited to backup, verification, restoration, and operator-approved retention tasks. Google user data is not used for advertising, profiling, or sale.
4. Storage and security
Google Drive holds any files uploaded after the integration is activated. The local controller or authorized administrator device holds the application's OAuth configuration and tokens, protected by operating-system access controls. Encryption of archives before upload, checksum verification, and restore testing are part of the planned deployment and must be validated before production data is archived; this page does not claim those controls are already operating.
This informational website does not receive or store Google OAuth tokens or backup contents.
5. Sharing and retention
Google Drive processes stored files as the chosen storage provider. The operator does not sell Google user data or make backup data publicly available through this website. Backups and historical files are retained according to the operator's documented recovery and archival requirements; there is no promise of a fixed automatic deletion period for remote archives.
6. Consent, access, and deletion
The Google account owner can revoke this application's access in their Google Account's third-party connections settings. Revoking permission stops future authorized API access but does not automatically delete files already saved to Google Drive. The owner can inspect or delete those files through Google Drive or through the backup client's authorized maintenance procedures.
7. Contact and changes
Project operator: stanlaky-dev on GitHub. This policy may be updated as the backup integration is implemented or its handling of data changes; the effective date above will be updated when the policy changes. Do not include private security logs, passwords, or OAuth tokens in public messages.