Privacy Policy

HKOS Drive Publisher · Effective 15 November 2026

Who this applies to

HKOS Drive Publisher is a private tool operated by one person for their own use. It runs on that person's own home server. It is not offered to the public, and the only Google account it is used with is the operator's own.

Google data the tool can access

The tool requests one Google OAuth scope: https://www.googleapis.com/auth/drive.file. Under this scope Google only allows access to files and folders that the tool itself created. The tool cannot see, read or change any other file in the Google Drive account.

Within its own folder the tool uses Google Drive to:

• create one folder, once, when it is first set up;
• upload its report files into that folder, replacing earlier versions of the same files;
• read the names, sizes, checksums and Google Drive IDs of the files in that folder, to check that uploads are complete and correct;
• download its own files during setup checks, to confirm that their contents match what was uploaded.

The tool does not delete files from Google Drive. It requests no Google permission other than drive.file: no profile, email or OpenID permissions, and no access to Gmail, Contacts, Calendar or any other Google service.

What is uploaded

The uploaded files are technical status reports that the operator's server generates about itself. They are scanned for credentials before upload, and the upload is refused if anything is found.

How the data is used

Google user data is used only to publish the reports and to verify that the published copies are intact. It is not used for advertising, it is not sold, and it is not used to train artificial-intelligence or machine-learning models.

The use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Storage on the operator's server

• The OAuth credentials issued by Google (refresh and access tokens) and the tool's OAuth client configuration are stored in a configuration file on the operator's server. File permissions restrict it to the account that runs the tool (and the server's administrator).
• A status file, a log and the server's system journal record when each publication ran, the result, and the names, sizes, checksums and Google Drive IDs of the published files. They do not contain file contents or credentials. These records stay on the server until the operator deletes them or the system journal's normal retention removes them.
• This status information (times, results, file counts and the Drive folder ID) is also read by the operator's own monitoring on the same server. The operator can view it directly or through AI assistants connected to their own accounts, and a one-line note about publication health can appear in the published reports themselves.
• Files downloaded during setup checks are written to a temporary directory that is deleted as soon as the check finishes.

Sharing

The tool itself sends data only to Google, in order to store the files in the operator's Google Drive. Apart from the operator's own monitoring described above, Google user data is not shared with anyone else. Files in Google Drive are then subject to the operator's own Google account settings and to Google's terms. The operator may read that folder with other tools of their own choosing, under their own accounts; this tool does not send data to those tools.

Removing access and data

• Access can be revoked at any time at myaccount.google.com/permissions. After that the tool can no longer reach Google Drive.
• The published files are removed by deleting the tool's folder in Google Drive.
• The operator removes the stored credentials, status file and log by deleting them from the server.

This website

These pages are static. They set no cookies, run no scripts and use no analytics. The web server keeps standard access logs (IP address, time, requested address, browser user-agent) for operating and securing the server.

Changes and contact

If the tool's use of Google data changes, this page is updated and the effective date above changes. Questions: whitlock.ethan80@gmail.com.