Privacy Policy

KLIMENTYEV Cloud · Last updated October 16, 2026

This policy describes the desktop application's current direct-to-Google architecture and its optional licensing feature. It must be reviewed against the final release before the site is published for OAuth verification.

1. Application and contact

KLIMENTYEV Cloud is a Windows desktop application for transferring and synchronizing files with Google Drive. For questions or privacy requests, contact the developer at klimentyevroman@gmail.com.

2. Google data we access

After your explicit Google OAuth authorization, the application requests the Google Drive scope https://www.googleapis.com/auth/drive. This scope can permit reading, creating, updating, sharing and deleting items in the authorized Google Drive account. The application uses these permissions to show storage quota, upload files and folder structures, download accessible items, maintain selected transfers, and create or change sharing permissions when directed by the user.

The application does not ask you to type your Google password into the desktop interface. Google authentication is performed in your browser.

3. How data is processed

• Google Drive transfers are made directly between the Windows application and Google services over HTTPS, without routing file contents through a developer-operated file server.
• Google OAuth credentials, transfer-queue metadata, local paths and transfer state are kept on the user's computer. The current preview stores the OAuth token in a local application JSON file; stronger OS-protected credential storage is planned before public release.
• Data is used to perform the user-requested file operations and to restore or synchronize selected transfer jobs. Public link permissions are only applied when the user selects that option.
• Local file removals in a one-way synchronization task do not automatically delete their cloud copies. Explicitly requested project deletion can move the selected cloud folder to Google Drive Trash.

4. Optional license activation

If the activation feature is enabled, the application contacts a separate license service over HTTPS to request or check activation. It may send a pseudonymous device identifier, the Windows account name, the product identifier and activation status. The administrator may receive activation requests in Telegram. The license service does not receive Google OAuth tokens, Drive file contents, file names or local paths. This activation mechanism is separate from Google authorization.

5. Limited Use of Google data

KLIMENTYEV Cloud's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google data is used to provide user-facing file-transfer functions and is not sold or used for advertising or training general-purpose AI models.

6. Sharing and service providers

Google processes Drive data under its own terms when users access Google Drive. When a user deliberately selects link-based sharing, anyone with the resulting link may be able to view the shared item according to the permissions selected. Website hosting may process technical connection logs. Optional license activation communicates only the activation data described above with its operator and Telegram.

7. Retention, revocation and deletion

Cloud files remain in the user's Google account subject to their Google Drive settings and actions. Locally stored OAuth data is removed from the app's active storage when the user disconnects; the user can also revoke authorization in Google Account connections. Local job history can be deleted with the application's local data. Contact the developer for requests concerning license records. Backups and retention practices for the optional license server should be finalized before its public activation.

8. Security

API connections use HTTPS. Access to local state depends on the security of the Windows user account and device. The current desktop preview is still being security-reviewed; no claim of independent security certification is made.

9. Updates

Changes to how Google or license data is handled will be reflected in this policy. Contact: klimentyevroman@gmail.com.