Privacy Policy
Last updated: 11 November 2026
This policy describes how the file-based data exchange component uses Google user data when an operator configures it with their own Google account and Google Drive API credentials.
Google account data accessed
The component uses OAuth 2.0 to access Google Drive. The configured Drive scope may grant access to files throughout the authorized Google Drive account, not only the folder selected for this service. Operators should use a dedicated Google account where appropriate and review the permissions before granting access.
How data is used
The Google Drive API is used to create, read, update, list, and remove temporary files that carry session data between the software instances configured by the operator. The instances communicate by exchanging these files through the selected Drive folder. The data carried in those files depends on the operator's use and configuration of the software.
Storage and retention
Temporary files are stored in the operator's Google Drive and may count toward that account's storage. The component is designed to remove expired session files. The operator remains responsible for the Google account, the selected folder, and any files that remain in Drive.
Sharing and disclosure
Files in the selected folder are accessible to the Google account and to the configured software instances that have the necessary credentials. Do not share OAuth client secrets, refresh tokens, configuration files, or logs containing credentials. This informational website does not receive those credentials merely because a visitor opens it.
Security and revoking access
OAuth credentials can provide broad access to the authorized Drive account. Keep them confidential and restrict access to configuration files. Operators can revoke the application's access through their Google Account settings and can stop the configured instances or delete the selected Drive folder and its contents.