Veeval uses Google Drive only when the Veeval owner explicitly connects it to the private Veeval development workflow. The integration is designed to move approved development files and brand assets from an owner-controlled Drive location to Veeval-controlled infrastructure.
The Veeval Drive integration supports a private file bridge between an owner-controlled Google Drive folder and the Veeval VPS. It may be used for development plans, brand assets, code packages, screenshots, bot packages and other files the owner chooses to place in the designated Veeval workflow.
Veeval requests only the Google Drive access needed for the configured workflow. When read-only Drive access is used, Veeval can view and download files available to the connected Google account; it does not use that permission to edit or delete Google Drive content.
Google Drive data is used only to identify and transfer files required for the owner-authorized Veeval workflow. It is not used for advertising, profiling, sale of personal data or unrelated marketing.
OAuth credentials and synchronized files are intended to remain within owner-authorized Veeval infrastructure and access-controlled development paths. Credentials must not be committed to source repositories or exposed in public website code.
The connected Google account can revoke Veeval's Google access through Google Account security controls at any time. Veeval can also disconnect the Drive integration from its server-side configuration.
Veeval's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.