How VideoBot uses Google information
VideoBot currently uses Google primarily for account sign-in and identity verification. The sign-in flow requests OpenID Connect identity scopes: openid, email, and profile.
Google API Limited Use Disclosure
Google API Limited Use Disclosure
Last updated: July 14, 2026
Information received
Google may provide a verified email address, display name, profile image metadata when available, issuer, audience, and provider subject. VideoBot stores the verified provider subject as the stable Google identity key and stores email/display name for account access and support.
What VideoBot does not receive
VideoBot does not receive your Google password. VideoBot does not request Gmail, Google Contacts, Google Drive, YouTube upload, YouTube posting, offline access, or refresh-token scopes for this identity-only sign-in foundation.
Sessions and security
After Google verifies identity, VideoBot creates its own secure session cookie. Sessions do not store Google tokens, roles, provider subjects, password hashes, or plaintext passwords in browser-editable cookies.
Retention and deletion
Google identity records are retained while needed for account access, security, support, and auditability. Users can request deletion through the account deletion page or support.
Sharing and service providers
VideoBot does not sell Google user data. Identity data is used to operate VideoBot account access and may be processed by service operators only as needed for security, support, and maintenance.
Revoking Google access
You can revoke VideoBot access from your Google Account permissions page. If you also want VideoBot account records deleted, use the account deletion instructions.
Contact
Contact support@videobotapp.com for Google sign-in, privacy, or deletion questions. Also review the Privacy Policy and Account Deletion instructions.