Last updated: September 11, 2026
MIP Drive is a private, single-user integration used by the owner of the Mac Integration Plugin (MIP). It connects that owner's Google Drive account to a private Linux server for file storage, archival, import, and export.
The integration may access Google Drive file and folder metadata and file contents as needed to list, import, export, or archive files. The intended operational root is a dedicated MIP Storage area in Google Drive.
MIP Drive does not use Google Drive data for advertising, profiling, sale, or unrelated analytics.
Drive data is used only to perform owner-requested file operations. Drive content is treated as inert storage until an explicit import copies selected content into MIP's isolated executable workspace.
OAuth credentials and refresh tokens are stored on the owner's private VPS in a protected configuration location that is not exposed to MIP's generic execution sandbox or ordinary workspace. Imported files may be stored in MIP's persistent local workspace until removed or archived.
MIP Drive does not sell Google user data and does not share Google user data with advertisers or data brokers. Data is transferred between the owner's Google Drive account and the owner's private MIP infrastructure as required for the requested operation.
Files remain in Google Drive until the owner deletes or moves them. Local workspace copies remain until the owner or MIP removes, replaces, or archives them. OAuth credentials remain until authorization is revoked or the credential is deleted from the private server.
The owner can revoke MIP Drive's Google account access at any time from the Google Account third-party connections/security controls. The corresponding server-side OAuth credential can also be deleted, after which the integration can no longer access Google Drive unless it is authorized again.
The Drive transfer broker and generic execution broker are separated. Generic executable processes do not receive general network access or the Google credential. This separation is intended to reduce the impact of untrusted or malicious files.
Questions about this private integration may be directed to the developer contact address listed on its Google OAuth consent configuration.