Google API & Gmail Data Use

Last updated: June 28, 2026 · LeadWithEmail (Love Ellie Inc.)

This page explains exactly what Google/Gmail data LeadWithEmail accesses, why we need it, how we use it, and what we store. It is a focused companion to our Privacy Policy.

Google API Services User Data Policy — Limited Use

LeadWithEmail’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Gmail data for advertising, we do not sell Gmail data, and we do not transfer Gmail data to others except as needed to provide the features below, to comply with applicable law, or as part of a merger or acquisition.

1. What Gmail scope we request

LeadWithEmail requests a single Gmail scope: https://www.googleapis.com/auth/gmail.modify. We request this scope only after you choose to connect Gmail from your account settings or onboarding — it is never requested at sign-in.

2. Why we need it & how we use it

We use Gmail access for three product features, and nothing else:

Send your outreach emails — we send the emails you create, from your own Gmail account, to the contacts you upload.
Detect replies — we periodically search your inbox for messages from contacts you have already emailed through LeadWithEmail, so we can show replies and flag interested buyers ("hot leads").
Mark messages — the modify scope lets the platform apply standard Gmail label/read changes to messages it handles.

We do not read, scan, index, or analyze your wider mailbox, drafts, or messages from people you have not contacted through LeadWithEmail. Reply detection is scoped to the specific contact addresses you have emailed.

You are responsible for having a lawful basis, permission, or prior relationship to email each recipient you contact through your connected Gmail account, and for complying with anti-spam and privacy laws. LeadWithEmail does not verify recipient consent. See our Terms of Service.

3. What Gmail data we store

To make the product work, we store the following in your isolated account:

OAuth tokens — your Gmail access and refresh tokens, encrypted at rest (Fernet / AES-128-CBC). These let us send and detect replies without asking you to sign in to Google every time.
Sent email records — for emails you send through the platform we store the recipient, subject, body, send time, and the Gmail message/thread ID.
Reply snippets — when a contact you emailed replies, we store a short preview of that reply (currently up to 500 characters, taken from the Gmail message snippet) plus its subject and message/thread ID, so the conversation and hot-lead view can show what they said.

We store a preview/snippet of inbound replies from tracked contacts — not your entire mailbox. We do not download or store messages from senders you have not contacted through LeadWithEmail.

4. Is Gmail data sent to AI providers?

Partly, and only for one feature. When a contact replies, the text of that reply snippet is sent to our AI provider (Anthropic Claude by default) to draft a suggested response for you. This draft is shown to you for review — it is never sent automatically.

Outbound email generation uses your brand details and a contact’s first name, company, and location — not the contents of your mailbox. We do not send your contact list, mailbox, or Google account credentials to AI providers, and we do not use Gmail data to train AI models. See Subprocessors.

5. AI never sends email on its own

AI is used to draft and recommend only. Emails are sent only from campaigns you create and start, and reply drafts are sent only when you choose to send them. Our recommendation engine ("Autopilot") suggests outreach opportunities for you to review — it does not send anything by itself.

6. How to disconnect Gmail

You can disconnect Gmail at any time. We provide two independent paths:

In LeadWithEmail — go to Settings → Account and choose Disconnect Gmail. This revokes the token with Google and deletes the stored access/refresh tokens, token expiry, and scopes from our database. Sending and reply detection stop immediately.
In your Google account — visit myaccount.google.com/permissions and remove LeadWithEmail’s access.

Disconnecting Gmail stops further access but does not by itself delete the email records already stored in your account — see deletion below.

7. How to delete your Google/Gmail data

You can delete your entire account — including stored Gmail tokens, sent-email records, and reply snippets — from Settings → Account → Delete account in the app. You may also email [email protected] with the subject "Data Deletion Request".

Full details, including what is deleted and any limits, are on our Data Deletion page.

Questions: [email protected] · Last updated: June 28, 2026