Privacy policy
This policy describes data handling by OTG Advisory's Company Drive Portal and its Google authorization application, “otg”. Updated 22 October 2026.
Data we access and why
After you connect Google, the portal accesses your Google account ID and email to bind the correct identity to your portal login. For authorized company tasks it accesses Drive file names, identifiers, types, folders and other metadata; file contents and spreadsheet cells; and Drive activity information, which may include actor identity, actions and times.
This data supports file access, work summaries, reconciliation, saved work records, monitoring and audit trails. Your role, department, assigned files and the Google account's own permissions limit access. Where permitted, explicit file actions can create spreadsheets, upload, rename, move or move files to Trash.
What the portal stores
Google account identity and encrypted OAuth access and refresh tokens are stored on the portal server under your portal user ID. They allow automatic token refresh and use from your other signed-in devices. The portal does not collect or store your Google password.
The portal also stores portal profiles and permissions, work records and snapshots used by enabled modules, saved payment or monitoring history, and audit records. Logs may include file IDs and names, actions, account identity, timestamps, IP address and user-agent information. Stored data depends on the features used; not every file read is a permanent copy.
Sharing and optional AI assistance
The service sends requests and permitted changes to Google and processes data on the server infrastructure configured by OTG Advisory. Authorized company users can view work data within their assigned access. Connecting Google does not make company records public.
When AI assistance is enabled and you use it, prompts, conversation context, authorized Drive search results and file contents can be sent to the configured OpenAI API service. Depending on the requested file and supported format, this may include the complete file, not only an excerpt. User and assistant messages and usage records are also saved in the portal's local history. The provider also processes submitted data under its applicable service terms and settings.
Connection controls, retention and deletion
Signing out of the portal retains your server-side Google connection. Disconnecting Google in the portal clears its saved Google credentials for all your devices and disables the associated management monitor connection. It does not itself revoke the application's authorization at Google or delete existing company work records, identity links, snapshots, audit entries or chat history. You can separately revoke access in your Google Account's third-party connection settings.
Saved data has no single retention period across all modules. For questions or requests to access, correct or delete data, contact the support address below and identify the portal account and records involved. Disconnecting alone is not a request to delete historical company data.
Cookies and policy updates
The portal uses cookies for sign-in sessions, language preference and the Google authorization flow. This policy may be updated as the service changes; the current version and update date are published on this page. For privacy requests or an explanation of a feature's data handling, contact OTG Advisory.