Privacy policy

Data accessed and used

The workflow reads the evidence files the operator selects on the research server. It uses their contents, names, sizes, modification times, and checksums to upload and verify the files.

Through the Google Drive API, it accesses the destination folder configured for the selected research project and the file information needed to create folders, upload evidence, compare checksums, and retry failed transfers. Projects may reuse the same valid Google authorization. The OAuth authorization uses the Google Drive scope, which can permit wider access to the account's Drive than the selected folder. Each delivery targets its configured project folder.

OAuth access and refresh tokens authorize these operations. Google handles the account sign-in; this website does not collect the account password.

Storage and retention

Selected evidence is stored in the relevant project's configured folder in the authorized Google Drive account. Original evidence remains on the research server. Uploaded copies remain until the owner removes them; deleting a local source file does not remove its Drive copy.

OAuth credentials are stored in rclone's private configuration on the research server. Delivery receipts remain beside the local evidence and contain local paths, file names, sizes, checksums, timestamps, and the Drive destination. Credentials are not included in these receipts.

Credentials and local receipts remain until the server administrator removes them. Revoking Google access prevents further authorized access but does not by itself erase previously uploaded files, saved credentials, or local receipts.

Transfer and sharing

The workflow sends selected evidence and associated file metadata to Google Drive over HTTPS through the research server's network proxy. Google processes the uploaded content under its own service terms and privacy practices.

The evidence-upload command does not make files public or change their sharing permissions. Existing permissions on the destination folder determine who can access uploaded files.

The uploader has no advertising, data-sale, or AI-model-training integration. Google API data is used for the evidence-delivery and verification functions described here. Its use is subject to the Google API Services User Data Policy, including its Limited Use requirements.

Your controls

The account owner can revoke the connection from Google Account third-party connections, delete uploaded files in Google Drive, or ask the server administrator to remove stored credentials and local receipts.

Revoking access or removing the server's saved authorization prevents future uploads until the tool is authorized again. For support or data requests, contact the project owner using the user-support email displayed on the Google authorization screen.

This website

These informational pages contain no analytics scripts, cookies, forms, or evidence-upload interface. Any request logs maintained by the website's hosting provider are governed by that provider's privacy practices.