If you connect an email account or use email functionality within the Service, we process the data needed to create, schedule, send, stop, or track emails.
You are responsible for ensuring you have the right to contact recipients and that your communications comply with applicable laws, including privacy, electronic communications, marketing, and anti-spam laws (such as the ePrivacy Directive 2002/58/EC and GDPR).
We do not guarantee email delivery, inbox placement, replies, conversions, or other business results.
10.1 Google Account and Gmail Data
This subsection describes Google Sign-In and the Gmail sending integration. It applies to Google user data processed through these features and takes precedence over any broader permission to use or disclose data elsewhere in this Privacy Policy.
Google authentication data
When you sign in with Google, we receive your Google Account identifier, primary email address, name and profile picture where made available by Google, together with authentication information and OAuth tokens needed to establish and maintain the connection. We use these data to create or link your Conflead account, authenticate you and connect the Gmail sending feature you authorise. We do not receive your Google password. Profile permission does not mean that we collect every item of personal information available in your Google Account.
Gmail sending data and purposes
With your authorisation, Conflead sends follow-up emails from your connected Gmail account in response to your actions or according to an email sequence or schedule you configure. To provide this feature, we process the sender and recipient email addresses, subject, message body, scheduled or actual send time, and sending identifiers and status information available from the sending operation. Follow-up content is entered by you or generated within Conflead using the information you provide. We use these data to prepare and send your follow-ups, manage their schedule and show their sending status.
Limits of the sending integration
The Gmail sending integration requests permission to send email on your behalf. This sending permission does not allow Conflead to read incoming messages, retrieve your existing mailbox contents or monitor replies. The sending integration described here does not use those capabilities. A sending status is not confirmation that a recipient opened or replied to an email. If we introduce a feature requiring additional Google data or permissions, we will first update the relevant disclosures and obtain the authorisation and consent required for that feature.
Storage and deletion
Google OAuth tokens are stored encrypted in our database while the connection is active and are deleted when you disconnect the integration. Token validity is determined by Google. Disconnecting Google does not delete data already stored in Conflead. Sending is unavailable until you reconnect. Scheduled follow-ups are not automatically cancelled on disconnection, but sending attempts made while the connection is inactive do not send the messages.
Follow-up content, schedules and sending status records stored in our application database are kept while your account exists and deleted from that database when you delete your account, subject to any specific legal retention obligation. Google-derived profile data are subject to Section 14 and the Google-data restrictions in this subsection. Emails already sent through Gmail remain in the relevant mailboxes and must be managed separately through the email provider.
Infrastructure and AI processing
Our hosting and infrastructure providers process the account, connection and email data necessary to operate and secure the integration. Google processes the sender, recipient and message data needed to send the email through Gmail. When you use AI-assisted follow-up generation, our AI providers process the lead information, meeting notes, prompts and other content supplied within Conflead that are needed to generate the requested message, as described in Section 9. This is distinct from reading your Gmail mailbox: the sending integration does not retrieve incoming Gmail messages for AI processing.
Google user data are disclosed to service providers only to support the disclosed user-facing features, with the required user consent and appropriate contractual restrictions, or under the other narrowly permitted circumstances described below. OAuth tokens are not provided to AI providers for message generation. Google user data are not used to train or improve general-purpose AI or machine-learning models.
Your control over Google access
You may revoke Conflead access through the third-party connections settings of your Google Account at https://myaccount.google.com/connections. Revocation prevents further authorised access through that connection; Gmail sending features will be unavailable until you reconnect. It does not automatically erase data already stored in Conflead. To request deletion of stored Google-related data, contact info@conflead.com. You may also initiate account deletion through the App as described in Sections 14 to 16. Deletion requests are handled subject to applicable law and the retention rules described here.
Limited Use of Google user data
We handle Google user data, including information derived from those data, in accordance with the Google API Services User Data Policy and its Limited Use requirements. Use is limited to providing or improving the disclosed, visible user-facing features. We do not sell Google user data, use them for advertising or retargeting, disclose them to data brokers, or use them for creditworthiness or lending decisions.
Transfers are limited to those necessary for the disclosed user-facing features with user consent, necessary security investigations, compliance with applicable law, or a merger, acquisition or sale of assets after obtaining the user's explicit prior consent. Confidentiality obligations alone do not authorise a transfer of Google user data in a business transaction.
Our personnel and service providers may not read Google user data unless the user has affirmatively agreed to access to the specific data, access is necessary for security or legal compliance, or the data are aggregated and anonymised for permitted internal operations. These restrictions apply to our employees, contractors, service providers and successors.
10.2 Microsoft Account and Outlook Data
This subsection describes Microsoft sign-in and the Outlook sending integration for individual Conflead users. Organisational workspace users may be subject to separate terms as described in Section 2.
Microsoft authentication data
When you sign in with Microsoft, we receive your Microsoft account identifier, email address, name and profile picture where available, together with authentication information and OAuth tokens needed for the authorised connection. We use these data to create or link your Conflead account, authenticate you and enable the Outlook sending feature you authorise. We do not receive your Microsoft password.
Outlook sending data and access limits
With your authorisation, Conflead generates, schedules and sends follow-up emails from your connected Microsoft/Outlook account in response to your actions or the schedule you configure. We process sender and recipient email addresses, the subject, message body, schedule and sending status information needed to provide this feature. Microsoft processes the message data needed to send the email.
For individual users, the integration requests sign-in and email-sending permissions only. It does not read incoming messages or monitor replies. The sending permission does not by itself grant access to read your mailbox. A sending status does not confirm that a recipient opened or replied to your email.
Tokens and disconnection
Microsoft OAuth tokens are stored encrypted in our database while the connection is active and deleted when you disconnect Outlook. Microsoft determines token validity and expiry; this does not change our storage and deletion rules.
Disconnecting Outlook leaves data already stored in Conflead in place. Sending is unavailable until you reconnect. Scheduled follow-ups are not automatically cancelled, but sending attempts made while the connection is inactive do not send the messages. You can manage your follow-up schedules through the Service. Connecting Outlook does not subscribe you to Conflead marketing emails.
Account deletion and retention
When you delete your Conflead account, your lead data, email content and follow-up schedules are immediately deleted from our application database, and your account and authentication data are removed from Amazon Cognito. Emails already sent remain in the relevant mailboxes. AWS email service logs may contain email addresses and names and are retained for 90 days from creation as described in Section 14. Providers and international transfers are described in Sections 11 and 12.