Your Google data, used only as you asked.

When you connect a Google account — for example, to verify or clean contacts from Gmail or Google Workspace — EmailListChecker accesses certain Google user data through Google APIs. This disclosure explains exactly what we access, why, and the strict limits we place on its use.

We request the narrowest scopes needed for the feature you enable. Depending on the integration, that may include:

• Contact data — names and email addresses from your Google Contacts or Workspace directory, so you can verify them.
• Basic profile — your name and email, to identify the connected account.
• Limited mail metadata — only where a feature explicitly needs it (e.g. recipient addresses for list building), and only with your authorization.

We do not request access to read the body of your emails for any purpose unrelated to the feature you turned on, and we request scopes incrementally — only when a feature needs them.

Google user data is used solely to provide and improve the user-facing feature you enabled — typically importing addresses and returning verification verdicts (VALID CATCH-ALL INVALID). Specifically, we:

• Import the contacts you choose to verify or clean.
• Run deliverability checks and return results to you.
• Write results back only where you explicitly ask us to (e.g. tagging or removing dead contacts).

In line with the Limited Use requirements, we affirmatively commit that we do not:

• Sell Google user data — ever, to anyone.
• Use it for advertising, ad targeting, or building advertising profiles.
• Transfer it to others except as needed to provide the feature, comply with law, or as part of a merger with equivalent protections and notice.
• Allow humans to readthe data, unless you give explicit consent for specific messages, it's necessary for security or to comply with law, or the data is aggregated and de-identified for internal operations.
• Use it to train generalized AI/ML models. We never train models on the raw contents of your Google data.

Google user data is encrypted in transit and at rest and held only as long as needed to deliver the feature, then deleted on the same retention clock as the rest of your data — down to zero-retention modes on eligible plans.

Our handling of Google user data is covered by our SOC 2 Type II program and the controls in our Security Requirements, and we have completed Google's security assessment for the relevant scopes. General data handling is described in our Privacy Policy.

Questions about how we use Google user data? Contact [email protected]. You can also report concerns about app behavior directly to Google.