Google Data Use

Google sign-in

For login and account creation, Migration Monkey requests basic identity scopes: openid, email, and profile. We use that data to verify the account, create or find the Migration Monkey user, link the Google account to the workspace, and maintain the login session.

For Google sign-in, we store hashed identity references, account metadata, and session records. We do not store Google access tokens after the login session is established.

Gmail and Google Workspace migration

If you start a Gmail or Google Workspace mailbox migration, Migration Monkey may ask for additional Google permissions for that specific migration. Those permissions are used to analyze mailbox size, labels, folders, message counts, quotas, and transfer progress, then move the mailbox data to the destination you selected.

The default route is no-custody mailbox transfer. Migration Monkey stores progress, counts, warnings, consent, hashes, and support logs. Email message bodies and attachments are not stored by default.

Limited use commitments

• Google user data is used only to provide or improve user-facing Migration Monkey features you requested.
• Google user data is not sold.
• Google user data is not used for advertising.
• Google user data is not used to train generalized AI or machine learning models.
• Google user data is not transferred except to service providers needed to operate the app, for security or legal reasons, or to complete the user-directed migration.

Revocation and deletion

You can revoke Google access from your Google Account permissions page. You can also request account deletion, OAuth unlinking, or migration metadata deletion by contacting privacy@migrationmonkey.com.