1. Scope of this policy
XDRIVE is a private experimental integration, not a public application or registration service. This informational website does not provide an OAuth sign-in form or directly process Google Drive files. The integration itself uses the Google Drive API when configured and authorized by its owner.
2. Google OAuth authorization
XDRIVE uses Google OAuth to request authorization for Google Drive API operations. Google presents the requested permissions during the authorization process. The exact data accessible to a deployment depends on the OAuth scopes granted and Google's permission model. Review the requested scopes before granting access.
Authorization credentials, such as access or refresh tokens, may be used by the configured integration to perform approved API requests. This public website does not display or distribute those credentials.
3. Google Drive data and file operations
Google Drive functions as a transport for temporary objects exchanged between Xray-core instances controlled by the owner. To support that operation, XDRIVE may:
- Create files or other Drive objects used to transport connection-related data.
- Read those objects to receive or process the transported data.
- Modify or replace objects as part of the exchange.
- Delete objects when required by the integration's operation.
Transport objects may contain technical connection information and data carried by the integration. Their content depends on the actual traffic and software configuration. Do not assume that those files contain only non-sensitive information.
4. Processing by Google and other providers
Google Drive necessarily receives and stores objects submitted through its API and processes them as part of providing the service. Google OAuth also processes information required for authorization. Google operates these services under its own applicable terms and privacy policies.
The informational website is intended to be hosted on Cloudflare Pages; visiting it can involve ordinary website request processing by the hosting provider. This policy does not claim that information remains exclusively on the owner's devices or is never processed by third-party services.
5. Temporary storage and retention
Drive objects are intended to be temporary transport artifacts. They may remain in the authorized Google Drive account while waiting to be read, updated, or deleted. Actual retention depends on the running integration, its configuration, and any manual actions by the account owner.
No specific automatic deletion schedule or maximum retention period is promised here. Revoking OAuth authorization does not itself remove files already stored in Google Drive.
6. Access revocation and removal
The Google Account owner can review or revoke XDRIVE's access through Google Account third-party connections (or the relevant Google Account security controls). Revocation prevents further access using the revoked authorization, subject to Google's enforcement of that change.
If Drive objects remain, the account owner can review and remove them in Google Drive, subject to their access rights and Google's normal behavior. Revoking access and deleting stored files are separate actions.
7. Security and limitations
The handling and protection of traffic data, Drive objects, and authorization credentials depend on the implementation and deployment configuration. This policy does not promise specific encryption, access isolation, or secure deletion mechanisms that have not been verified for the deployed version.
8. Changes and contact
This policy may be updated as the experimental integration changes. The date above indicates the current published version.
Questions about this policy may be directed to CONTACT_EMAIL.