Data Usage Policy
1. Scope of Data Access
OhanaBotz Drive Access requests specific OAuth scopes to interact with your Google Drive. This access is limited to reading metadata, organizing file structures, and facilitating authorized file transfers as initiated by the user. We maintain a non-persistent connection designed strictly for active management sessions.
2. Security and Encryption
All data transmitted during Drive management sessions is encrypted using industry-standard TLS 1.3 protocols. Our OAuth implementation ensures that your Google login credentials are never processed or stored on our servers; instead, we utilize short-lived access tokens that are immediately purged upon session termination.
3. Data Retention and Deletion
We do not maintain secondary databases of your personal file content. Project metadata required for workflow optimization is stored in local volatile memory and is deleted automatically. Users may revoke application permissions at any time through their Google Account security settings, terminating all association with our service.
Security Protocols
This technical disclosure outlines our rigorous approach to Google OAuth verification and the systemic measures established to protect your enterprise data assets.
OAuth 2.0 Integration
OhanaBotz utilizes restricted Google Cloud scopes to perform programmatic actions strictly as authorized. All handshake operations occur via server-side secure tunnels (TLS 1.3), ensuring that authorization tokens are never exposed to the client-side environment. We maintain a non-custodial relationship with your Drive credentials.
Data Encryption Standards
All file metadata retrieved during synchronization is encrypted at rest using AES-256. Transient data processed during organizational tasks is held exclusively in memory and purged immediately upon completion of the operation. Our clinical infrastructure ensures zero residual footprint on secondary storage devices.