XDrive Transport

Privacy Policy

This policy describes the intended data practices of XDrive Transport. Update it if your actual deployment differs.

1. Information accessed

When the operator configures Xray-core to use Google Drive, the transport may access file contents and file metadata permitted by the Google OAuth scope and the implementation. With the full Drive scope, this can include files across the authorized Google Drive account.

2. Purpose of use

Google Drive data is accessed only to support the configured transport's storage, retrieval, synchronization, or other documented transport operations. It is not used to build advertising profiles or sold to third parties.

3. Storage and sharing

The transport may store or update its operational data in Google Drive. Whether any data is also stored locally, cached, logged, or transferred through an operator-controlled server depends on the actual Xray-core configuration and transport implementation. The operator is responsible for securing those systems and limiting access.

4. Google OAuth credentials

OAuth refresh tokens and client secrets are sensitive credentials. They should be stored securely, must not be published in source code or logs, and should be revoked when no longer needed. This informational website does not collect or store these credentials.

5. Google services

Google Drive API access is subject to Google's applicable terms and privacy policies. Users can review and revoke third-party account access through their Google Account.

Google API Services User Data is used in accordance with applicable Google API Services User Data Policy requirements, including Limited Use requirements where applicable.

6. Data retention and deletion

This website does not provide a login, collect form submissions, or maintain a database of visitor information. Drive files and transport records are retained or deleted according to the operator's configuration and actions. Revoke OAuth access and remove stored credentials to stop future authorized access.

7. Children's privacy

This service is not designed to collect personal information from children.

8. Changes to this policy

This policy may be updated to reflect changes in the software or its data practices. The revision date is shown on this page.

9. Contact

For privacy questions, contact ahmad@ahmad2213.eu.org.