Last updated: 26 October 2026.
The current Google Drive connector accesses the metadata and contents of one configured document to provide reference material in Nexa Brain. The requested Google permission is Drive read-only, which is broader than the document the current implementation reads. Nexa does not modify Google Drive files.
A text snapshot is stored in the owner's configured Windows project folder. Local study material and relevant excerpts may be included in requests to the owner's locally running model. These requests do not train or change model weights. Folders managed by OneDrive, Google Drive Desktop, or other backup software may be synchronized according to the owner's settings.
The current Google refresh credential and Make API credential are encrypted in private local Docker volumes. Access credentials are not included in normal application reports. Local administrators and anyone with administrative access to Docker can access the environment; this is not a hardware-backed credential vault.
The current Work path uses Google endpoints to authorize and read Drive, Make endpoints to read workflow evidence, and the local model endpoint to prepare reviewed answers. It does not sell Google user data, use it for advertising, or use it to train a generalized model.
The local Google connection page provides a disconnect control that removes Nexa's saved Google refresh credential and current Google document snapshot. It does not revoke Google's account-side grant or remove backups, exported reports, or existing conversation text. The owner may revoke access separately in Google Account settings and remove local data and backups under their control.
Contact the installation owner using the support email shown on this application's Google consent screen.