Privacy Policy

1 Introduction

Drivix ("we", "the application") is an open-source desktop client for Linux that allows users to sync local files with Google Drive. We respect your privacy and are committed to protecting your personal data.

This privacy policy explains what information we collect, how we use it, and the rights you have regarding your data when using Drivix.

2 Google User Data Accessed

Drivix is an application that runs entirely on your local machine. We do not send data to any server of our own. However, in order to fulfill its file synchronization purpose, the application accesses, interacts with, and locally stores the following Google user data:

1. Profile and Authentication Data:

Email Address: Used to identify the user's account and manage multiple local sync profiles.
Name and Profile Picture: Used exclusively to customize the graphical user interface of the application and show which account is active.
OAuth 2.0 Authentication Tokens (Refresh and Access Tokens): Secure credentials stored locally to allow the application to connect with the Google Drive API without requiring you to log in manually on every startup.

2. Google Drive File Data:

File Metadata: File names, unique Google Drive IDs, modification timestamps, file sizes, and MD5 hashes. This data is queried to compare the local state against the cloud and decide which files need to be synchronized.
File Content: The files you decide to sync in your local folders are read, downloaded, and uploaded directly to keep the identical state between your PC and your Google Drive.

3 Google User Data Usage

The access, processing, and handling that Drivix performs on Google user data is strictly limited to the following operational purposes:

Local Bidirectional Synchronization: Uploading new or modified local files to your Google Drive account, and downloading new or modified files from Google Drive to your local Linux folder.
Local Account Management and Configuration: Allowing the user to link and unlink Google accounts interactively and visually within the Drivix user interface.
Real-time Change Monitoring: Monitoring file differences using timestamps and hashes to avoid duplicates and unnecessary data transfers.

🛡️ Limited Use Disclosure: Drivix's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the **Limited Use Requirements**. We do not sell, share, transfer, or disclose your data to third parties under any circumstances.

4 Requested Google Drive Permissions (OAuth Scopes)

To operate securely and correctly, Drivix requests access to the following scopes of your Google account:

https://www.googleapis.com/auth/drive: Full access to read, create, modify, sync, and send files to the Google Drive cloud trash in an automated manner according to user directives.
https://www.googleapis.com/auth/drive.file: Access to specific files created or opened by the Drivix application.
https://www.googleapis.com/auth/userinfo.profile: Access to your name and profile picture for visual personalization in the UI.
https://www.googleapis.com/auth/userinfo.email: Access to your email address for local profile identification and management.

These permissions are strictly necessary for the application to function. The user can revoke the granted access at any time through the Google account permissions management page.

5 Storage and Security

All data (tokens, configuration, sync state) is stored locally in the application's configuration directory on your system.
Authentication tokens are saved in encrypted JSON files protected by operating system permissions.
Communication with Google Drive is carried out exclusively through secure direct HTTPS requests (TLS encryption).
Drivix does not have its own servers. It is a 100% local application.

6 Your Rights

As a user, you have the right to:

Revoke Access: You can disconnect your Google account from the Drivix settings or from your Google Account settings.
Delete Your Data: You can delete all application data by removing the Drivix configuration directory on your system.
Inspect the Code: Drivix is open source. You can audit exactly what the application does by reviewing the source code on GitHub.

7 Cookies and Tracking

Drivix does not use cookies, analytics, tracking pixels, or any kind of tracking. The application does not collect usage data, telemetry, or statistics. Your activity remains completely private.

8 Third-Party Services

Drivix interacts with Google Drive API and Google OAuth 2.0, services provided by Google LLC. The use of these services is subject to the Google Privacy Policy and their Terms of Service.

9 Changes to this Policy

We may update this privacy policy occasionally. Changes will be posted on this page with a new update date. We recommend checking it periodically.

10 Contact

If you have questions about this privacy policy, you can contact us at:

Email: drivixsync@gmail.com
GitHub: Open an Issue