Privacy Policy

Effective and last updated: November 13, 2026

This policy explains how the EgoHub Session Splitter project handles information when its authorized Google Drive integration is used.

1. Information accessed

The application requests the minimum Google Drive permission needed to create and manage files created by, or explicitly selected for, the application. It is not designed to browse or manage unrelated files across the Drive owner's account.

2. How information is used

Authorized Session files and folders are used only to store prepared outputs in the project owner's Google Drive and, when configured by the owner, transfer those outputs to the designated delivery destination.

3. Storage and retention

Session files stored in Google Drive remain under the Drive owner's control until the owner deletes them. Transfer infrastructure is designed to stream files without retaining permanent duplicate Session copies. Limited operational records, such as file name, transfer status, byte count, and timestamps, may be retained for reliability and troubleshooting.

4. Sharing

Google Drive data is not sold or used for advertising. Files are shared only with services selected by the project owner for authorized delivery, such as the configured data-delivery destination, or when required by law.

5. AI and machine learning

Data obtained through Google Workspace APIs is not used to develop, improve, or train generalized or non-personalized artificial-intelligence or machine-learning models.

6. Security

Long-lived Google authorization credentials are intended to remain in owner-controlled infrastructure and are not distributed to collection operators. Access can be revoked by the Google Drive owner at any time through Google Account security settings.

7. User choices

The Drive owner may revoke access, delete files, or stop using the integration at any time. Revoking access prevents future Drive operations but does not automatically delete files already stored in Drive.

8. Contact

For privacy or access questions, contact the project owner using the support address displayed on the Google OAuth consent screen.