Leads AI Privacy Policy

Leads AI is an AI-powered sales platform founded and developed by Ishan Satia and operated by Network Medias. Network Medias is the business operator responsible for the service and its handling of personal information. Questions about this Privacy Policy may be sent to ishan@networkmedias.com.

Users may provide information such as:

• Name and email address
• Business Profile information and company information
• Lead and contact information
• Uploaded Excel or CSV files
• Business-card images
• Email draft content, meeting details, notes and sales activities
• Support requests

Users are responsible for having the appropriate rights or permission to upload and process third-party contact information.

When you choose “Continue with Google”, Google may provide:

• Google Account name
• Email address
• Profile picture
• Google Account identifier

This information is used for account creation, login, account identification and profile display. Basic Google login is separate from the optional Gmail and Google Calendar connection.

When you choose to connect Gmail, Leads AI requests the https://www.googleapis.com/auth/gmail.send permission. This permission is used only when you:

1. Create or generate an email in Leads AI
2. Review the recipient
3. Review the subject
4. Review or edit the body
5. Explicitly select “Send via Gmail”

Leads AI:

• Does not read your Gmail inbox
• Does not retrieve Gmail message history
• Does not automatically send emails
• Does not manage Gmail mailbox drafts
• Does not request the gmail.compose permission

When you send an email through Leads AI, we store the internal draft record you created, which includes the recipient address, subject, body, send timestamp and the Gmail message identifier returned by Google, along with a lead activity entry.

When you choose to connect Google Calendar, Leads AI requests the https://www.googleapis.com/auth/calendar.events.owned permission. This permission is used only for user-approved:

• Google Calendar event creation
• Calendar invitations
• Google Meet creation
• In-person meeting creation

You review and confirm the meeting title, attendee email, date, time, description, Google Meet option and any in-person location before an invitation is created. Leads AI does not automatically schedule meetings and does not create invitations without your confirmation.

Leads AI stores the calendar event ID, meeting title, attendee information, date and time, Google Meet URL, calendar event URL, in-person location and meeting activity history for meetings you create through the app.

When you connect Google, Leads AI stores:

• Google access token
• Google refresh token
• Granted scopes
• Connected Google email address
• Token expiration timestamp
• Connection status and update timestamps

These credentials are used only to provide the Gmail and Calendar features you request. Google OAuth credentials are handled through the application’s server-side integration and are not intentionally exposed through the public user interface.

• Provide account access
• Manage leads
• Generate user-requested AI drafts and briefs
• Send user-approved Gmail messages
• Create user-approved Calendar events
• Display meetings and activities
• Maintain Business Profile context
• Improve reliability, security and performance
• Respond to support requests

Leads AI does not use your information for advertising.

Google Workspace API data is not used to develop, improve, or train generalized or non-personalized artificial intelligence or machine-learning models.

When you request an AI-generated result — such as an email draft, a lead brief or a meeting invitation description — Leads AI sends the user-entered lead and Business Profile context, and the content you supplied, to an AI provider to generate that output. The AI provider used is the Lovable AI Gateway. Google Workspace API data received from Google APIs is not sent to AI providers for training. AI-generated output is stored as your internal Leads AI draft until you send or delete it.

Leads AI uses the following service-provider categories:

• Supabase — authentication, database and storage
• Google — Gmail Send and Calendar Events APIs when you connect Google
• Lovable AI Gateway — AI model provider for user-requested generations
• Cloudflare Workers — application hosting runtime

Google user data:

• Is not sold
• Is not shared for advertising
• Is not transferred to data brokers
• Is not used for surveillance

10.1 Data accessed

When you authenticate with Google or connect Google, Leads AI may access:

• Basic Google account information such as name, email address and profile information when you authenticate or connect Google.
• The outgoing email recipient, subject and message body that you have created or approved inside Leads AI for the purpose of sending that message through Gmail.
• Google Calendar event information necessary to create and manage user-approved events on calendars owned by the connected user, including title, attendees, date and time, description, location and Google Meet information.
• Google OAuth access and refresh tokens required to maintain the authorized connection.

Leads AI does not read your Gmail inbox, and does not retrieve Gmail history or existing Gmail messages. Leads AI does not require access to calendars the connected user does not own.

10.2 How Google data is used

Google data is used only to:

• Authenticate or identify the connected Google account.
• Send an email after you review and explicitly confirm the message.
• Create or manage a Calendar event after you review and explicitly confirm the event.
• Maintain the user-authorized Google connection.

Leads AI does not use Google Workspace API data for advertising, profiling, credit decisions or unrelated purposes.

10.3 AI and machine learning

Leads AI uses the Lovable AI Gateway with Google Gemini 2.5 Flash to power its AI features. Information obtained from the Gmail API or the Google Calendar API is not sent to the AI/ML service.

AI-generated email drafts are produced from user-entered Leads AI CRM, lead and Business Profile data before the Gmail API is called. Meeting information is prepared in Leads AI and reviewed by you before the Calendar API is called. Google OAuth tokens, Gmail API responses, Calendar API responses and connected-account metadata are not sent to AI/ML providers.

10.4 Data transfer

Google user data is processed by infrastructure and service providers only as necessary to operate Leads AI (application hosting and authentication, database and storage). Google user data is not sold, transferred to advertisers or data brokers, or used for targeted advertising. Gmail or Calendar API data is not transferred to third-party AI/ML services.

10.5 Data protection

• Google OAuth credentials are encrypted at rest using authenticated encryption.
• Connections use HTTPS/TLS in transit.
• OAuth credentials are processed only by trusted server-side services.
• Access is restricted through authentication and database access controls.
• OAuth credentials are not exposed to browser clients.

10.6 Retention and deletion

Google OAuth credentials are retained only while the Google integration remains connected, or as required to provide the service you requested. Disconnecting Google in Leads AI revokes or removes the stored Google OAuth credentials. You may also request deletion of your Leads AI account and associated data through the existing Data Deletion process.

10.7 Limited Use

The use of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

10.8 Support

Privacy and support questions: ishan@networkmedias.com.

Leads AI’s use and transfer to any other application of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Leads AI Reports turns the CRM information already stored in your account into a downloadable PDF report. This section explains exactly what data a report uses, how it is generated and where it is stored.

12.1 What data a report uses

Reports are built only from records stored in your own Leads AI account:

• Lead records (name, company, contact person, role, email, phone, source, status, priority, follow-up date, notes and timestamps)
• Lead activity records logged in Leads AI
• Meeting records created through Leads AI
• Counts of internal email drafts and sends recorded in Leads AI
• Your Business Profile details, used for report branding and context
• Any commentary you type into the report builder

12.2 Google user data is not used

Leads AI Reports do not call any Google API and do not read your Gmail mailbox or your Google Calendar. Report content never includes Gmail message content, Gmail metadata retrieved from Google, or Google Calendar data retrieved from Google. Reports reflect only what is stored inside Leads AI.

12.3 How reports are generated

Report figures, charts, stage breakdowns and tables are calculated deterministically from your stored records. Report content is not written by an AI model, and lead data is not sent to an AI provider in order to produce a report. AI features elsewhere in Leads AI (such as lead briefs) remain separate and are described in section 8.

12.4 Storage and access

Generated PDFs are stored in private, user-scoped storage. Only your authenticated account can list or download your reports, and downloads use short-lived signed links. Reports are never public, are not shared with other users, and are not sold or used for advertising.

12.5 Retention and deletion

Reports remain available in your report history until you delete them. Deleting a report removes the stored PDF and its history record. Deleting your Leads AI account removes your report history and all stored report PDFs.

12.6 Your responsibility when sharing

A report can contain contact information for the leads you have stored. If you share a report outside your organisation, you are responsible for ensuring that sharing is lawful under applicable privacy and data-protection rules.

We retain account information, lead data, internal email drafts, meeting records, activity records, generated Leads AI Reports and stored Google OAuth credentials while the account remains active and as needed to provide the service, unless deletion is requested or a longer period is legally required.

When you disconnect Google, Leads AI clears the stored access token, refresh token and token expiration information for that connection. Your leads, internal email drafts and previous meeting records remain in your Leads AI account so you keep your history.

When you delete your Leads AI account, your user-owned records are removed from active application storage. Backups may temporarily retain information for a short period before being overwritten.

You can:

• Disconnect Google inside Leads AI to remove stored Google OAuth credentials
• Revoke access from your Google Account permissions page
• Delete individual Leads AI Reports, which removes the stored PDF
• Request deletion of your Leads AI account and data

See the Data Deletion page for step-by-step instructions, or email ishan@networkmedias.com.

Leads AI applies operational security measures including:

• HTTPS transmission
• Server-side handling of Google OAuth tokens
• Supabase authentication
• Row-Level Security policies on user-owned tables
• Private, user-scoped storage for generated report PDFs
• Restricted secret storage for API credentials

No system is perfectly secure. Leads AI does not claim SOC 2, ISO or HIPAA certification.

You may request access, correction, export where supported, deletion, Google disconnection and withdrawal of authorization. Send privacy requests to ishan@networkmedias.com.

Leads AI is intended for business and professional use. Users must meet the minimum age required to consent to online services in their jurisdiction. If you believe a child has provided information to Leads AI, contact ishan@networkmedias.com.

Material changes to this policy will be reflected on this page with an updated effective date. Continued use of Leads AI after changes indicates acceptance of the updated policy.