Privacy Policy

Last Updated: October 30, 2026

This Privacy Policy explains how Conflead (“Conflead,” “App,” “Service,” “we,” “us,” or “our”) collects, uses, stores, and protects personal data when you use Conflead as a standalone mobile user. We are committed to processing personal data responsibly, securely, and transparently, in compliance with Regulation (EU) 2016/679 (GDPR), the UK GDPR where applicable, and other applicable data protection laws. By using the App, you acknowledge that your personal data will be processed as described here. This Privacy Policy should be read together with our Terms of Use.

1. Who We Are

Conflead is operated by Geniusee LLC registered under the laws of Ukraine, registration number 41464540, registered address: Yaroslavs’kyi Ln, 4, Kyiv, Ukraine, 04071. For standalone users, we act as data controller within the meaning of Article 4(7) GDPR.

Data Protection Contact: info@conflead.com

2. Scope of This Privacy Policy

This Privacy Policy applies to standalone users of the Conflead mobile application. It governs our processing of personal data when you create or use a standalone account, use available features, add or generate data, use AI-assisted functionality, or contact us for support. Organisation workspace users may be subject to separate privacy terms or data processing agreements.

3. Personal Data We May Collect

Account and profile data: email address, name, gender, profile picture, preferred language or languages, account settings, account status, login and session details, other profile or account details needed to create, secure, personalise, and operate your account.

Authentication provider data: if you sign in via Apple, Google, or Microsoft, we receive only the data necessary to authenticate you (provider ID, email, name, profile picture, authentication tokens). We do not receive your password.

User Content and lead data: conference and event information; lead and contact details (names, emails, phone numbers, job titles, company names, LinkedIn links, websites); meeting information and summaries; voice recordings or transcriptions; AI-generated content; follow-up emails and sequences; calendar data; export files; and related metadata. If you add data about third parties, you are responsible for ensuring you have all required rights, notices, and lawful bases to do so.

AI-related data: data you provide or create in the App to generate AI outputs, including account data, lead data, meeting information, summaries, and transcriptions. You must not submit sensitive personal data, special category data (Art. 9 GDPR), or data you are not authorised to process through AI features.

Email and communication data: recipient information, subject lines, email content, send date and time, email sequence data, email status, connected email account information, and related metadata where you use email functionality.

Marketing preferences, consent records and email sending data: your marketing email preference and unsubscribe status; records of when and how you gave or withdrew consent and the wording presented to you; the email address and name used for messages; scheduled messages and technical information confirming that Amazon SES accepted an email for sending. We do not track opens or clicks in our marketing emails.

Purchase and subscription data: purchased plan, subscription and payment status, transaction identifier, renewal and cancellation status, and payment confirmation. Full payment card details are handled by Apple App Store, Google Play, or Stripe; we do not store them.

Device, technical, and usage data: device model, operating system and app version, IP address, approximate location from IP, app events, feature usage, crash reports, error logs, and security events.

Support and contact data: name, email, message content, and communication history when you contact us.

Aggregated or anonymised data: we may derive aggregated or anonymised information for analytics and product improvement. If such data could re-identify you, we treat it as personal data.

4. Special Categories of Personal Data

We do not intentionally collect special category data within the meaning of Article 9 GDPR, such as health data, biometric data, racial or ethnic origin, political opinions, religious beliefs, or sexual orientation. You must not upload or process such data through the Service unless you hold all required explicit consents and legal safeguards under applicable law.

5. Data Minimisation

We collect and process only personal data that is reasonably necessary for the purposes described in this Privacy Policy.

6. Lawful Bases for Processing

Where applicable law requires a lawful basis for processing, we rely on:

  • Performance of a contract (Art. 6(1)(b) GDPR): to provide the Service, manage your account, and process payments.
  • Legitimate interests (Art. 6(1)(f) GDPR): to maintain security, prevent fraud, improve the Service using aggregated data, and provide support. We have assessed that these interests are not overridden by your fundamental rights.
  • Legal obligation (Art. 6(1)(c) GDPR): to comply with applicable tax, financial, and regulatory requirements and respond to lawful authority requests.
  • Consent (Art. 6(1)(a) GDPR): for optional marketing emails as described in Section 17 and for non-essential cookies or similar technologies where consent is required. Marketing consent is separate from account registration and acceptance of the Terms. You may withdraw it at any time without affecting prior lawful processing.
  • Legitimate interests (Art. 6(1)(f) GDPR), where applicable: to maintain and apply your unsubscribe preference while your account exists so that we do not send unwanted marketing, subject to the retention rules in Section 14.

7. How We Use Personal Data

We use your Personal Data for the following purposes:

  • Service Delivery: To create and manage your account; capture and organise leads; process meeting notes, recordings and summaries; generate AI-assisted content; and provide email sequences, calendar integrations and other features you request.
  • Billing & Payments: To process subscription payments, issue invoices, and manage billing disputes.
  • Customer Support: To respond to inquiries, troubleshoot issues, and provide technical assistance.
  • Security & Fraud Prevention: To detect, investigate, and prevent fraudulent transactions, unauthorized access, and abuse of the Service.
  • Service Improvement: To analyse aggregated, anonymised usage patterns to improve the functionality, performance and reliability of Conflead.
  • Legal Compliance: To comply with applicable law, respond to lawful requests, and enforce our Terms.
  • Communications: To send email verification and password-related service messages through Amazon Cognito, and to send optional onboarding marketing emails through Amazon SES with separate marketing consent, as described in Section 17.
  • Marketing Sequence Management: To schedule onboarding emails following registration and cancel future messages when you unsubscribe. We do not use your in-app activity or behavioural profiling to select or personalise marketing emails. We do not read your connected Gmail mailbox for this purpose.

No Model Training: We do not use Google user data to train or improve general-purpose AI or machine-learning models. Processing of User Content through AI features is described in Section 9 and, for Google user data, Section 10.1.

8. Data About Other People

The Service may permit you to add, store, or otherwise process data relating to third parties, including without limitation leads, contacts, meeting participants, email recipients, or any other individuals whose information you input into or process through the Service.

You bear sole and complete responsibility for ensuring that you possess all necessary rights, permissions, notices, consents, or other lawful basis required to:

  • input such data into the Service;
  • store such data;
  • process such data in any manner;
  • send emails based on or to such data;
  • synchronize such data with other systems or platforms;
  • export such data; or
  • otherwise use such data through any functionality of the Service.

The Company acts solely as a technical intermediary and processes such third-party data only to the extent necessary to provide the Service and the specific functionality you elect to use. The Company does not verify, validate, or assume any responsibility for the lawfulness, accuracy, completeness, or basis upon which you obtained such information.

You agree to be solely responsible, at your own expense, for resolving any claims, disputes, or demands brought by third parties arising from or related to the processing of their data through the Service, and you agree to indemnify and hold the Company harmless from any losses, damages, or liabilities arising from your breach of this provision.

9. AI Processing

Where you use AI-assisted features, information you provide is processed to generate outputs such as summaries, extracted data, talking points, or follow-up emails. We may use third-party AI providers to support AI features; such providers process data only as necessary to generate the requested output and do not retain User Content beyond the active processing request or use it to train their models. AI outputs may be inaccurate or incomplete. You are responsible for reviewing all AI-generated content before using or sending it.

10. Email Features

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.

11. Third-Party Services and Disclosures

We do not sell your personal data. We share personal data with third-party service providers only as necessary to operate the Service, under written agreements requiring them to process data only on our instructions and maintain appropriate security. Providers include:

  • cloud hosting and infrastructure providers;
  • authentication providers (Apple, Google, Microsoft);
  • payment providers (App Store, Google Play, Stripe);
  • AI, transcription, and automation providers;
  • Amazon Web Services, including Amazon SES for our onboarding marketing emails and Amazon Cognito for account authentication and service messages; Google/Gmail and Microsoft/Outlook for follow-ups sent from your connected account; and calendar providers where you use calendar integrations;
  • analytics and diagnostics providers;
  • security and fraud prevention providers;
  • legal, accounting, and compliance advisers;
  • competent authorities, regulators, or courts where required by law;
  • successors in a merger, acquisition, or sale of assets, subject to confidentiality obligations; for Google user data, any such transfer additionally requires the user’s explicit prior consent and compliance with Section 10.1.

Amazon SES processes recipient email addresses and message content to send our onboarding marketing emails. In our current setup, we do not maintain contact lists in SES; technical AWS service logs may remain as described in Section 14. Amazon Cognito processes account and authentication data for email verification and password-related messages. Follow-up emails to your leads are generated, scheduled and sent by Conflead from your own connected Gmail or Microsoft/Outlook account through the relevant integration; they are not routed through our SES marketing sequence. International transfers are subject to Section 12, and Google user data remain subject to Section 10.1.

12. International Data Transfers

Your data may be processed in countries outside the European Economic Area, including the country where you are located.

Where such transfers occur, we apply appropriate safeguards required by applicable law, such as Standard Contractual Clauses adopted by the European Commission, adequacy decisions, or other legally recognised transfer mechanisms.

Details on the safeguards applied to a specific transfer are available upon request.

13. Data Security

We implement appropriate technical and organisational measures to protect personal data against unauthorised access, loss, misuse, alteration, or disclosure in accordance with Article 32 GDPR. These measures may include access controls, confidentiality obligations, encryption in transit (TLS 1.2 or higher), monitoring, and incident response procedures. No method of electronic transmission or storage is completely secure, and we cannot guarantee absolute security. In the event of a personal data breach likely to result in a high risk to your rights and freedoms, we will notify you without undue delay in accordance with Article 34 GDPR. You are responsible for keeping your device, account credentials, email account, authentication methods, and connected third-party accounts secure.

14. Data Retention

We retain account-related data while your account exists. The following rules distinguish deletion from our own systems from copies and logs held by external services:

  • Account and authentication data: kept while your account exists and immediately removed from our application database and Amazon Cognito when you delete your account. Connection tokens are stored encrypted while the relevant connection is active and deleted when you disconnect it, as described in Sections 10.1 and 10.2.
  • Lead data, emails and follow-up schedules held in our application database: immediately deleted from that database when you delete your account. Other meeting content, AI outputs and voice recordings held in our application database are kept while your account exists and deleted from that database when you delete your account.
  • Records subject to a specific legal retention obligation: any legally required exception is limited to the relevant data and period required by that obligation.
  • Marketing preferences, consent records and unsubscribe status: kept with your account to document your choices and honour them. Unsubscribing stops marketing, cancels scheduled marketing emails and remains effective after you sign in again. These records are removed from our application database when you delete your account, subject only to a specific legal retention obligation described above.
  • AWS email service logs: these logs may contain email addresses and names. We retain these logs for 90 days from the date each log entry is created, after which they are automatically deleted. Deleting your account does not immediately erase these logs; any remaining entries are deleted when their respective 90-day retention periods expire.

Account deletion does not delete emails already sent to recipients or copies held in connected Gmail or Microsoft/Outlook mailboxes. These copies must be managed through the relevant email provider. AWS service logs are subject to the separate rule above.

15. Account Deletion

The App provides a mechanism to initiate account deletion where required by applicable app store rules or law. Deleting your account immediately removes your account-related data from our application database and Amazon Cognito as described in Section 14. It does not erase already-sent emails from recipients’ mailboxes or automatically remove the AWS service logs described there.

16. Your Privacy Rights

Depending on your location and applicable law, you may have rights regarding your personal data. If you are located in the EEA or UK, you have the right under the GDPR and UK GDPR to:

  • be informed about how your personal data is processed (Arts. 13–14 GDPR);
  • request access to your personal data (Art. 15 GDPR);
  • request correction of inaccurate or incomplete personal data (Art. 16 GDPR);
  • request deletion of personal data, where the legal basis for processing no longer applies (Art. 17 GDPR);
  • request restriction of certain processing (Art. 18 GDPR);
  • receive your data in a portable format, where processing is based on contract or consent and carried out by automated means (Art. 20 GDPR);
  • object to processing based on legitimate interests, including direct marketing, at any time (Art. 21 GDPR);
  • not be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning you or similarly significantly affects you (Art. 22 GDPR);
  • withdraw consent at any time, where processing is based on consent, without affecting the lawfulness of processing carried out before withdrawal;
  • lodge a complaint with a data protection supervisory authority (Art. 77 GDPR).

To exercise your rights, contact us using the details in the "Contact" section. We may need to verify your identity before responding to your request. We will respond within 30 days of receipt, which may be extended by a further 60 days for complex requests, in which case we will notify you of the extension and the reasons for the delay. Some rights may be limited by applicable law, security requirements, legal obligations, fraud prevention, or the rights of others.

17. Service and Marketing Communications

Service emails

We send non-marketing service emails for email verification and password-related account actions through Amazon Cognito. These messages support account authentication and access to the Service, do not depend on marketing consent and do not contain promotional material. The applicable legal bases are described in Section 6.

Optional marketing emails

With your separate, optional consent, we send our onboarding marketing emails through Amazon SES. This sequence introduces Conflead, explains how to try its features and encourages you to use the Service. These promotional onboarding emails are treated as marketing even when sent soon after registration.

Marketing consent is not required to create an account, sign in or use the Service. You give consent by selecting a separate, optional checkbox that is unchecked by default. We send marketing emails only to users with active consent. Signing in, accepting the Terms or acknowledging this Privacy Policy does not by itself constitute marketing consent. Existing preferences remain in effect unless you actively change them.

To document your choice, we keep a record linked to your account showing the date and time of consent, its source and the version of the consent wording presented to you. We retain a copy of each version of that wording and record the date and time of withdrawal when you unsubscribe. These records are used to manage your choices and demonstrate compliance.

Your choice and withdrawal

Every marketing email includes an unsubscribe link, including a one-click unsubscribe option. You may also contact info@conflead.com to withdraw consent. Unsubscribing stops future marketing emails, cancels scheduled marketing emails and remains effective after you sign in again. Necessary verification and password-related service emails may continue. Withdrawal does not affect the lawfulness of processing carried out before withdrawal and does not prevent you from using the Service.

Data used for communications

We process your email address, name, communication preferences, consent and withdrawal records, unsubscribe status and sending information for these communications. We do not track whether you open our marketing emails or click their links, and in-app activity does not influence these mailings. The sending status currently available to us confirms that Amazon SES accepted the email for sending; it does not confirm delivery to your inbox, opening or reading. Providers are described in Section 11 and retention in Section 14.

Emails you send through Conflead

This marketing consent and unsubscribe preference concern emails sent by Conflead to you. They do not constitute consent from recipients of follow-up emails you send to your leads. Conflead generates, schedules and sends those follow-ups on your behalf from your connected Gmail or Microsoft/Outlook account, in response to your actions or configured schedule. Unsubscribing from Conflead’s marketing emails does not itself stop follow-ups you have scheduled for your leads; these are controlled through the email features of the Service. Marketing consent does not grant additional access to your mailbox or override the access limits in Sections 10.1 and 10.2.

18. Cookies and Similar Technologies

Where Conflead uses websites, landing pages, analytics tools, or web-based services, we use only strictly necessary cookies without consent. For non-essential cookies, we obtain your prior consent in accordance with Article 5(3) of Directive 2002/58/EC (ePrivacy Directive) and provide cookie management options. More information may be provided in a Cookie Policy or cookie notice where applicable.

19. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. If we make material changes, we will provide at least 14 days' prior notice through the App, by email, on our website, or by another reasonable method, and update the "Last Updated" date. Your continued use of the Service after the updated Privacy Policy becomes effective constitutes your acceptance of the updated Privacy Policy.

20. Contact

If you have questions about this Privacy Policy or wish to exercise your privacy rights, contact us at:

Company: Conflead

Data Protection Contact: info@conflead.com

Address: Yaroslavs’kyi Ln, 4, Kyiv, Ukraine, 04071

We aim to respond to all privacy-related inquiries within 72 hours.