ALW Drive Archive

Privacy policy

This policy covers the ALW Drive Archive Windows tool and its public information pages.

Data used by the tool

The operator selects local files to archive. The tool uses rclone and the Google Drive API with the drive.file scope. This scope provides access to individual Drive files created or explicitly opened with the app. The tool reads archive file contents, names, paths, sizes, identifiers and checksums to upload, verify, list and restore the operator’s archives.

Where data is stored

Selected files and their integrity manifests are stored in the operator’s own Google Drive account. Authorization credentials and operation records remain in a protected directory on the Windows computer. The tool stores only the local records it needs to track operations and resume interrupted work.

Use and sharing

Google user data is used to provide archive, verification, restoration and status operations for the operator. The tool sends selected content to Google Drive and receives it back on restore. ALW Drive Archive does not sell this data, use it for advertising or model training, or send it to an ALW-operated server. Use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Retention and control

The operator can remove archives through Google Drive, revoke access in their Google Account settings and remove local credentials and operation records from their workstation. The public information pages are served by Cloudflare and contain no forms, analytics or sign-in. Cloudflare may process connection information to serve and protect these pages.

Questions

Use the developer support email listed on the app’s Google authorization screen to ask about access, privacy or deletion.